all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41767@debbugs.gnu.org
Subject: [bug#41767] [PATCH 0/9] Authenticate channels
Date: Sun, 14 Jun 2020 15:51:36 +0200	[thread overview]
Message-ID: <87mu55vjpz.fsf@gnu.org> (raw)
In-Reply-To: <86ftaznqeq.fsf@gmail.com> (zimoun's message of "Sat, 13 Jun 2020 13:42:05 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

>>> 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
>>>
>>> In this case, do I have to use the option '--disable-authentication'?
>>
>> Yes, you can always use it.
>
> "Qui peut le plus peut le moins." ;-)
>
> The question is: is it mandatory?

If you have a local fork with unauthorized commits (for instance, you
made commits yourself and you’re not listed in ‘.guix-authorizations’)
then yes, you have to use ‘--disable-authentication’.

The alternative for you would be to publish an introduction for your
fork, which means you would be able to test which is the first commit to
authenticate.

However, this may be inconvenient for one-off forks where you just want
to test changes.  In that case, ./pre-inst-env probably remains the
preferred approach.

Thanks,
Ludo’.




  reply	other threads:[~2020-06-14 13:52 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
2020-06-09 14:16   ` Ludovic Courtès
2020-06-13 11:42     ` zimoun
2020-06-14 13:51       ` Ludovic Courtès [this message]
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=87mu55vjpz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41767@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.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.
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.