unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: guix-devel@gnu.org
Subject: Using G-Expressions for public keys (substitutes and possibly more)
Date: Sun, 17 Oct 2021 14:47:21 +0200	[thread overview]
Message-ID: <5f7e587c376ed0abffa321152e185cbf4014e05b.camel@gmail.com> (raw)

Hi Guix,

let's say I wanted to add my own substitute server to my config.scm. 
At the time of writing, I would have to add said server's public key to
the authorized-keys of my guix-configuration like so:
  (cons* (local-file "my-key.pub") %default-authorized-guix-keys)
or similarily with append.  This local-file incantation is however
pretty weak.  It changes based on the current working directory and
even if I were to use an absolute path, I'd have to copy both that file
and the config.scm to a new machine were I to use the same
configuration there as well.

However, it turns out that the format for said key files is some
actually pretty readable Lisp-esque stuff.  For instance, an ECC key
reads like
  (public-key (ecc (curve CURVE) (q #Q#)))
with spaces omitted for simplicity.
Were it not for the (q #Q#) bit, we could construct it using scheme-
file.  In fact, it is so simple that in my local config I now do
exactly that.

(define-record-type* <ecc-key> ...)
(define-gexp-compiler (ecc-key-compiler (ecc-key <ecc-key>) ...) ...)

(ecc-key
  (name "my-key.pub")
  (curve 'Ed25519)
  (q "ABCDE..."))

Could/should we support such formats out of the box?  WDYT?

Regards,
Liliana



             reply	other threads:[~2021-10-17 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 12:47 Liliana Marie Prikler [this message]
2021-10-21 20:13 ` Using G-Expressions for public keys (substitutes and possibly more) Ludovic Courtès
2021-10-22  4:47   ` Liliana Marie Prikler
2021-11-21  0:12     ` Jelle Licht
2021-11-21  8:28       ` Liliana Marie Prikler
2021-11-22 13:27         ` Ludovic Courtès
2021-11-22 14:32           ` Jelle Licht
2021-11-22 19:35           ` Liliana Marie Prikler
2021-11-23 17:14             ` 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

  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=5f7e587c376ed0abffa321152e185cbf4014e05b.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).