From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: kdesu security update needed
Date: Thu, 29 Sep 2016 16:49:32 -0400 [thread overview]
Message-ID: <20160929204932.GA25044@jasmine> (raw)
In-Reply-To: <CAL1_imngvefzyKohmZLVrL3qKR_zDcE15=52+mGjfOz0rKd52A@mail.gmail.com>
On Thu, Sep 29, 2016 at 08:52:34PM +0200, David Craven wrote:
> Ah just checked our linter doesn't flag a CVE, so I think we're ok...
The linter is a good tool for catching things that we miss, but it's not
a substitute for manual investigation :)
First, our package's name might not match the name used by the Common
Platform Enumeration [0], which is the name that the linter looks up. We
can give packages a cpe-name property [1], which tells the linter to use
something besides the package's name.
Second, I've noticed that sometimes bugs are publicized on oss-sec or
elsewhere, but then they don't show up in the CVE database for a while.
An aside, the CVE linter gives false positives for grafted packages. For
example, try `guix lint -c cve openssl@1.0`.
[0]
https://nvd.nist.gov/cpe.cfm
[1] An example:
http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/gd.scm#n76
next prev parent reply other threads:[~2016-09-29 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 15:23 kdesu security update needed Leo Famulari
2016-09-29 18:35 ` David Craven
2016-09-29 18:52 ` David Craven
2016-09-29 20:49 ` Leo Famulari [this message]
2016-10-01 12:19 ` Ludovic Courtès
2016-10-01 12:59 ` David Craven
2016-10-02 13:34 ` Ludovic Courtès
2016-10-01 16:37 ` Leo Famulari
2016-10-03 21:36 ` Ludovic Courtès
2016-10-03 21:47 ` Leo Famulari
2016-09-29 21:34 ` Leo Famulari
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=20160929204932.GA25044@jasmine \
--to=leo@famulari.name \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
/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).