From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Oleg Pykhalov" <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix support in cachix
Date: Wed, 04 Jul 2018 16:17:35 +0200 [thread overview]
Message-ID: <87in5v84qo.fsf@fastmail.com> (raw)
In-Reply-To: <87h8lgf0o3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> Oleg Pykhalov <go.wigust@gmail.com> skribis:
>
>> Domen Kožar <domen@dev.si> recently was in #guix (IRC) 2 days ago asking
>> about support of Guix in cachix. Also he opened an issue on GitHub:
>>
>>> I'm opening this issue for interest around supporting Guix.
>>
>> [1] https://github.com/cachix/cachix/issues/85
>
> Cachix looks interesting! It’s good to collaboratively provide
> binaries. It’s easier than having everyone set up ‘guix publish’, at
> the cost of being more centralized.
>
> The “cachix use <name>” example on https://cachix.org/ glosses over
> security “details” though. I wonder how one gets to authenticate a
> particular user of Cachix and to authorize binaries coming from them.
> There’s also the issue that said user could be publishing binaries they
> themselves obtained from a source that you do not trust yourself. Tough
> issues!
I asked about discovering signing keys and apparently you'll find it at
https://<user>.cachix.net, and that's the substitute URL too.
It looks useful for those who don't want to or can't publish their own
substitutes. And `guix challenge` makes it easy to verify the builds
coming from a particular "channel".
I would not want to publish all my builds there, though. Not sure how
it would be integrated on the client side.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-07-04 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:49 Guix support in cachix Oleg Pykhalov
2018-07-03 21:51 ` Ludovic Courtès
2018-07-04 14:17 ` Marius Bakke [this message]
2018-07-11 11:09 ` Ludovic Courtès
2018-07-13 13:31 ` Nils Gillmann
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=87in5v84qo.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.