all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: 47188@debbugs.gnu.org
Subject: bug#47188: "guix lint -c cve" does not account for language prefixes (rust-, python-, go-, ..)
Date: Thu, 18 Mar 2021 14:26:18 +0100	[thread overview]
Message-ID: <87a6r0r3t1.fsf@gnu.org> (raw)
In-Reply-To: <706d51950b7545eefd43a54f738bc82df0d7f36c.camel@zaclys.net> ("Léo Le Bouter"'s message of "Tue, 16 Mar 2021 10:29:43 +0100")

Hi,

Léo Le Bouter <lle-bout@zaclys.net> skribis:

> ./pre-inst-env guix lint -c cve python-urllib3@1.26.2
> Here this should return at least CVE-2021-28363 but it does not because
> the CVE database contains urllib3 and not python-urllib3 (which AFAICT
> the cve linter searches for).
>
> Annotating each and every python-, go-, and rust- package with cpe-name 
> properties is going to be very annoying. I suggest we add some
> heuristics that try both the full name and prefix-trimmed name. python-
> urllib3's cpe name and vendor is python (vendor) urllib3 (name).
>
> Same story for CVE-2021-28305 and rust-diesel, though it doesnt even
> have a CPE entry yet.

Yes, that’s an issue.  We can address these by adding a ‘cpe-name’
property (info "(guix) Invoking guix lint"), but that’s going to be
tedious.  We can at least add it to high-profile packages for now.

Tooling that suggests or deduces the CPE name would help a lot:

  https://issues.guix.gnu.org/42299

Ludo’.




      parent reply	other threads:[~2021-03-18 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  9:29 bug#47188: "guix lint -c cve" does not account for language prefixes (rust-, python-, go-, ..) Léo Le Bouter via Bug reports for GNU Guix
2021-03-16 13:05 ` zimoun
2021-03-18 13:26 ` Ludovic Courtès [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

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

  git send-email \
    --in-reply-to=87a6r0r3t1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47188@debbugs.gnu.org \
    --cc=lle-bout@zaclys.net \
    /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.