>>ssh-2.0.13 and ssh-1.2.27 have been released today to the public.
>>
>>It is recommended that you upgrade your ssh versions to these current
>>versions.
>
>FWIW, 2.0.13 seems to have fixed the lingering connection problem experienced
>while using TCP-Wrappers under Solaris. The extra features also make the
>upgrade well worthwhile.
Ahem. Seems that this lingering connection is dependant on the configuration
of the client (and, to a certain extent, the server-side of the connection).
It seems that if password authorization is used, the server exits cleanly on
logging out (either via 'logout' or ^D). If passphrase authentication is
used, the connection lingers. Since after compilation, I was set up for
passwords (not passphrases, which is my normal configurations), it seemed the
problem had been fixed.
The difference seems to occur at the authentication stage; here is a snippet
of output from running sshd -v:
debug: new_connection_callback returning
debug: ssh_sigchld_real_callback
debug: ssh_sigchld_process_pid: no handler for pid 18825 code 0
Those second two lines _only_ occur where ~/.ssh2/authorization and
~/.ssh2/identification exist; even if an incorrect passphrase is entered and a
password is entered, those last two lines have already appeared on the server
side. From a quick glance at the source, those debug errors seem to occur
because the child process has received a SIGCHLD.
The configuration is Solaris 7 with ssh-2.0.13 compiled with gcc-2.8.1 and TCP
wrappers 7.6
I hope this information can help to track down the problem more easily.
--
John Riddoch Email: [EMAIL PROTECTED] Telephone: (01224)262721
Room C6, School of Computer and Mathematical Science
Robert Gordon University, Aberdeen, AB25 1HG
I am Homer of Borg. Resistance is Fu... Ooooh! Donuts!
