ssh w/no pass not working
I created a key pair with no password, scp'ed id_dsa.pub to the users
home dir on the other machine, called it authorized_keys and set ~/.ssh
to 0700 and ~/.ssh/authorized_keys 0644 This has worked on several
machines, but in this particular case, it doesn't. What am I missing?
First machine is Fedora Core 2 with openssh-3.9p1-1fc2 and the second
machine is Fedora Core 3 with openssh-3.9p1-8.0.3
--
* John Oliver [url]http://www.john-oliver.net/[/url] *
Re: ssh w/no pass not working
> I created a key pair with no password, scp'ed id_dsa.pub to the users[color=blue]
> home dir on the other machine, called it authorized_keys and set ~/.ssh
> to 0700 and ~/.ssh/authorized_keys 0644 This has worked on several
> machines, but in this particular case, it doesn't. What am I missing?[/color]
Connect with ssh -v or -vv or -vvv to get debugging output that will show
you where the protocol is breaking down.
--
To reply by email, change "deadspam.com" to "alumni.utexas.net"
Re: ssh w/no pass not working
Andrew Schulman <andrex@deadspam.com> wrote:[color=blue][color=green]
>> I created a key pair with no password, scp'ed id_dsa.pub to the users
>> home dir on the other machine, called it authorized_keys and set ~/.ssh
>> to 0700 and ~/.ssh/authorized_keys 0644 This has worked on several
>> machines, but in this particular case, it doesn't. What am I missing?[/color][/color]
[color=blue]
> Connect with ssh -v or -vv or -vvv to get debugging output that will show
> you where the protocol is breaking down.[/color]
In my experience, that often won't tell you anything for authorization
problems. You'll usually need to run the server in debug/verbose mode
and examine its output.
[color=blue]
> --
> To reply by email, change "deadspam.com" to "alumni.utexas.net"[/color]
--
Darren Dunham [email]ddunham@taos.com[/email]
Senior Technical Consultant TAOS [url]http://www.taos.com/[/url]
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Re: ssh w/no pass not working
try authorized_keys2
--
[email]jbeasley@sdf.lonestar.org[/email]
SDF Public Access UNIX System - [url]http://sdf.lonestar.org[/url]