ssh help

[Nyck_1]

I'm trying to configure ssh so that when I ssh to a server it does not prompt me for a password, so far its does not work!

I have been looking round the net and have found some good guides and followed them but I'm still having problem. Can someone help me please????

[OldSchool]

well....what have you tried?

the basic procedure is to create keys and place them on the server that you are trying to log in to. the details of doing that vary depending upon what the client is.

also, having correct permissions on the directory containing the keys is critical.

[James R. Ferguson]

Hi Nyck:

To setup SSH public keys see Matti's directions in this thread --- he does a nice job of describing the simple procedure:

http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1254688

Regards!

...JRF...

[OFC_EDM]

What are the OS's of your source and destination? Sometimes that's an issue.

For example I've given up trying to get SSH to work without a password between Tru64. It just won't work (as far as I know). Unless you move to OpenSSH on Tru64 which is not an option as it breaks stuff :)

It's most likely not your issue but thought I'd mention it just in case.

Cheers

[Nyck_1]

The issue was between an Itanium in our office and a Solaris8 server at the customer site.

I have now got this working between two Itanium servers, pretty straight forward. But we think the issue might lie on the customer's server so we have bounced the issue back to them now.

When its resolved I will let you know the solution.

[Steven Schweda]

If you still have any questions, please
provide more information than "does not
work". "ssh -v [...] " output can be useful.
Unless you're _trying_ to waste everyone's
time.

[Victor Fridyev]

If the target machine there is in another site, the problem is 90% in a firewall rules. Please verify that all firewalls in the way are open for port 22.
4% are for permissions of .ssh and authorized_keys. Compare them with the ones on the computers where ssh works normally.
4% for corruption of the keys and 2& - God knows 8)))

HTH

[Bill Hassell]

The 3 most common problems with public keys are:

1. copy/paste with vi splits the ONE line into several lines. Look at the authorized_keys file with wc. If there are 3 keys in the file, wc -lw will report 3 6 (3 lines, 6 words). Always start the vi session with :set wm=0 noai, then move from line to line to verify each entry is one big line.

2. The permissions for the .ssh directory as well as the contents must all zeros for group and world:

chmod 700 $HOME/.ssh
chmod 600 $HOME/.ssh/*

3. Some versions of Secure Shell do not put the key type (ssh-dss for example) in front of their public key. Be sure each key has the key type first on the line, then a space, the actual key and finally a comment on where the key originated.

You can get some debug information using ssh -vvv on the client side although it really isn't clear what test was made in the ssh daemon that failed the public key authorization.