all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Claes Wallin (韋嘉誠)" <clacke+gmail@lysator.liu.se>
Cc: guix-devel <guix-devel@gnu.org>, "McGee, Jenny" <jmc@stowers.org>
Subject: Re: security concerns of using guix packages
Date: Sat, 04 Jul 2015 16:32:01 +0200	[thread overview]
Message-ID: <87h9pkt2n2.fsf@gnu.org> (raw)
In-Reply-To: <CAGv_=BrW4PA8n9Ua6n6foFDKX9W5pMZ-avqPeM+m96AzknZgdg@mail.gmail.com> ("Claes Wallin \=\?utf-8\?B\?KOmfi+WYieiqoCkiJ3M\=\?\= message of "Fri, 3 Jul 2015 07:40:59 +0200")

"Claes Wallin (韋嘉誠)" <clacke+gmail@lysator.liu.se> skribis:

> If I'm interpreting the OP's IT department correctly, this is not about
> trusting guix or Red Hat regarding malice, not about binaries and
> substitutions, but regarding competence and diligence, and the package
> tree. If there are important patches coming out, will they get into
> guix/Red Hat fast enough and will they get to users fast enough?

That’s a valid concern, and there’s not much we can say other than we’ve
been doing our best and will continue to do so.

That said, sysadmins don’t have to wait for upstream Guix to provide the
patch; in case of urgency, they could easily add the necessary patches
to, say,
<http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/openssl.scm#n29>,
upgrade their software, and share the patch with upstream Guix.

Of course that would be a last resort, and I hope users don’t run into
it.  But what it means is that users are more independent than with a
traditional distro.

Ludo’.

  reply	other threads:[~2015-07-04 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  0:38 security concerns of using guix packages Cook, Malcolm
2015-07-03  4:44 ` John Darrington
2015-07-03  5:40   ` Claes Wallin (韋嘉誠)
2015-07-04 14:32     ` Ludovic Courtès [this message]
2015-07-04 13:50 ` Pjotr Prins
2015-07-04 14:22 ` Ludovic Courtès
2015-07-04 14:37   ` Pjotr Prins
2015-07-04 19:51   ` Claes Wallin (韋嘉誠)
2015-07-04 20:43     ` John Darrington

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=87h9pkt2n2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=clacke+gmail@lysator.liu.se \
    --cc=guix-devel@gnu.org \
    --cc=jmc@stowers.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.