From: zimoun <zimon.toutoune@gmail.com>
To: "Léo Le Bouter" <lle-bout@zaclys.net>,
"Mark H Weaver" <mhw@netris.org>,
guix-devel@gnu.org
Subject: Re: gnutls package may be vulnerable to CVE-2021-20232
Date: Sat, 13 Mar 2021 12:53:19 +0100 [thread overview]
Message-ID: <86mtv7gths.fsf@gmail.com> (raw)
In-Reply-To: <e2045ef00da2fbf52f12da772461e0e7226edc15.camel@zaclys.net>
Hi Léo,
On Sat, 13 Mar 2021 at 11:50, Léo Le Bouter <lle-bout@zaclys.net> wrote:
> On Sat, 2021-03-13 at 05:12 -0500, Mark H Weaver wrote:
>> For what it's worth, I think that <bug-guix@gnu.org> would be a more
>> appropriate place to send these bug reports. What do you think?
>
> I don't know, it seems people read guix-devel more maybe? I don't know
> if they are bug reports, most of the time I am handling these issues
> myself, I just try to keep a public log so I don't forget things and
> can come back later, and if I disappear, other people can still have a
> go at them.
I also think it is better to fill a bug report for these security issues
instead of guix-devel. One reason is debbugs allows severity tags,
which can be helpful to filter. Another reason is «if you disappear»,
people will not dig into guix-devel to read this “public log” but would
probably address the items in the bug tracker.
I speak for myself, when I read guix-devel or any other Guix list, I
have an org-capture and capturing security issue is not in my list (I
have enough on my plate :-)). Time to time, I open “M-x debbugs-gnu“
and select bugs: check the status and try to close them; and months
later from now I will never search in guix-devel to check
vulnerabilities of some packages. And even if I would do, the search
query, assuming a pattern in the messages, would return both closed and
still open security issues, so I would have to read first some messages,
even the closed ones, just to find the still open ones; the length of
the search results becoming larger and larger.
BTW, thanks for all this effort! :-)
Cheers,
simon
prev parent reply other threads:[~2021-03-13 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 1:25 gnutls package may be vulnerable to CVE-2021-20232 Léo Le Bouter
2021-03-13 10:12 ` Mark H Weaver
2021-03-13 10:50 ` Léo Le Bouter
2021-03-13 11:53 ` zimoun [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=86mtv7gths.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--cc=mhw@netris.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).