unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, help-guix@gnu.org
Subject: Re: Security of packages in official repo
Date: Thu, 26 Nov 2020 17:01:46 +0100	[thread overview]
Message-ID: <86eekgrtsl.fsf@gmail.com> (raw)
In-Reply-To: <855z5sqoxm.fsf@beadling.co.uk>

Hi,

On Thu, 26 Nov 2020 at 12:32, Phil <phil@beadling.co.uk> wrote:

> However, can anyone point me to, or explain - what is done to audit
> packages in the official Repo in the first place - i.e. how do I know
> that a piece of software supplied to me by Guix is not only
> delivered in a safe/reliable fashion, but is also free from malware potentially
> introduced by the authors/maintainers themselves?

Nothing.  It is about trust, as with any distribution.  Now, you can
audit by yourself the source code, compiled by yourself and check if it
is the same that the substitutes serve you.

  # get the source
  guix build -S foo

  # build (fetch substitutes by default)
  guix build foo

  # re-build
  guix build foo --no-grafts --check

And if the binaries are different, it means unreproducibility are
around; which implies weakness (unsafe is too strong).

Note “guix challenge” allows to compare what is build locally and
what is served by the build farm.

An experimental service is running to detect unreproducibility between
the different build farms.  For example scripts are floating around [1].

Moreover, if you are in paranoid mode, then you have to start to verify
the bootstrap chain and the initial binary seed; ~60MB in Guix if I
remember correctly and too much for Ubuntu and co.


1: <https://yhetil.org/guix-devel/86mu0rt95k.fsf@gmail.com>


> How are new packages or updates audited or reviewed before being accepted
> into Guix's official repo?
>
> It's a paranoid question I know - but it's a regular one on security
> audits to sign-off software use....  I know that nobody is going to audit
> every single line of code of every package, but knowing that some
> process exist is normally enough to satisfy the audit?

There is no formal process, AFAIK.  But since no one wants craps running
on their machine, we can guess it is informally done. :-)


> A similar question and fairly reassuring answer from the Ubuntu Security
> Team is given here - I was hoping to find something similar for Guix:
> https://askubuntu.com/questions/1186039/are-ubuntu-packages-security-audited

I will not comment on this because it is a trap.  You have no insurance
(the ability to check) that the source code they audited corresponds to
the binary you fetch and then run.

Pedestrian video explaining that is here: <https://youtu.be/I2iShmUTEl8>

(Sorry, maybe the video is on a platform more respectful but I am too
lazy to search.)


AFAIK, Guix is one the most advanced tool to check paranoid questions.

Last, if you are talking about CVE and security updates, they are pushed
to master as soon as possible, IIUC.

Hope that helps,
simon


  reply	other threads:[~2020-11-26 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 12:32 Security of packages in official repo Phil
2020-11-26 16:01 ` zimoun [this message]
2020-11-26 16:51   ` Ricardo Wurmus
2020-11-26 19:30     ` zimoun
2020-11-26 21:10       ` Ricardo Wurmus
2020-11-26 21:35         ` zimoun
2020-11-26 19:07   ` Phil
2020-11-26 19:50     ` zimoun

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=86eekgrtsl.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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.
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).