unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 26695@debbugs.gnu.org
Subject: bug#26695: openssh password-authentication? should be #f by default
Date: Fri, 28 Apr 2017 19:23:50 +0200	[thread overview]
Message-ID: <87efwcbg49.fsf@fastmail.com> (raw)
In-Reply-To: <87h9184heg.fsf@dustycloud.org>

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

Christopher Allan Webber <cwebber@dustycloud.org> writes:

> Maxim Cournoyer writes:
>
>> +1. Although it means the keys will have to be copied by another mean
>> than the "ssh-copy-id" script. Maybe the configuration could accept
>> the public key? :) I haven't checked if this is already possible.
>
> We have discussed in the past having some service that just copies some
> static files on init.  That would be enough to set up public keys
> appropriately.

I think that can already be done with 'special-file-service-type'.

https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00332.html

Another approach could be a small program that reads a configuration
file and can also pull from e.g. the ec2 metadata service which should
work with many "cloud" providers. Similar to "cloud-init" but Guile of
course :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2017-04-28 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 14:37 bug#26695: openssh password-authentication? should be #f by default Christopher Allan Webber
2017-04-28 16:09 ` Maxim Cournoyer
2017-04-28 16:37   ` Christopher Allan Webber
2017-04-28 16:40     ` Maxim Cournoyer
2017-04-28 17:23     ` Marius Bakke [this message]
2017-04-28 18:25       ` Christopher Allan Webber
2017-04-30 19:47       ` Chris Marusich
2017-04-28 19:28 ` Leo Famulari
2023-08-29  3:24   ` Maxim Cournoyer

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=87efwcbg49.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=26695@debbugs.gnu.org \
    --cc=cwebber@dustycloud.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).