| gabriel rosenkoetter on Thu, 27 Sep 2001 20:40:11 +0200 |
|
On Wed, Sep 26, 2001 at 06:06:11PM -0400, Paul wrote:
> Now it seems you're correct. The other day it would prompt me
> for a password unless I set the auth* files to read and execute.
> Now it doesn't care.
Is it possible that your ssh-agent didn't know about your keys when
they read-only settings were made and that at the same time as you
added the execute bit you either used a shell which was aware of the
right ssh-agent or added the key to the agent?
Or, is it possible that you edited either your .ssh/config or the
server's /etc/sshd_config file to change the allowance of public/
private key authentication or use of SSH-2 protocol during this
time?
> (One thing I did find after running the ssh -V command is that
> my client is a little old. 2.5.2p2)
Not much changed about the basic functionality of all this between
2.5 and 2.9. It's the converse example, but here's another server
(and from which this email is sent) I connect to regularly (and
*really* need to update both the kernel and ssh version on, but
I've got a copy of NetBSD 1.5.2 built waiting for me to install it
next time I'm at the console):
uriel:~% uname -a
NetBSD uriel.eclipsed.net 1.5 NetBSD 1.5 (URIEL) #0: Thu Jan 25 15:27:28 EST 2001 gr@uriel.eclipsed.net:/usr/src/sys/arch/macppc/compile/URIEL macppc
uriel:~% ssh -V
SSH Version OpenSSH_2.2.0 NetBSD_Secure_Shell-20001003, protocol versions 1.5/2.0.
Compiled with OpenSSL (0x0090581f).
(Yes, that machine has a vulnerable telnetd. No, I'm not running
it, so I didn't bother obliterating the hostname.)
> Here are more details than most will want to see:
No issues I know about whose bells that information rings.
--
~ g r @ eclipsed.net
Attachment:
pgpezkommS0t1.pgp
|
|