From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Mark H Weaver <mhw@netris.org>, guix-devel@gnu.org
Subject: Re: GNOME 3.34 in GNU Guix and security
Date: Thu, 11 Mar 2021 09:28:22 +0100 [thread overview]
Message-ID: <1db062314b9b45d651bf7ba549a8f7e2bf0d1dbd.camel@zaclys.net> (raw)
In-Reply-To: <87lfaugl23.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Thu, 2021-03-11 at 03:18 -0500, Mark H Weaver wrote:
> Hi Léo,
Hello!
> I appreciate your recent work on Guix security. Thank you for that.
Very happy to catch up there as well for my own usage of GNU Guix as
well!
> Can you please substantiate this? What vulnerabilities do you know
> of,
> and what makes you think that we can't address them adequately in the
> usual ways, without "upgrading GNOME to [the] latest"?
I have not yet fully investigated each CVE but there is uncertainty
around gnome-shell, gvfs, librsvg, gdk-pixbuf, pango, cairo, if not
more. You can use 'guix lint -c cve <pkg>' to find out, also look up in
NVD individually in case GNU Guix doesnt find it.
I am always uneasy relying on CVE only for security patches since I
know how much lots of security issues are fixed by developers without
issuing any CVE, so to me the best way of keeping up is to always be on
latest.
> I saw your bug report about our Glib being vulnerable to CVE-2021-
> 27218
> and CVE-2021-27219. Thanks very much for bringing that our
> attention.
>
> I'll backport the fixes to our version of Glib. It will actually be
> quite easy, given that Ubuntu has already published backports of
> the
> fixes for Glib 2.56.4 and 2.64.4, which brackets the version in Guix
> (2.62.6). I just looked at the diffs between those two patch sets,
> and
> the differences are quite slight, apart from line number differences.
I am really happy you are willing to help! I will have to admit that I
am a bit overwhelmed by the amount of work that I have left still.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-11 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:19 GNOME 3.34 in GNU Guix and security Léo Le Bouter
2021-03-11 8:08 ` Ricardo Wurmus
2021-03-11 8:23 ` Raghav Gururajan
2021-03-11 9:11 ` Ricardo Wurmus
2021-03-11 9:17 ` Raghav Gururajan
2021-03-18 21:32 ` Danny Milosavljevic
2021-03-19 0:10 ` Ricardo Wurmus
2021-03-19 9:13 ` Guillaume Le Vaillant
2021-03-11 8:24 ` Jonathan Brielmaier
2021-03-11 8:18 ` Mark H Weaver
2021-03-11 8:28 ` Léo Le Bouter [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=1db062314b9b45d651bf7ba549a8f7e2bf0d1dbd.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--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).