unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: George myglc2 Clemmer <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How best to set host key in vm
Date: Thu, 15 Feb 2018 10:21:01 -0500	[thread overview]
Message-ID: <867ere9t42.fsf@gmail.com> (raw)
In-Reply-To: <87h8qi8fwg.fsf@gnu.org>

Hi Ludo’,

On 02/15/2018 at 14:51 Ludovic Courtès writes:

> George myglc2 Clemmer <myglc2@gmail.com> skribis:
>
>> On 02/09/2018 at 11:02 Ludovic Courtès writes:
>>
>>> George myglc2 Clemmer <myglc2@gmail.com> skribis:
>>>
>>>> I want to set the host key in 'guix system vm-image' so that updating a
>>>> VM config does not break that VM's host key entry in my client machine
>>>> ~/.ssh/knownhosts files.  AFAIK there is no direct way to do this. I
>>>> tried this ...
>>
>>> The recommendation in this case is to use “out-of-band” storage—i.e.,
>>> have the secrets stored in a place other than the store.
>>>
>>> For example, you could have an activation snippet that copies secret
>>> files directly to /etc, along these lines (untested):
>>>
>>>   (simple-service 'copy-private-key activation-service-type
>>>                   (with-imported-modules '((guix build utils))
>>>                     #~(begin
>>>                         (use-modules (guix build utils))
>>>                         (mkdir-p "/etc/ssh")
>>>                         (copy-file "/root/secrets/ssh_host_ed25519_key"
>>>                                    "/etc/ssh/ssh_host_ed25519_key'))))
>>>
>>> That means you have to arrange for /root/secrets/ssh_host_ed25519_key to
>>> exist in the first place, but that’s pretty much all we can do.
>>
>> Thank you. So what is an easily-automated way to populate /root/secrets?
>
> Guix doesn’t have any helper module/tool for that yet.
>
> Perhaps ‘guix system vm-image’ could include a ‘--copy’ option that
> would copy a file from the host into the image.  We’d have to be careful
> with the implementation to make sure that it doesn’t end up in the host
> store nor in the guest store.

How about a '--copy-image=<imagefile>' option that copies the image out
of the store? Then the ‘--copy’ could operate on <imagefile> and fail
if it isn't specified.

- George

  reply	other threads:[~2018-02-15 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 20:58 How best to set host key in vm George myglc2 Clemmer
2018-02-09 11:02 ` Ludovic Courtès
2018-02-09 17:55   ` George myglc2 Clemmer
2018-02-15 14:51     ` Ludovic Courtès
2018-02-15 15:21       ` George myglc2 Clemmer [this message]
2018-02-16 10:17         ` 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=867ere9t42.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@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.
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).