all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41767@debbugs.gnu.org
Subject: [bug#41767] [PATCH 0/9] Authenticate channels
Date: Tue, 9 Jun 2020 12:52:38 +0200	[thread overview]
Message-ID: <CAJ3okZ0dqFbpQJ7OHCSpA5Evp7Rsfs5M4dB=pQDXkRwWtGsm=w@mail.gmail.com> (raw)
In-Reply-To: <20200608215224.2672-1-ludo@gnu.org>

Hi Ludo

(-22883@debbugs.gnu.org)

On Mon, 8 Jun 2020 at 23:53, Ludovic Courtès <ludo@gnu.org> wrote:

> I would much welcome feedback!  I’m happy to answer questions if
> anything’s unclear.  Don’t hesitate, because after that it’ll be
> harder to change!

I am sorry to be slow to understand and if I am naive but there are
still points which are unclear [1] to me, especially when 'guix
time-machine' will use this authentication machinery.

[1] https://lists.gnu.org/archive/html/guix-devel/2020-06/msg00057.html


From my understanding, there are 4 situations

 1- add signed material to a signed channel
 2- introduce authentication to an unsigned channel
 3- add unsigned material to a signed channel
 4- add unsigned material to unsigned channel

And I am interested by how it works for the situation #3.  For a
concrete example of 3., e.g.,

--8<---------------cut here---------------start------------->8---
git clone https://git.savannah.gnu.org/git/guix.git
git worktree add -b foo wk/foo
cd wk/foo
# add my unready stuff
./pre-inst-env guix pull --branch=foo --url=$PWS -p /tmp/foo
/tmp/foo/bin/guix install unready-stuff
--8<---------------cut here---------------end--------------->8---

In this case, do I have to use the option '--disable-authentication'?
And this is the scenario for almost all the patches on guix-patches;
even if 'pull' is generally not necessary when testing the patch. :-)

Another example is let consider that this channel [2] -- or any other
public one used by labs to publish specific tools; I am not aware
about one by INRIA ;-) -- and let imagine that this channel is
authenticated, i.e., there is a '.guix-authorizations' file.  Now, can
I fork this channel and my unsigned material without entering in the
security dance?  Do I need to use the option
'--disable-authentication'?

Moreover, if this forked channel is added to
'~/.config/guix/channels.scm', i.e., in addition to
'%default-channel', what happens for pulling?  Well, it is not
possible to pull a signed channel and an "unauthorized fork from a
signed channel" in only one command, right?

[2] https://github.com/BIMSBbioinfo/guix-bimsb


Well, I am sorry to be insistent but this authentication machinery
seems having an hard implication in my workflow and I would like to be
prepared.

All the best,
simon




  parent reply	other threads:[~2020-06-09 10:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 21:52 [bug#41767] [PATCH 0/9] Authenticate channels Ludovic Courtès
2020-06-08 22:02 ` [bug#41767] [PATCH 1/9] git-authenticate: Cache takes a key parameter Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 2/9] git-authenticate: 'authenticate-commits' takes a #:keyring parameter Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 3/9] tests: Move OpenPGP helpers to (guix tests gnupg) Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 4/9] channels: 'latest-channel-instance' authenticates Git checkouts Ludovic Courtès
2020-06-09 17:49     ` Maxim Cournoyer
2020-06-11  9:24       ` Ludovic Courtès
2020-06-11 13:15         ` Maxim Cournoyer
2020-06-08 22:02   ` [bug#41767] [PATCH 5/9] channels: Make 'validate-pull' call right after clone/pull Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 6/9] .guix-channel: Add 'keyring-reference' Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 7/9] channels: Automatically add introduction for the official 'guix' channel Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 8/9] pull: Add '--disable-authentication' Ludovic Courtès
2020-06-08 22:02   ` [bug#41767] [PATCH 9/9] DROP? channels: Add prehistorical authorizations to <channel-introduction> Ludovic Courtès
2020-06-09 18:35     ` Maxim Cournoyer
2020-06-10 13:21       ` Ludovic Courtès
2020-06-09  7:15 ` [bug#41767] [PATCH 0/9] Authenticate channels Ludovic Courtès
2020-06-09 10:52 ` zimoun [this message]
2020-06-09 14:16   ` Ludovic Courtès
2020-06-13 11:42     ` zimoun
2020-06-14 13:51       ` Ludovic Courtès
2020-06-13  9:46 ` Ludovic Courtès
2020-06-16 14:22 ` bug#41767: " Ludovic Courtès
2020-06-16 14:34   ` bug#22883: [bug#41767] " Ludovic Courtès

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='CAJ3okZ0dqFbpQJ7OHCSpA5Evp7Rsfs5M4dB=pQDXkRwWtGsm=w@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=41767@debbugs.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.