From: myglc2 <myglc2@gmail.com>
To: guix-devel@gnu.org
Subject: Re: It’s building!
Date: Tue, 31 Jan 2017 21:47:47 -0500 [thread overview]
Message-ID: <8660kud3u4.fsf@gmail.com> (raw)
In-Reply-To: <8737goz2ba.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 12 Jan 2017 17:10:49 +0100")
On 01/12/2017 at 17:10 Ludovic Courtès writes:
> Hello Guix!
>
> Good news: the new machine, bayfront.guixsd.org, is building Guix master
> for x86_64/i686 with Cuirass⁰!
>
> You can get substitutes from https://bayfront.guixsd.org; just authorize
> its key (with ‘guix archive --authorize’), which is:
>
> (public-key
> (ecc
> (curve Ed25519)
> (q #8D156F295D24B0D9A86FA5741A840FF2D24F60F7B6C4134814AD55625971B394#)))
Hi Ludo, I have a couple questions. I autorized bayfront like so ...
g1@g1 ~/src$ cat bayfront.guixsd.org.pub
(public-key
(ecc
(curve Ed25519)
(q #8D156F295D24B0D9A86FA5741A840FF2D24F60F7B6C4134814AD55625971B394#)))
g1@g1 ~/src$ sudo guix archive --authorize < bayfront.guixsd.org.pub
... and I read this ...
3.7 Invoking ‘guix archive’
===========================
[...]
The list of authorized keys is kept in the human-editable file
‘/etc/guix/acl’. The file contains “advanced-format s-expressions”
(http://people.csail.mit.edu/rivest/Sexp.txt) and is structured as
an access-control list in the Simple Public-Key Infrastructure
(SPKI) (http://theworld.com/~cme/spki.txt).
... so I expected to find the bayfront key here ...
g1@g1 ~/src$ sudo cat /etc/guix/acl
(acl
(entry
(public-key
(rsa
(n #00DB1634E3D9DFAC97AE4734DAE968CCB15EE4815C82BDC254883DBB49FE1EF32268E82D4BBE0E35298C481C9DA1551642FAFF05AEC1A60712F1BB4BE7D25D7EFF7A4F89704A5A9AC232870CB9F2476C3B538A0E990A8825DEB73081D317001FB8A188600F2FEF5F5F570E857F3EE4355077A3C3918ED72723A56BA55C466D400658974D7DAD1F6B7B63C192B9C2704D98BBFF1C3BD5B8EF11A8ADC83ACB8FD8E9F1E792FDAD262415D13F2DEE55F330908CFDA9C3C8C32B64F7DD088457D34F445E2E2C83C6D680549DC9B6E6573B89496567204ED285E67A279F2F667080BA941D80D015CE87B0FB6A91A99CECC7D91D2D210B00E4B6E611DA51DB008F1DFE3FCAC6B27393FA781D45F9A15FC7B8785A3E86BA6592B2916CA22CF1E40FC85F85CACA590461154F58F3580B16398908EF32076F411299C28727C94D88B6A618F84DD73AEBED8270BCB6690928CB1BF250C35E1F6BF3B1B30D05BA246ECE8F69D9065DE26F4B3E0D814D70A9C27CB5B7B050C9090590D3A9EF83374F2643E5446FBD39DDB124DBF6DFDAA6D18E2560AD0CBFA11C959C9B7316BF19963A191967054E9FD97DC14D71082B30B1C90A46E8996682474C3BCB51BA0882958897B6DD35E41B5174D0A6BCDE97B89043E95BD1B70DE61DA666893B417196A180005466BC3A742FDF04E89B04460E3E6BC72E7F1B5FEA5B3092FEE551A3C447C12E104E65#)
(e #010001#)
)
)
(tag
(guix import)
)
)
)
... but no. Where did it go?
Also you recommended ...
> guix challenge gdk-pixbuf \
> --substitute-urls="https://mirror.hydra.gnu.org https://bayfront.guixsd.org"
... which I tried _before_ I had authorized bayfront. I was surprised that it
worked before authorization. Should it?
TIA - George
next prev parent reply other threads:[~2017-02-01 2:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:10 It’s building! Ludovic Courtès
2017-01-12 16:23 ` Kei Kebreau
2017-01-12 17:18 ` David Craven
2017-01-12 17:31 ` Alex Sassmannshausen
2017-01-15 22:32 ` Ludovic Courtès
2017-02-01 2:47 ` myglc2 [this message]
2017-02-09 16:36 ` Archive authentication & ‘guix challenge’ Ludovic Courtès
2017-02-10 22:57 ` myglc2
2017-02-11 14:32 ` Ludovic Courtès
2017-02-11 21:56 ` myglc2
2017-02-13 2:15 ` Maxim Cournoyer
2017-02-13 14:05 ` Ludovic Courtès
2017-02-13 17:13 ` myglc2
2017-02-14 9:20 ` Ludovic Courtès
2017-02-14 15:34 ` myglc2
2017-02-14 16:29 ` Ludovic Courtès
2017-02-14 23:16 ` myglc2
2017-02-14 17:43 ` Maxim Cournoyer
2017-02-14 23:29 ` myglc2
2017-02-14 5:55 ` Maxim Cournoyer
2017-02-10 23:01 ` myglc2
-- strict thread matches above, loose matches on Subject: below --
2017-01-20 6:28 It’s building! Maxim Cournoyer
2017-01-22 13:10 ` ng0
2017-01-22 16:02 ` 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
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=8660kud3u4.fsf@gmail.com \
--to=myglc2@gmail.com \
--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).