From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Mark H Weaver <mhw@netris.org>, guix-devel@gnu.org
Subject: Re: [opinion] CVE-patching is not sufficient for package security patching
Date: Wed, 17 Mar 2021 07:07:31 +0100 [thread overview]
Message-ID: <9f737d23e85e11ae4810373b043dd9c78eb0b5ae.camel@zaclys.net> (raw)
In-Reply-To: <87v99qit39.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
On Tue, 2021-03-16 at 19:19 -0400, Mark H Weaver wrote:
> That said, I strongly disagree that we should "never backport patches
> ourselves in most cases". The only way to do that, while addressing
> security flaws, would be to promptly update even our lowest-level
> libraries in response to CVEs, of which there is a steady stream.
Fortunately I think that lots of these core package upstreams also have
good CVE-issuance practices. For the Glib care in particular, I think
they are good, I consider acceptable to backport patches, everyone is
doing it, upstream is cooperative and works towards that same goal.
To everyone else in general, I understand we have to ship a working
system, and I want that too, that's why I said we should "strive" to,
but it doesnt mean we should break things, of course. By that I mean
that we shouldnt leave packages unmaintained without updates for too
long even without CVEs or other security notices issued. At some point,
if a package is of no use, no users show up and it's painful to update,
we should also consider removing the package or archiving it in a third
party channel we could create like "guix-archive", "guix-ugly" or
"guix-love-me-please".
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-17 6:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 11:10 [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-16 11:17 ` Jonathan Brielmaier
2021-03-16 11:27 ` Léo Le Bouter
2021-03-16 19:15 ` Leo Famulari
2021-03-16 23:19 ` Mark H Weaver
2021-03-16 23:49 ` Leo Famulari
2021-03-17 11:54 ` Guix moving too fast? zimoun
2021-03-17 6:07 ` Léo Le Bouter [this message]
2021-03-17 6:21 ` [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-20 11:19 ` Ludovic Courtès
2021-03-22 13:44 ` raingloom
2021-03-23 16:22 ` Joshua Branson
2021-03-23 23:53 ` Mark H Weaver
2021-03-23 17:56 ` Leo Famulari
2021-03-23 22:54 ` Ricardo Wurmus
2021-03-24 19:51 ` Leo Famulari
2021-03-24 20:24 ` Vincent Legoll
2021-03-24 20:32 ` Léo Le Bouter
2021-03-24 20:55 ` Leo Famulari
2021-03-25 14:22 ` Mathieu Othacehe
2021-03-25 18:19 ` Leo Famulari
2021-03-30 8:42 ` Buying AArch64 hardware? Ludovic Courtès
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=9f737d23e85e11ae4810373b043dd9c78eb0b5ae.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).