From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ssh and pcauth
Date: Fri, 29 Aug 2003 10:29:03 +0100 [thread overview]
Message-ID: <095acfaa80c4629c57866fbb9940a018@yourdomain.dom> (raw)
In-Reply-To: <730584430@snellwilcox.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
I beleive you must have a factotum running, its started at boot,
so I would expect it to prompt you for a key (user & password in this case).
If this happened once and you have the wrong key
then factotum will rembember them until reboot or its
told to forget.
rob (pike) posted a neat script, delkey, a while back
to simplify the deletion of unwanted/bad keys. I don't
know why this didn't make it into the distribution.
I run a simgle plan9 machine so I have no secstore. In my
$user/lib/profile I have:
echo -n 'factotum '
auth/aescbc -d < $home/lib/wallet | read -m > /mnt/factotum/ctl
This works similarly though less securely (somone could steal
my wallet and spend weeks cracking it).
-Steve
[-- Attachment #2: Type: message/rfc822, Size: 1386 bytes --]
From: 9fans@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: [9fans] ssh and pcauth
Date: Fri, 29 Aug 2003 06:55:49 +0100
Message-ID: <730584430@snellwilcox.com>
When I boot from my new pcauth kernel, I cannot use ssh.
When I try to ssh from Plan 9 to Linux, the same connection that
previously worked now gives "ssh: client authentication failed"
In the wiki, there is a reference to copying
$home/lib/$user.secret.factotum to /mnt/factotum/ctl. What is this
for ? Is it for ssh'ing to the Plan 9 machine, or do I have to do it
? I did it as user bootes and ssh still didn't work, and I did it as
another user and got a permission denied.
I can ssh just fine if I boot from the old pcdisk kernel.
I see no messages in the logs on the receiving side of the ssh.
However, if I connect to a non-existent or non-responding machine, the
ssh just times out, it doesn't give the error; and sniffing the
connection reveals some traffic does go between the computers when I
attempt and get the "ssh: client authenticaion failed" error.
--Rob
next parent reply other threads:[~2003-08-29 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <730584430@snellwilcox.com>
2003-08-29 9:29 ` steve.simon [this message]
2003-08-29 5:55 Rob Ristroph
2003-08-29 6:46 ` Skip Tavakkolian
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=095acfaa80c4629c57866fbb9940a018@yourdomain.dom \
--to=steve.simon@snellwilcox.com \
--cc=9fans@cse.psu.edu \
/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).