[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eekt9l5k.fsf@gnu.org>
Date: Mon, 16 Nov 2020 20:06:15 +0100
From: Marius Bakke <marius@....org>
To: "David A. Wheeler" <dwheeler@...eeler.com>, oss-security@...ts.openwall.com
Subject: Re: Buffer Overflow in raptor widely unfixed in
Linux distros
"David A. Wheeler" <dwheeler@...eeler.com> writes:
> If you think that CVE assignment is still of “fluctuating reliability” I’d like to hear that argument
> and get it fixed. It’s normally better to fix the standard process for doing something than
> to create yet another process that runs in parallel. I’ve seen no recent evidence of this reliability issue.
Speaking as a co-maintainer of an understaffed GNU/Linux distribution
who fixed this back in 2017[0], I preferred the "old days" when free
software security problems were almost always discussed on this list.
While there's no questioning the utility of CVEs in general (Guix can
check the CVE list for any given package with 'guix lint -c cve PKG'),
there are still unresolved CPE mappings, and I don't know how to get
informed of new problems without checking specific (or all) packages.
I tried following the CVE assignment RSS feed initially, but it was not
suitable for human consumption.
How do other distros keep up with new CVE assignments?
[0] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=099c9fdae623e06e4fded8b0d4e55d9d5b56715b
Download attachment "signature.asc" of type "application/pgp-signature" (508 bytes)
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
