From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Announcement regarding the oss-security mailing list
Date: Mon, 13 Feb 2017 10:37:46 +0200 [thread overview]
Message-ID: <20170213083746.GB2475@macbook42.flashner.co.il> (raw)
In-Reply-To: <87h93zwluq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Sun, Feb 12, 2017 at 02:59:57PM +0100, Ludovic Courtès wrote:
> Hi Leo,
>
> Leo Famulari <leo@famulari.name> skribis:
>
> > I look at the lwn.net security advisories, the Debian security-announce
> > mailing list, `guix lint -c cve`, the upstream bug trackers of a handful
> > of packages, and even some Twitter personalities.
>
> For me it’s mostly oss-sec, LWN, and ‘guix lint’.
>
> The good thing with the new MITRE policy is that the CVE database will
> be more up-to-date, IIUC. Until now, they’d quickly reserve an ID for
> issues reported to oss-sec, but then it would take time until the CVE
> database would be updated to contain all the info (for the recent Guile
> CVEs, they asked me to give them the details again after two months or
> so…). As a side effect, ‘guix lint -c cve’ should become more useful.
>
> Ludo’.
>
That's great, in the past I assumed that if `guix lint -c cve' found the
CVE then it had already been out for a bit.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-02-13 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 19:44 Announcement regarding the oss-security mailing list Leo Famulari
2017-02-11 20:05 ` Ricardo Wurmus
2017-02-14 17:41 ` Marius Bakke
2017-02-11 20:10 ` ng0
2017-02-12 6:44 ` Alex Vong
2017-02-12 13:59 ` Ludovic Courtès
2017-02-13 8:37 ` Efraim Flashner [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=20170213083746.GB2475@macbook42.flashner.co.il \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@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).