From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Announcement regarding the oss-security mailing list
Date: Sat, 11 Feb 2017 21:05:32 +0100 [thread overview]
Message-ID: <87k28w7asz.fsf@elephly.net> (raw)
In-Reply-To: <20170211194400.GA10091@jasmine>
Leo Famulari <leo@famulari.name> writes:
> I think that several of us are subscribed to oss-security as part of our
> effort to learn about upstream security issues in a timely manner.
>
> A couple days ago, MITRE decided to stop assigning CVEs from the list:
>
> http://seclists.org/oss-sec/2017/q1/351
>
> So, I expect that we will see fewer bugs sent to oss-security, and Guix
> developers interested in package security may need to adjust their
> approach to learning about such bugs.
>
> Let's share some tips on where to find this information.
>
> 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.
>
> What about you?
I’m not sure if this is sufficient but it looks like new CVEs are also
listed here:
https://cassandra.cerias.purdue.edu/CVE_changes/today.html
The added CVEs can also be viewed per day or month.
There’s also an RSS feed:
https://nvd.nist.gov/download/nvd-rss.xml
A disadvantage (but also a blessing) is that there’s a lot of software
in the feed that we don’t have in Guix. I would be happy if we had a
system to give us more *relevant* warnings. (Running “guix lint -c cve”
regularly and shooting off notifications…?)
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-02-11 20:05 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 [this message]
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
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=87k28w7asz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).