SecureCRT / SecureFX and HP Secure Shell A.03.71.000

[Jan Mlotkiewicz]

Not a question, but just an FYI based on our experience after upgrading our server side Secure Shell and doing some testing with MS Win based clients.

SecureCRT / SecureFX do not do failover to an alternate authentication type if the primary type fails. When running Secure Shell A.03.71.000 on the server side, under a HP-UX 11.00 Trusted System, any user account with a password > 8 chars gets denied and the syslog traps a message saying Failed password for from .

The workaround for this is to set SecureFX / SecureCRT to do Keyboard Interactive as the primary authentication method. This has to be set on a per session basis from the session list - won't work after connection is established

[Jaakko Kemppainen]

Great Information!!

I have been struggling with this a long time and lost significant amount of hair with it ;-)

Actually, I can report that same functionality seems to appear with HP-UX 11.11.

Thanks, Jaakko