unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark Meyer <mark@ofosos.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: AWS + OpenStack support
Date: Fri, 14 Apr 2017 14:41:19 +0200	[thread overview]
Message-ID: <87wpanduvk.fsf@gnu.org> (raw)
In-Reply-To: <87k26ot90t.fsf@ofosos.org> (Mark Meyer's message of "Thu, 13 Apr 2017 21:14:26 +0200")

Hello,

Yes, feel free to take the register-user-SSH-keys task!  :-)

Mark Meyer <mark@ofosos.org> skribis:

>>>>>> "ng0" == ng0  <contact.ng0@cryptolab.net> writes:
>     ng0> It would be very welcome. This is currently one of two blocking
>     ng0> features I need until I can introduce GuixSD to IN-Berlin
>     ng0> e.V. (among other services they run virtual servers as a
>     ng0> non-profit).
>
> Concerning the OpenSSH configuration, if we don't want to create files
> in $HOME, it's possible to pass multiple AuthorizedKeysFile directives
> to the server, so this might be:
>
>  AuthorizedKeysFile %h/.ssh/authorized_keys /etc/ssh/%u/authorized_keys
>
> So that guix would control /etc/ssh/%u and you can alternatively add you
> own keys to $HOME/.ssh/authorized_keys.

So the default value for ‘AuthorizedKeysFile’ does not include
/etc/ssh/%u, right?

In that case, we don’t even need to add an entry to /etc and can
directly add something like:

  /gnu/store/…-sshd-authorized-keys

to the config file.

Ludo’.

      reply	other threads:[~2017-04-14 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 20:21 AWS + OpenStack support Mark Meyer
2017-04-11  4:16 ` Chris Marusich
2017-04-13 14:39 ` Ludovic Courtès
2017-04-13 15:02   ` Chris Marusich
2017-04-13 17:25     ` Mark Meyer
2017-04-14 12:39     ` Ludovic Courtès
2017-04-13 17:30   ` Mark Meyer
2017-04-13 17:34     ` ng0
2017-04-13 19:14       ` Mark Meyer
2017-04-14 12:41         ` Ludovic Courtès [this message]

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=87wpanduvk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mark@ofosos.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).