unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Nicolò Balzarotti" <anothersms@gmail.com>, guix-devel@gnu.org
Subject: Re: Please help reviewing CVE entries
Date: Fri, 09 Apr 2021 17:33:19 +0200	[thread overview]
Message-ID: <7aa3ae8b99129c1ab1d201237e063e7dfb25335a.camel@zaclys.net> (raw)
In-Reply-To: <87sg3zmvym.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

On Fri, 2021-04-09 at 15:25 +0200, Nicolò Balzarotti wrote:
> Léo Le Bouter <lle-bout@zaclys.net> writes:
> 
> > Hello!
> 
> Hi!
> > I have been feeling considerable amount of stress reviewing CVE
> > entries
> > alone, these days I want to focus on other things and I've been
> > feeling
> > held back because I abandonned the CVE entries reviewing task
> > without
> > anyone doing it when I'm not here.
> 
> Thanks for your work
> > Right now at time of sending this email, I've reviewed in-order up
> > until CVE-2021-26709 on the 
> > https://nvd.nist.gov/feeds/xml/cve/misc/nvd-rss.xml feed, I use the
> > 'quiterss' package as an rss reader.
> > 
> I just subscribed to the feed, and noticed our version of dnsmasq
> might
> be vulnerable to CVE-2021-3448, I'll follow your suggestions here and
> open a bug report.
> 
> Thanks, Nicolò

That's one really good review you opened at bug#47674

Thank you so much!!

Keep it up!


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-09 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 13:04 Please help reviewing CVE entries Léo Le Bouter
2021-04-09 13:25 ` Nicolò Balzarotti
2021-04-09 15:33   ` Léo Le Bouter [this message]
2021-04-14 18:44 ` Joshua Branson

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=7aa3ae8b99129c1ab1d201237e063e7dfb25335a.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=anothersms@gmail.com \
    --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).