sshd

[Stu Innes]

We are experienceing some weirdness with sshd.
When executing ssh -V we get a response of OpenSSH_3.8.1p1, OpenSSL 0.9.7d, when testing sshd we telnet (hostname) 22 the response we get is SSH-2.0-OpenSSH_3.6p1. We have searched the system for any and all sshd executables and only fine one under /usr/local/sbin/sshd, the init script also points to this exe. Anyway, this is causing the system not to disable a user account with multiple login attempts (trusted).
Is there a way to find out why we are getting two different outputs vers for sshd?
Thanks
S

[RAC_1]

Is this from same host??

type ssh
what ssh
type sshd
what sshd

[H.Merijn Brand (procura]

Might be that sshd was build with a STATIC libssh
This is rare

Then there is the - more likely - possibility that there are more than one sshd available, and the system starts one you don't expect
when you're connected, use lsof to see what files the sshd process has open

Or find sshd system wide

Or remove all (open)ssh/(open)ssl packages you can find and install the most recent version available

FWIW openssh-4.0p1 is MUCH faster than openssh-3.9.x

Enjoy, Have FUN! H.Merijn

[Jeff Schussele]

Hi Stu,

Besides RAC's ideas also try

ps -ef | grep sshd

then check that the running sshd is indeed the same one that is being started up in the rcX.d script. If it's not then use /sbin/init.d/sshd2 stop & /sbin/init.d/sshd2 start (use the appropriate script name of course) to bounce it. It may be that someone manually started the wrong one.

If that checks out then run

swlist | grep -i ssh

to verify the proper version is installed - then run

swlist -l fileset -a state | grep -i ssh

and verify that the filesets are *all* in a configured state. May be that the "RUN" fileset didn't install correctly or all the way.

HTH,
Jeff

[Darrel Louis]

Stu,

Check the /etc/rc.config.d/sshd file.
To which directory is it pointing?

Good luck

Darrel