From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Mathieu Othacehe <othacehe@gnu.org>,
31444@debbugs.gnu.org, 31442@debbugs.gnu.org
Subject: [bug#31444] 'guix health': a tool to report vulnerable packages
Date: Fri, 25 Sep 2020 18:34:00 +0200 [thread overview]
Message-ID: <87a6xdiznr.fsf@gnu.org> (raw)
In-Reply-To: <864knuk8nk.fsf@gmail.com> (zimoun's message of "Sat, 19 Sep 2020 00:43:59 +0200")
Hi!
zimoun <zimon.toutoune@gmail.com> skribis:
> Well, instead to create another new command, I think it would be better
> to include the “leaf” packages to “guix graph” and then pipe to “guix
> lint”. Other said, “guix graph” should help to manipulate the graph of
> packages.
I don’t think so.
One reason is that ‘guix lint’ is really a generic tool for package
developers that happens to include a ‘cve’ checker; apart from that,
it’s not designed for CVE handling.
More importantly, ‘guix health’ needs info not available in the output
of ‘guix lint’: it needs the CPE name of each package in the graph,
along with the list of known-fixed CVEs.
>> Fundamentally, that means we cannot reliably tell much about
>> dependencies: in cases where the CPE name differs from the Guix name, we
>> won’t have any match, and more generally, we cannot know what CVE are
>> patched in the package; we could infer part of this by looking at the
>> same-named package in the current Guix, but that’s hacky.
>>
>> I think that longer-term we probably need to attach this kind of
>> meta-data to packages themselves, by adding a bunch of files in each
>> package, say under PREFIX/guix. We could do that for search paths as
>> well.
>
> What is the status of this idea?
The idea is still up in the air. :-)
In the meantime, package metadata is added to manifest entries.
Ludo’.
next prev parent reply other threads:[~2020-09-25 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 22:15 [bug#31444] 'guix health': a tool to report vulnerable packages Ludovic Courtès
2018-05-14 8:06 ` Martin Castillo
2018-05-14 9:07 ` Ludovic Courtès
2018-05-14 16:49 ` Nils Gillmann
2018-05-15 7:24 ` Ludovic Courtès
2020-09-18 22:43 ` zimoun
2020-09-25 16:34 ` Ludovic Courtès [this message]
2023-07-21 16:44 ` Maxim Cournoyer
2023-09-08 16:25 ` Ludovic Courtès
2023-09-09 22:14 ` Maxim Cournoyer
2023-09-11 11:23 ` Closing submission incomplete since years? Simon Tournier
2023-09-11 17:54 ` Maxim Cournoyer
2023-09-11 18:17 ` Simon Tournier
2023-09-11 20:43 ` Maxim Cournoyer
2023-09-13 19:58 ` [bug#31444] 'guix health': a tool to report vulnerable packages Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6xdiznr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31442@debbugs.gnu.org \
--cc=31444@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.