From: Tobias Geerinckx-Rice <me@tobias.gr>
To: phodina <phodina@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Providing/Submitting substitutes
Date: Thu, 16 Dec 2021 16:42:35 +0100 [thread overview]
Message-ID: <87o85ga6cv.fsf@nckx> (raw)
In-Reply-To: <J-BJnNwgpFsAqSVqZ9tZkEcC74Gv5s_2mSVhsnnbgKxEUgDyaDm3sIZTuWc5hCfPTAhPwTYydo0Da_CmD2cADujlBChcn8h0urLpB1xPHdE=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
Petr,
phodina via 写道:
> However, since I already built the browser and it took several
> hours
> I'd like to provide it also to other people.
That's very considerate of you. Thank you!
> Is there a way to submit the outputs of derivation to the
> official
> substitution server or the only way would be to make public my
> substitution server?
I'm afraid so (the latter). As you mention, this would require
trusting the other party but to an unreasonably degree: the
ability to redistribute arbitrary binaries, signed by the project,
to all Guix users.
That said, if your substitution server has decent uptime, traffic,
and a public IP, nothing's stopping you from putting up a
disclaimer page (like guix.tobias.gr… or better) and serving your
substitutes to others.
Adding the guix publish service is trivial, about as much work as
typing ‘guix archive --export’ once, and is a one-time effort!
</promo>
> Correct me if I'm wrong but can't this be solved be verified by
> using guix challenge?
In this case, I don't see how. Guix challenge is a valuable tool
but to use it in this way requires a fundamentally trusted party
(e.g., you, or say, bordeaux.guix.gnu.org) to be distributing
their own independently-built copy.
If that were the case you wouldn't have had to build it yourself.
So it could be used after the fact, or for general ‘hm, this is
interesting’ flagging for further research, and that's not good
enough here. Copies would have been distributed by then.
Challenges between 2 supposedly independent unofficial substitute
providers would be quite vulnerable to various kinds of
subversion.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-12-16 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:19 Providing/Submitting substitutes phodina via
2021-12-16 15:42 ` Tobias Geerinckx-Rice [this message]
2021-12-22 11:59 ` phodina
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=87o85ga6cv.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.com \
/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).