From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Use OpenSSH in the bare-bones GuixSD template [was Re: how to "install" guixsd on a digitalocean server]
Date: Sat, 8 Apr 2017 21:42:17 -0400 [thread overview]
Message-ID: <20170409014217.GA15018@jasmine> (raw)
In-Reply-To: <87inmguh17.fsf@gnu.org>
On Fri, Apr 07, 2017 at 09:57:56PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Fri, Apr 07, 2017 at 02:07:16PM +0200, Andy Wingo wrote:
> >> (3) Why do we promote lsh by default? It took me quite some looking to
> >> figure out why my authorized_keys wasn't working. The fix was to
> >> just use OpenSSH.
> >
> > lsh is a GNU project and we did not have an OpenSSH service until a few
> > months ago. I'm in favor of changing the OS declaration templates to use
> > OpenSSH.
>
> I agree with this change (lsh upstream hasn’t been receiving the
> attention I was hoping for.)
Here's a patch for discussion.
next prev parent reply other threads:[~2017-04-09 1:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 12:07 how to "install" guixsd on a digitalocean server Andy Wingo
2017-04-07 12:27 ` ng0
2017-04-07 12:31 ` Pjotr Prins
2017-04-07 13:40 ` Leo Famulari
2017-04-07 13:42 ` Leo Famulari
2017-04-07 19:57 ` Ludovic Courtès
2017-04-09 1:42 ` Leo Famulari [this message]
2017-04-09 1:48 ` Use OpenSSH in the bare-bones GuixSD template [was Re: how to "install" guixsd on a digitalocean server] Leo Famulari
2017-04-09 9:08 ` ng0
2017-04-09 14:18 ` Leo Famulari
2017-04-09 14:21 ` ng0
2017-04-12 15:45 ` Leo Famulari
2017-04-07 14:04 ` how to "install" guixsd on a digitalocean server myglc2
2017-04-07 14:14 ` Andy Wingo
2017-04-07 14:31 ` ng0
2017-04-07 18:34 ` myglc2
2017-04-07 21:37 ` Ludovic Courtès
2017-04-13 15:28 ` ng0
2017-04-13 15:51 ` Andy Wingo
2017-04-13 16:06 ` 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
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=20170409014217.GA15018@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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.
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).