From: George myglc2 Clemmer <myglc2@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: How best to set host key in vm
Date: Tue, 06 Feb 2018 15:58:16 -0500 [thread overview]
Message-ID: <86tvut25uf.fsf@gmail.com> (raw)
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 ...
(services (cons*
[...]
(extra-special-file "/etc/ssh/ssh_host_ed25519_key"
(local-file "ssh_host_ed25519_key"))
(extra-special-file "/etc/ssh/ssh_host_ed25519_key.pub"
(local-file "ssh_host_ed25519_key.pub"))
)
... which does work but naturally throws errors ...
localhost sshd[236]: error: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
localhost sshd[236]: error: @ WARNING: UNPROTECTED PRIVATE KEY FILE! @
localhost sshd[236]: error: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
localhost sshd[236]: error: Permissions 0444 for '/etc/ssh/ssh_host_ed25519_key' are too open.
localhost sshd[236]: error: It is required that your private key files are NOT accessible by others.
localhost sshd[236]: error: This private key will be ignored.
localhost sshd[236]: error: key_load_private: bad permissions localhost sshd[236]: error: Could not load host key:/etc/ssh/ssh_host_ed25519_key
localhost sshd[236]: Accepted publickey for g1 from 192.168.1.14 port 56311 ssh2: RSA SHA256:RAXP4+5SU3UN09NL+QwkQmAsLIoDa8Wq6Bi61DzUScY
When I specifyed only the public key, new private and public keys were
generated by, I guess, the first boot.
Suggestions? TIA - George
next reply other threads:[~2018-02-06 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 20:58 George myglc2 Clemmer [this message]
2018-02-09 11:02 ` How best to set host key in vm 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
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=86tvut25uf.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@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).