From: "Steven Stallion" <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Fun with sshsession
Date: Tue, 6 Dec 2022 20:12:53 -0600 [thread overview]
Message-ID: <a48fcb63b914580f2c6f368cfad466f7@gunge.quuxotic.net> (raw)
All,
I've recently had a need to get SSH2 up and running on a CPU server
using auth_userpasswd and I'm running into issues after authenticating
as a user other than the host owner.
I'm able to authenticate successfully as a normal user, however the
actual login user is still treated as the host owner (even though
$user disagrees). Passing -t to sshsession at least corrects the
$user misnomer, but I can't seem to escape the host owner.
I recall something from the distant past at Coraid when bls was
working on ssh2 relating to the host owner but for the life of me I
can't remember what the issue was.
Has anyone on the list gotten sshsession up and running supporting
non-host owner logins?
Cheers,
Steve
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2a6ccbc6a0c58700-Mbb9f1227abac8c123999c67c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
reply other threads:[~2022-12-07 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a48fcb63b914580f2c6f368cfad466f7@gunge.quuxotic.net \
--to=sstallion@gmail.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).