From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] factotum/ssh issue
Date: Mon, 11 Nov 2002 09:43:23 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0211110751001.1071-100000@athena> (raw)
Hola,
We finally stopped working long enough to upgrade
to 4e last week and I have to admit, the first
time I was auto-login'd to a remote unix box
after having stored the key in factotum I was
exuberant.
I have a minor nitpick, though. When I ssh'd into a unix
box for the first time I was prompted to add the key
(not real security, but good enough for me), then I was
asked for the password to the machine. My trigger happy finger
decided to hit enter, thereby entering a nil password
and failing to authenticate. Further attempts to
ssh into the machine failed because factotum stored the
incorrect password. I needed to become accustomed to
key management with factotum anyway, but it still seems improper
to store the password if password authentication fails.
I looked at removing the server key if ssh password authentication
fails, but there doesn't seem to be an rpc mechanism in factotum
to do this.
Cheers,
Sam
next reply other threads:[~2002-11-11 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 14:43 Sam [this message]
2002-11-11 15:36 Skip Tavakkolian
2002-11-11 16:56 Russ Cox
2002-11-11 17:29 ` Sam
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=Pine.LNX.4.30.0211110751001.1071-100000@athena \
--to=sah@softcardsystems.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).