From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: guix-devel@gnu.org
Subject: Re: [opinion] CVE-patching is not sufficient for package security patching
Date: Tue, 16 Mar 2021 12:17:49 +0100 [thread overview]
Message-ID: <baa7aa74-4e10-1739-679d-e5d6be371975@web.de> (raw)
In-Reply-To: <9b9a43a584e2dc70488482fce5931b46abd0e006.camel@zaclys.net>
On 16.03.21 12:10, Léo Le Bouter wrote:
> For these reasons, I suggest that we always strive to update packages
> to their latest versions and that I think it is security relevant to
> always do so. Of course, new code could *introduce* new vulnerabilities
> but I am not trying to debate this, it's that to the best of the
> upstream's knowledge chances are that the latest version will contain
> more security fixes than older versions (if that upstream is actually
> maintaining the project).
I think the only two reasons against that are: time and CI/rebuilding. I
think thats the reason why stuff like Gnome and others lower in the
dependency tree are lacking behind... Being non-FHS and non-systemd
makes updates for those stuff not easier and is maybe the third
reason/root issue...
next prev parent reply other threads:[~2021-03-16 11:18 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 [this message]
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 ` [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-17 6:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=baa7aa74-4e10-1739-679d-e5d6be371975@web.de \
--to=jonathan.brielmaier@web.de \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.