From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43075@debbugs.gnu.org, chaosmonk@riseup.net
Subject: bug#43075: Prioritize providing substitutes for security-critical packages with potentially long build times
Date: Fri, 11 Sep 2020 16:33:00 +0200 [thread overview]
Message-ID: <87a6xwjsdf.fsf@web.de> (raw)
In-Reply-To: <CAJ3okZ30O-Y-1QyKymxwGh6WCcxKiqKizogiT=A5Sy76Ef3gVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> On Fri, 11 Sep 2020 at 08:56, Ludovic Courtès <ludo@gnu.org> wrote:
>> To me the proposal is more about introducing scheduling priorities. For
>> these packages, it’s indeed safe to assume that every new release brings
>> security fixes.
>
> Why would some packages be prioritized on the build farm than others?
> Based on what? Which criteria?
There are two aspects that make ungoogled-chromium, icecat and
linux-libre special:
- long build time
- security critical
If a user cannot run the newest ungoogled-chromium, icecat, or
linux-libre due to too high build times (so it can for example only be
built on a weekend, but not on a weekday when the computer is only
active for a few hours), then this user is prone to be hit by zero-day
vulnerabilities.
So the minimal criterion would be: Protect users from zero-days.
For ungoogled-chromium, icecat, and linux-libre, two factors match:
- the chance is very high that an update fixes a vulnerability, and
- they take so long to build that many users won’t be able to do it
right away.
I certainly can’t: I cannot update ungoogled-chromium during work-time
because the compile is so heavy on resources, that it considerably slows
down my work.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2020-09-11 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 20:50 bug#43075: Prioritize providing substitutes for security-critical packages with potentially long build times chaosmonk
2020-09-10 8:00 ` Ludovic Courtès
2020-09-10 9:19 ` zimoun
2020-09-11 0:47 ` Bengt Richter
2020-09-11 1:06 ` Mason Hock
2020-09-11 6:56 ` Ludovic Courtès
2020-09-11 7:37 ` zimoun
2020-09-11 8:23 ` Ricardo Wurmus
2020-09-11 13:39 ` Leo Famulari
2020-09-11 14:33 ` Dr. Arne Babenhauserheide [this message]
2020-09-11 14:45 ` Ludovic Courtès
2020-09-11 1:14 ` Mason Hock
2020-09-11 6:53 ` 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=87a6xwjsdf.fsf@web.de \
--to=arne_bab@web.de \
--cc=43075@debbugs.gnu.org \
--cc=chaosmonk@riseup.net \
--cc=zimon.toutoune@gmail.com \
/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).