I am trying to get ssh-2.0.13 installed and running on a couple AIX 4.3.2 servers, which both have an almost identical configuration and OS installation. One is an F50, the other is an F40. I have used a patch to get it working (sshunixuser.c) on AIX, and I have patched it to look at hostbased authentication before pubkey. Everything works great except for hostbased authentication. But wait, this is where it gets weird. The F50 has no problem, ever. The F40 works *right after* I "make install," but then quits working if I log out and log back in. I can always use ssh on the F50, to the F40 or to itself. After a matter of time, or after logging out for sure, the F40 loses the ability to connect to either one. It's almost like it loses it's mind or something. Here's where it's sticking: root@pdmux001(288):# ssh pdmux003 -d 4 debug: connecting to pdmux003... debug: entering event loop debug: SshEventLoop/sshunixeloop.c:563: Starting the event loop. debug: ssh_client_wrap: creating transport protocol debug: ssh_client_wrap: creating userauth protocol debug: Ssh2Common/sshcommon.c:204: remote hostname is "10.7.6.3". debug: Ssh2Transport/trcommon.c:592: Remote version: SSH-2.0-2.0.13 (non-commercial) debug: Host key found from the database. debug: Ssh2Common/sshcommon.c:155: special packet received from connection protocol: 3 debug: Ssh2Common/sshcommon.c:155: special packet received from connection protocol: 4 debug: SshConfig/sshconfig.c:574: Got config cipherlist "AnyStd" debug: SshConfig/sshconfig.c:633: Final cipherlist "3des-cbc,blowfish-cbc,twofish-cbc,arcfour,none" debug: Ssh2AuthHostBasedClient/authc-hostbased.c:279: Reading pubkey-blob from /etc/ssh2/hostkey.pub... debug: Ssh2AuthHostBasedClient/authc-hostbased.c:288: done. debug: Ssh2AuthHostBasedClient/authc-hostbased.c:329: Child: Execing ssh-signer...(path: ssh-signer2) It will sit here until I ^c. I uncommented the "#define SIGNER_DEBUG" line in ssh-signer2.c so that I could get specific debug information from that module, but even after "./configure --enable-debug --enable-debug-heavy" and reinstalling, I don't get any more detail on what's going on inside the signer module at runtime. Does anyone have any idea how to really get DEBUG info going on this module? I wrote the author of the program, but I haven't heard anything yet. It's not that I've given up hope of hearing from him, it's just that this program is *exactly* what I need, and I'm getting impatient. I've lost days looking at the problem and it's beyond me. Thanks for any help you can lend, dk David Krider Product Data Management Administrator, Arvin Industries Acts 17:28 - For in Him we live, and move, and have our being.
