From: ng0 <ng0@infotropique.org>
To: 27388@debbugs.gnu.org
Subject: bug#27388: offloading: Add support for keyfile-less keys as used by GnuPG
Date: Mon, 3 Jul 2017 22:16:56 +0000 [thread overview]
Message-ID: <20170703221656.3lhbbpvqs2ynh3ib@abyayala> (raw)
In-Reply-To: <20170615191359.ysym3dv4c7f5lwek@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
ng0 transcribed 2.6K bytes:
> ng0 transcribed 2.3K bytes:
> > At the moment the field (private-key) in /etc/guix/machines.scm expects
> > to be a file.
> > When you use GnuPG authentication keys for ssh logins, you have no
> > pubkey file, but you have a very long pubkey which can be used with
> > ~/.ssh/authorized_keys and similar mechanisms.
> >
> > Example:
> >
> > user@abyayala ~/src/guix/guix$ cat /etc/guix/machines.scm
> > (list (build-machine
> > …
> > (privat-key "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDgRM0G+Dnl/wlrHNb9sr3/yW9tHA8weIbwvfly/NRW6LHSLIPvsLksabVQsYbUH6i2aK2ZlE3Oo+H/R2wrs7dmVCo57O4MbZk8Kb0fatN3qhq6g/+bNobVIexS5XN6g5JcmXM4ZzR8Q0rEd46oaxFWy8nDSw4RR1d+OU5/Z/LHR1VUTCQKU0Q1Jv//4YFVq/BEf6oj4SU9+/Li9kUo9f++i4PaiWyrQDm1FAYtMGW5MBKH3ohO1dlPgqNjdeqTjZfgvCMPdbyV6Xwtz7KVkCR0+r9u7JefCCKUXL3Ap4VPtjhyCLoRuqJ+ZIp9XR2wf3rVGR6KRcLWPEXLkGfAPCs+7uAnfReBxNiWYt+FHuQpeyUld8u8E0G8u9FSf/l25A85QrQK0EUrVHdFc1q8tcCeq0EomoIPl7GnwtDIwYmkWtViCz0ivVRvNBUTXvq0XtI/9kLgcBgKfzap8dLeVSXJrUhYlbcOZNnstzkmut1ce8my5TwSRzr2dxgUF8563cM3cdLu+C9bdMWvR/s4xwu6Q5opbehdFHd2Hj/Lnqv+xwNKNFkhZCHiyum8L/VKQAsboXgJ7/sB7CHsEcBif73RWj3bFcMnPHHlJgxXB1aOH4kM+y6fF8wW/bGC/9gGiYXzovdbopv3B89oyuT73aoXg4TIPz6gv6Bg1OiGpfseGw== (none)")
> > …
>
> Actually this might be the wrong approach.
>
> The key you see above is the public key equivalent to the ssh pubkey.
> The private key is only in the GnuPG keyring.
>
> Solution for this kind of situations are welcome. For now I'll use
> ssh pubkeys.
> --
> ng0
> OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> https://krosos.org/~/ng0/ https://www.infotropique.org
Ignore the second message in this thread. I tried to provide
a possible solution which lead to the believe that this is
considered solved. It isn't. This wishlist bug is still wanted.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-03 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o9ta7c9g.fsf@gnu.org>
2017-06-15 18:56 ` bug#27388: offloading: Add support for keyfile-less keys as used by GnuPG ng0
2017-06-15 19:13 ` ng0
2017-07-03 22:16 ` ng0 [this message]
[not found] ` <handler.27388.C.14985070652097.notifdonectrl.0@debbugs.gnu.org>
2017-06-26 21:17 ` bug#27388: acknowledged by developer (control message for bug #27388) ng0
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=20170703221656.3lhbbpvqs2ynh3ib@abyayala \
--to=ng0@infotropique.org \
--cc=27388@debbugs.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.