topic Re: slogin problems in Operating System - HP-UX

slogin problems

Dan Copeland — Thu, 10 Jan 2002 16:59:30 GMT

I'm still being prompted for a passwd when using slogin w/ .shosts file including the client machine--i.e:

hptest11 copeld

Any suggestions?

tia,
Dan

Re: slogin problems

Tim D Fulford — Thu, 10 Jan 2002 17:15:49 GMT

Hi

a few things
o I hope you mean rlogin & .rhosts not slogin & .shosts. If not then the rest is probably rubbish

o /.rhosts only works for the user with / as it's home (usually root). If root does not use / as it's home directory then it will fail.

o If you want to use .rhosts it is placed in each of the users home directories.

o name resolution: remember the machines will be reversed looked up so if .rhosts is
maca billy

and /etc/hosts is
193.164.192.23 machinea maca

This will not work as the IP will resolve to machinea & not maca.

o make sure the users are correctly in /etc/passwd file.

Tim

Re: slogin problems

Thierry Poels_1 — Thu, 10 Jan 2002 17:28:59 GMT

hi,

I'll give you some rubbisch about Secure Shell ;)
Is the .shosts protected properly: read-only; writeable by world might ruine the game.

regards,
Thierry.

Re: slogin problems

Craig Rants — Thu, 10 Jan 2002 17:37:18 GMT

Do an ssh -v -l username hostname

Look for some errors, also you will have to setup the trust, just having a .shosts file will not suffice.

Each server will have to have a key in the .ssh/known_hosts file. To get those do a ssh/slogin (slogin is linked to ssh) in both directions so the keys are accepted, then try it again.

GL,
C

Re: slogin problems

Sanjay_6 — Thu, 10 Jan 2002 18:12:54 GMT

Hi Frank,

Maybe the userid is different on the two systems. Configure a /etc/hosts.equiv file on the client system. do a "man hosts.equiv" to know more about the same.

Hope this helps.

Regds

Re: slogin problems

Craig Rants — Thu, 10 Jan 2002 18:19:42 GMT

Frank,
I actually prefer the key encryption from ssh. It is more secure and works better (with less problems) than a .shosts file. You may have to make changes to your sshd_conf file to allow .shost type authentication also. Below or my instructions for setting that up.

GL,
C

6) Generate the users key (as user)
/opt/openssh2/bin/ssh-keygen
press enter when prompted for file location
press enter when prompted for passphrase

12) Setup trust with server1
On the server1:
cd /username/.ssh
scp identity.pub client_hostname:/username/.ssh/identity.pub.server1 (where the
client_hostname is the name of the box you are installing ssh on)
On client_hostname
cd /username/.ssh
cat identity.pub.server1 >> authorized_keys

13) Try the trust connection
On server1:
ssh -v client_hostname (watch for errors in the output, you should get in without
being prompted for a password)

Re: slogin problems

Wilfred Chau_1 — Thu, 10 Jan 2002 20:09:12 GMT

If you are using openssh, make sure the .ssh
dir is not write/executable by group and others.

Also make sure you have the identification file
in place on your server's .ssh(or .ssh2) dir.

Good luck!