topic Re: ssh problem in Operating System - HP-UX

ssh problem

Avi Liani — Thu, 13 Jan 2005 09:02:32 GMT

Hi,

I just installed openssh3.9p1 depot on HP-UX box Ver 11.11

whene i try to bring the demon up i get the result :
Privilege separation user sshd dose not exist
EXIT CODE:255

can someone help me pleas ?

Re: ssh problem

Fred Ruffet — Thu, 13 Jan 2005 09:06:28 GMT

when UsePrivilegeSeparation is set to yes in sshd_config file, sshd will try to run as a user called sshd. If you did not create this user, it won't work.
Solutions :
. Create user sshd
. Set UsePrivilegeSeparation to no

Regards,

Fred

Re: ssh problem

Avi Liani — Thu, 13 Jan 2005 09:18:37 GMT

thenks,

that work fine, but now when i tride to open session white : ssh

i asking for password.

how can i run ssh whith out asking for password ?

Re: ssh problem

Steven E. Protter — Thu, 13 Jan 2005 09:22:36 GMT

I am attaching a document on proper setup of password free ssh access between machines. You cat copy the key files using any utility you wish, X is not required. Besides that, the document is solid and works very well.

SEP

Re: ssh problem

Ralph Grothe — Thu, 13 Jan 2005 09:40:04 GMT

If you haven't changed the default sshd_config file (which contains sensible default settings) then public key authorization will work.
You just need to create a private/public pair of RSA keys, and distribute the public keys to a file called authorized_keys in a subdirectory .ssh beneath the home directory of users on all hosts where you wish to log in.
Not to be asked for a passphrase you either have to create those keys with an empty passphrase (or revoke an existing one from an existing pair), or you need to start up an ssh-agent.
Usually the first method is a baerable compromise as far as security is concerned.
You can create the keys by ssh-keygen.
e.g.
Login as the account you connect from.
Then you could issue (find out the path of ssh-keygen if it's not in your PATH) something like

ssh-keygen -t rsa -b 1024 -N "" -f $HOME/.ssh/id_rsa

to generate an RSA key pair
(see manpage of ssh-kegen for details)

You can repeat this for other crypto systems like DSA, or RSA1 if you connect to protocol 1 servers.

The most "dangerous" part is the appending of your public key (denoted by the suffix .pub) to the aforemetioned authorized_keys file
(caveat "man-in-the-middle")
But usually ssh and remote cat \>\> will suffice if you know you can trust the route between client and server.

Re: ssh problem

Sanjay_6 — Thu, 13 Jan 2005 10:48:01 GMT

Hi,

Try this link to setup ssh without password between different version of ssh/sshd.

http://bumblebee.lcs.mit.edu/ssh2/

Hope this helps.

Regds