Operating System - HP-UX
1753546 Members
5682 Online
108795 Solutions
New Discussion юеВ

HP-UX Secure Shell login problem.

 
Erol KAHRAMAN
Advisor

HP-UX Secure Shell login problem.

hi folks,
today i updated my SS to HP 4.20 version. But after i restarted my ss any users can login. I recreated ssh_host_rsa|dsa_key file but nothing changed.
In my syslog.log file i am seeing the followin lines;
Failed none for user1 from IP_addr port AnyPort ssh2
Failed password for user1 from IP_addr port Anyport ssh2
I changed the password of user1 to be sure that is correct.
What could be a problem ?
5 REPLIES 5
Asif Sharif
Honored Contributor

Re: HP-UX Secure Shell login problem.

Hi Kahraman,

Kill ssh proceses and run it again then check.

Regards,
Asif Sharif
Regards,
Asif Sharif
Steven E. Protter
Exalted Contributor

Re: HP-UX Secure Shell login problem.

Shalom Erol,

ssh -vvv user@hostname

WE need diagnostics.

Usually bounding the sshd service helps.

/sbin/init.d/sshd stop
/sbin/init.d/sshd start

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Erol KAHRAMAN
Advisor

Re: HP-UX Secure Shell login problem.

I send the output of "ssh -vvv" as an attachment. I restarted the service but the problem didn't solve.
Alzhy
Honored Contributor

Re: HP-UX Secure Shell login problem.

Did you by any chance install KRNG11i prior to installing/updating SSH 4.x?
Hakuna Matata.
Matti_Kurkela
Honored Contributor

Re: HP-UX Secure Shell login problem.

HP-UX Secure Shell versions 3.7x and below had no significant prerequisites.
On the other hand, the newer versions require that the OS is patched to a certain level.
See http://docs.hp.com/en/T1471-90019/ch01s08.html
for more information.

The problem would seem to be on the server side, probably somehow related to the password checking. Your "ssh -vvv" output was from the client side, so it can tell about server-side events only what the server chooses to tell... and when the server thinks the password is not correct, it does not tell very much about its internal workings to the client.

Could you run sshd (the Secure Shell server) with a -d (debug) option and show us what it reports? The server's debug listing might be more useful when solving password checking problems.
MK