openssh unix dev - Nov 2000 - StrictHostKeyChecking

Long ago, when I wrote the ssh config file on my desktop box, ssh 
(which might have been the non-openssh one) took 3 possible values for 
the StrictHostKeyChecking option - yes, no & ask.

Today, when I attempted to connect to a new machine, with no DNS 
entries (so using IP address) from my desktop box, ssh (now 2.3.0p1) 
SEGVed.  Looks like there is some subtle interaction between having an 
illegal value for StrictHostKeyChecking, an ip address target (I am 
sure I have done this before with named hosts) and a host that is not 
in known_hosts.

	Nigel.

-- 
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham                  Nigel.Metheringham at VData.co.uk ]
[ Phone: +44 1423 850000                         Fax +44 1423 858866 ]

I found what was causing this problem... and I'll share my 
embarrassment in public.

I build and install all packages as rpms.  Unfortunately in a moment of 
madness, I had installed the Red Hat package of openssl 0.9.5a on my 
build machine, but had my rebuild of Damien's openssl 0.9.5a on all the 
others.

Something in those 2 versions of openssl libraries don't quite match up.

	Nigel.

-- 
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham                  Nigel.Metheringham at VData.co.uk ]
[ Phone: +44 1423 850000                         Fax +44 1423 858866 ]