From: Dworkin Muller <dlm-9fans@weaselfish.com>
To: 9fans@9fans.net
Subject: Re: [9fans] getting 9front ssh to use RSA key?
Date: Mon, 25 Jan 2021 00:56:45 -0700 (MST) [thread overview]
Message-ID: <20210125.005645.575575916048045945.dworkin@weaselfish.com> (raw)
In-Reply-To: <085F2F9D360B60340D8C39E16662A3E5@eigenstate.org>
On Sun, 24 Jan 2021 22:33:59 -0800, ori@eigenstate.org wrote:
ori> Quoth Dworkin Muller <dlm-9fans@weaselfish.com>:
ori> > If I have PasswordAuthentication enabled on a remote host (tested on
ori> > MacOS and FreeBSD so far), I can log in to them without any problem.
ori> > However, if I have passwords disabled, but have an RSA key on the Plan 9
ori> > host and the corresponding pub key in authorized_keys on those remote
ori> > hosts, I'm failing to log in with the error message:
ori> >
ori> > ssh: auth: no key matches proto=rsa service=ssh role=client
ori> >
ori> > Presumably, this means I haven't set something up somewhere.
ori> > Currently, I do not have an auth server - I'm doing everything from a
ori> > terminal, slowly working my way up to a full world. Is there a way to
ori> > make this work in such an environment, without jumping through more
ori> > hoops than getting an auth server going would take?
ori> >
ori> > Thanks.
ori> >
ori> > Dworkin
ori>
ori> there's an example in the rsa(8) manpage.
That's what I thought I'd been doing, and doing it again just now
gives the same results. ``cat /mnt/factotum/ctl'' gives two lines,
one starting ``key proto=pass server=lethe service=ssh ...'' and the
other ``key proto=rsa service=ssh ...''. I've triple checked that
what's in .authorized_keys on the remote host (lethe) matches the
output of auth/rsa2ssh. I've also verified that the proto=rsa line in
factotum matches my lib/ssh/rsa file. Thus my confusion.
Thanks.
Dworkin
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td072863a97c9d3e9-M877d35325ba8c613afebac3c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-25 7:57 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 [this message]
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
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=20210125.005645.575575916048045945.dworkin@weaselfish.com \
--to=dlm-9fans@weaselfish.com \
--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).