ScSSHClient log for fail connection tracing

[eridatacom]

Hi,
I need to do tracing for SSH interconnection (Password Authentication),
because I always get exception error message :
'Opening command shell : Authentication failed Publickey, Keyboard-Interactive'.
When trying to connect to an Avaya CM8 Pabx maintenance port 5022
which runs OpenSSH server (SSH 2.0 OpenSSH_7.4)

This exception triggered on the section code :
...
try
ScSSHShell.Connect;
mmLogging('Command Shell Opened.');

except
on E: EscError do
begin
sMsg := 'Error on opening command shell :'+ E.Message;
mmLogging(sMsg);

if MessageDlg(Format(ErrMsg,['Opening command shell',E.Message]),
mtError,[mbYes,mbNo],0) = mrYes then
begin
try
ScSSHShell.Disconnect
finally
ScSSHClient.Disconnect;
end;
end;
end;

end;
...

My testing modul runs well when connecting to :
- Windows 10 OpenSSH server (SSH-2.0-OpenSSH_for_Windows_8.1)
- Windows MobaSSH Server (SSH-2.0-OpenSSH_7.1)
- CentOS OpenSSH Server (SSH-2.0-OpenSSH_7.4)

Test connection to Avaya CM8 using putty works well (password authentication) with same user & password.
This is the PuTTY eventlog :
2020-08-27 13:33:03 Looking up host "10.126.2.130" for SSH connection
2020-08-27 13:33:03 Connecting to 10.126.2.130 port 5022
2020-08-27 13:33:03 We claim version: SSH-2.0-PuTTY_Release_0.74
2020-08-27 13:33:03 Remote version: SSH-2.0-OpenSSH_7.4
2020-08-27 13:33:03 Using SSH protocol version 2
2020-08-27 13:33:03 No GSSAPI security context available
2020-08-27 13:33:03 Doing ECDH key exchange with curve Curve25519 and hash SHA-256 (unaccelerated)
2020-08-27 13:33:03 Server also has ecdsa-sha2-nistp256/ssh-rsa host keys, but we don't know any of them
2020-08-27 13:33:03 Host key fingerprint is:
2020-08-27 13:33:03 ssh-ed25519 255 fa:cd:f9:a4:c1:2b:18:bc:61:e4:71:53:92:c6:7c:0a
2020-08-27 13:33:03 Initialised AES-256 SDCTR (AES-NI accelerated) outbound encryption
2020-08-27 13:33:03 Initialised HMAC-SHA-256 (unaccelerated) outbound MAC algorithm
2020-08-27 13:33:03 Initialised AES-256 SDCTR (AES-NI accelerated) inbound encryption
2020-08-27 13:33:03 Initialised HMAC-SHA-256 (unaccelerated) inbound MAC algorithm


Do you have any suggestion to do the interconection tracing ?

[ViktorV]

You won't be able to get a more detailed error message because the SSH procotol doesn't provide more information.
Please make sure that you've set the TScSSHClient.Authentication property to atPassword.