unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Greg Hogan <code@greghogan.com>
Cc: 62380-done@debbugs.gnu.org
Subject: bug#62380: [staging PATCH 0/4] Update hdf5.
Date: Thu, 30 Mar 2023 23:27:01 -0400	[thread overview]
Message-ID: <87fs9ly516.fsf_-_@gmail.com> (raw)
In-Reply-To: <20230322135711.181552-4-code@greghogan.com> (Greg Hogan's message of "Wed, 22 Mar 2023 13:57:11 +0000")

Hello,

I've installed the series to staging.  It seems it could have also been
on the limit to go to master, so in the future feel free to submit for
master.

Something we should look into is hide the (false positive, I assume?)
CVEs reported by guix lint:

--8<---------------cut here---------------start------------->8---
gnu/packages/maths.scm:1390:2: hdf5@1.8.23: probably vulnerable to CVE-2020-10809, CVE-2020-10810, CVE-2020-10811, CVE-2020-10812
gnu/packages/maths.scm:1515:2: hdf5@1.10.9: probably vulnerable to CVE-2020-10809, CVE-2020-10810, CVE-2020-10811, CVE-2020-10812
gnu/packages/maths.scm:1535:2: hdf5@1.12.2: probably vulnerable to CVE-2021-37501
--8<---------------cut here---------------end--------------->8---

This can be done by adding lint-hidden-cve properties, with explanatory comments.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-03-31  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 13:55 [bug#62380] [staging PATCH 0/4] Update hdf5 Greg Hogan
2023-03-22 13:57 ` [bug#62380] [staging PATCH 1/4] gnu: hdf5@1.8: Update to 1.8.23 Greg Hogan
2023-03-22 13:57   ` [bug#62380] [staging PATCH 2/4] gnu: hdf5@1.10: Update to 1.10.9 Greg Hogan
2023-03-22 13:57   ` [bug#62380] [staging PATCH 3/4] gnu: hdf5@1.12: Update to 1.12.2 Greg Hogan
2023-03-22 13:57   ` [bug#62380] [staging PATCH 4/4] gnu: Add hdf5@1.14 Greg Hogan
2023-03-31  3:27     ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fs9ly516.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=62380-done@debbugs.gnu.org \
    --cc=code@greghogan.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).