From: Chris Marusich <cmmarusich@gmail.com>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 30143@debbugs.gnu.org
Subject: bug#30143: UX: print warning if substitute server is not authorized
Date: Sun, 21 Jan 2018 23:08:39 -0800 [thread overview]
Message-ID: <87a7x6xte0.fsf@gmail.com> (raw)
In-Reply-To: <idjpo681xyo.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 17 Jan 2018 13:17:19 +0100")
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Suppose I add example.com as a substitute server by passing
> “--substitute-urls=https://example.com” to the daemon or the Guix
> command line. I haven’t authorized the signing key, so Guix won’t
> accept any of the substitutes from example.com.
>
> Currently, Guix does not make it obvious to the user that a requested
> substitute server is ignored because its key is not authorized. We
> should print a clear warning in this case.
>
> (guix scripts authenticate) already includes “validate-signature”, which
> aborts with an error if the key is not authorized, but we don’t seem to
> use it.
What if example.com serves substitutes that are signed by another
server, such as hydra.gnu.org? No matter where a substitute comes from,
if it was signed with an authorized key and its signature checks out,
then it's OK to use, right?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-22 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 12:17 bug#30143: UX: print warning if substitute server is not authorized Ricardo Wurmus
2018-01-22 7:08 ` Chris Marusich [this message]
2018-01-23 6:50 ` Ricardo Wurmus
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=87a7x6xte0.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=30143@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.