From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] getting 9front ssh to use RSA key?
Date: Mon, 25 Jan 2021 19:08:43 -0800 [thread overview]
Message-ID: <680018982E4780C52664493EFBC797A6@eigenstate.org> (raw)
In-Reply-To: <20210125.193425.1816358441470322534.dworkin@weaselfish.com>
Quoth Dworkin Muller <dlm-9fans@weaselfish.com>:
> On Tue, 26 Jan 2021 12:24:35 +1030, Alex Musolino <alex@musolino.id.au> wrote:
> alex> You're missing the 'role=client' tuple.
>
> You are exactly correct. Looks like rsa(8) has a bug in its example
> for generating and installing a fresh key for a remote Unix system, in
> that it says to use:
>
> auth/rsagen -t 'service=ssh' >key
> auth/rsa2ssh key | ssh unix 'cat >>.ssh/authorized_keys'
> cat key >/mnt/factotum/ctl
> ssh unix
>
> Inferring from the example generating a tinc host key, it appears that
> the first line should instead be:
>
> auth/rsagen -t 'service=ssh role=client' >key
>
> Thank you *very* much for catching that.
>
> Dworkin
Now, I'm confused. The example just works for me -- and
I use ssh to get into my linux and openbsd machines on
a daily basis.
I also just spun up a FreeBSD 12.1 vm on vultr to test,
and it just worked out of the box for me. (I assume you're
on 12.2, but that wasn't an option -- the update is
currently running)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td072863a97c9d3e9-Mf20b55b72d8ec45320e81836
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-26 3:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 6:23 Dworkin Muller
2021-01-25 6:33 ` ori
2021-01-25 7:56 ` Dworkin Muller
2021-01-25 15:52 ` ori
2021-01-26 1:37 ` Dworkin Muller
2021-01-26 1:54 ` Alex Musolino
2021-01-26 2:34 ` Dworkin Muller
2021-01-26 2:49 ` Alex Musolino
2021-01-26 3:01 ` Dworkin Muller
2021-01-26 3:08 ` ori [this message]
2021-01-26 3:44 ` Dworkin Muller
2021-01-26 2:35 ` Alex Musolino
2021-01-25 12:14 ` Richard Miller
2021-01-25 23:44 ` Dworkin Muller
2021-01-26 0:02 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=680018982E4780C52664493EFBC797A6@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).