From: Maxime Devos <maximedevos@telenet.be>
To: "Marek Paśnikowski" <mail@marekpasnikowski.name>, 54711@debbugs.gnu.org
Subject: bug#54711: Bad Documentation Series: 6.1 Specifying Additional Channels
Date: Mon, 04 Apr 2022 21:54:24 +0200 [thread overview]
Message-ID: <ae30f1b5875a0de5697ad9b9da89c665ba8dd510.camel@telenet.be> (raw)
In-Reply-To: <4b4fb5fcf67ee63c9899f43e9653b1cfd689dd26.camel@marekpasnikowski.name>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Marek Paśnikowski schreef op ma 04-04-2022 om 20:43 [+0200]:
> 2. If I create my own channel from scratch,
> then I have to authorize it with my key.
> Thus I know the commit and the key fingerprint.
You don't have to do any authorization -- you can skip .guix-
authorization and channel introductions. However, by skipping this,
you lose some nice security properties, so I cannot recommend this if
the channel is published over the Internet or something for other
people. But if it's purely local, then skipping it is probably fine.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-04 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 16:21 bug#54711: Bad Documentation Series: 6.1 Specifying Additional Channels Marek Paśnikowski
2022-04-04 17:53 ` Maxime Devos
2022-04-04 18:13 ` Maxime Devos
2022-04-04 17:55 ` Maxime Devos
2022-04-04 17:58 ` Maxime Devos
2022-04-04 18:02 ` Maxime Devos
2022-04-04 18:08 ` Maxime Devos
2022-04-04 18:43 ` Marek Paśnikowski
2022-04-04 19:47 ` Maxime Devos
2022-04-04 19:51 ` Maxime Devos
2022-04-04 19:52 ` Maxime Devos
2022-04-04 19:54 ` Maxime Devos [this message]
2022-04-10 12:55 ` Marek Paśnikowski
2022-04-10 13:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-04-10 13:54 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-04-10 16:27 ` Marek Paśnikowski
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=ae30f1b5875a0de5697ad9b9da89c665ba8dd510.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54711@debbugs.gnu.org \
--cc=mail@marekpasnikowski.name \
/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.