Re: Authenticate a channel

["Marek Paśnikowski" <marek@marekpasnikowski.pl>]

> >dim. 29 déc. 2024 at 14:04, Marcel van der Boom <marcel@hsdev.com> wrote:
> > I have issues with this too. On every git pull and guix pull I get
> > messages that my key is missing, although I did add it locally to the
> > keyring branch.
> > 
> > Is there a procedure documented somewhere on how to make sure the
> > signature is present and correct? It feels like I am just missing
> > something small here.
> 
> Most up to date documentation is here,
> 
> https://guix.gnu.org/manual/devel/en/html_node/Specifying-Channel-Authorizat
> ions.html
> > Some unknowns for me:
> > - are subkeys supported? anything special needed?
> > - it seems there is a file-naming convention on the keyring branch for the
> > keys? - do i need to pull the keyring in manually over time of does the
> > machinery take care of> 
> >  this?
> 
> Have you checked with other public channels ?
> 
> --
> Cayetano Santos
> GnuPG Key:   https://meta.sr.ht/~csantosb.pgp
> FingerPrint: CCB8 1842 F9D7 058E CD67 377A BF5C DF4D F6BF 6682

I looked at Jeko’s channel and noticed one discrepancy from my working setup.

The key file has a wrong name extension.

From documentation:

Additionally, your channel must provide all the OpenPGP keys that were ever 
mentioned in .guix-authorizations, stored as .key files, which can be either 
binary or “ASCII-armored”.

In Jeko’s case, the key is stored in a jeko-A2E0F15D.asc file, which breaks 
the documented assumption. My key is named marekpasnikowski.key , for 
reference.

Hopefully, the name problem is the only problem here.

I also share the opinion that the documentation is written in a confusing 
style, especially for novices.