From: John Darrington <john@darrington.wattle.id.au>
To: "Claes Wallin (?????????)" <gnu@clacke.user.lysator.liu.se>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: security concerns of using guix packages
Date: Sat, 4 Jul 2015 22:43:04 +0200 [thread overview]
Message-ID: <20150704204304.GA15555@jocasta.intra> (raw)
In-Reply-To: <CAGv_=BrtmBiGtWL5rMXVa6Zk=Ptrc7fTwyQeDxLuodVqCiumjA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Sat, Jul 04, 2015 at 09:51:22PM +0200, Claes Wallin (?????????) wrote:
On 04-Jul-2015 4:22 pm, "Ludovic Court??s" <ludo@gnu.org> wrote:
Still, if an installed package is not depending on the latest version of
the vulnerable package, the graft won't reach them. So there is still some
education and continuous information necessary if you want to be on top of
things.
This is true. However, one advantage of Guix is, that because of the rollback mechanism,
if you suddenly hear that there was a gaping great security hole introduced into package foo
in version 1.2.3 and no fix is yet available, it is very easy to rollback to version 1.2.2
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-07-04 20:43 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
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 [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=20150704204304.GA15555@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=gnu@clacke.user.lysator.liu.se \
--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 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).