From: Julien Lepiller <julien@lepiller.eu>
To: 41907@debbugs.gnu.org, mail@ambrevar.xyz
Subject: bug#41907: [security] Substitutes fetched from server with no authorized key
Date: Wed, 17 Jun 2020 07:05:42 -0400 [thread overview]
Message-ID: <DDDA1FF9-4503-4547-BF17-CFA181DDD204@lepiller.eu> (raw)
In-Reply-To: <87k106nnwg.fsf@ambrevar.xyz>
Le 17 juin 2020 03:37:35 GMT-04:00, Pierre Neidhardt <mail@ambrevar.xyz> a écrit :
>I could be doing something wrong, but...
>
>1. Alice starts `guix publich -u ambrevar`.
>2. Bob, who did _not_ authorize Alice's signing key:
> - herd stop guix-daemon
>- guix-daemon --build-users-grouop=guixbuild
>--substitute-urls='http://10.0.0.4:8080 https://ci.guix.gnu.org'
> - guix build curl
>
>Result:
>
>--8<---------------cut here---------------start------------->8---
>downloading from http://10.0.0.4:8080/nar/gzip/...
>--8<---------------cut here---------------end--------------->8---
>
>Guix commit 8b00728144d0e4bbc740e1595c85f0ecee3f6fb0.
>
>Am I missing something or there is something really wrong?
There are two ways that you can get substitutes from unauthorized servers:
Substitutes for fixed-output derivations: guix lredy knows the result, so it doesn't need a signature, it checks the result (not sure this is a thing)
Substitutes that are reproducible. If you have a narinfo from an authorized build farm for a package in your local cache and alice's publish server proposes the same (name and checksum) substitute, you can download it. This is definitely a thing.
Other than that, guix should not use alice's substitutes.
next prev parent reply other threads:[~2020-06-17 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 7:37 bug#41907: [security] Substitutes fetched from server with no authorized key Pierre Neidhardt
2020-06-17 11:05 ` Julien Lepiller [this message]
2020-06-17 11:51 ` Pierre Neidhardt
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=DDDA1FF9-4503-4547-BF17-CFA181DDD204@lepiller.eu \
--to=julien@lepiller.eu \
--cc=41907@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.