SSH Server Signature - WeOnlyDo Discussion board

SSH Server Signature (wodSSH / wodSSH.NET)

by Bitzk, Wednesday, May 06, 2020, 13:02 (27 days ago)

Hi, i'm having problem connecting to an HP-UX server with Wod Client, i receive this error: the server signature does not match.

syslog.log file show this for 2 connections, one from Putty_client and the other one with WoD.NET_client:

May 6 11:58:10 tebas sshd[13193]: SSH: Server;Ltype: Version;Remote: 172.16.14.222-55521;Protocol: 2.0;Client: PuTTY_Release_0.73
May 6 11:58:10 tebas sshd[13193]: SSH: Server;Ltype: Kex;Remote: 172.16.14.222-55521;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none [preauth]
May 6 11:58:22 tebas sshd[13193]: SSH: Server;Ltype: Authname;Remote: 172.16.14.222-55521;Name: swinds [preauth]
May 6 11:58:33 tebas sshd[13193]: Accepted keyboard-interactive/pam for swinds from 172.16.14.222 port 55521 ssh2
May 6 11:58:33 tebas sshd[14498]: SSH: Server;Ltype: Kex;Remote: 172.16.14.222-55521;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
May 6 12:09:38 tebas SAPBRD_30[28084]: Q02 Monitoring: Stop Workp. 12, PID 28084
May 6 12:12:40 tebas sshd[22220]: SSH: Server;Ltype: Version;Remote: 172.16.14.222-56209;Protocol: 2.0;Client: WeOnlyDo.Net
May 6 12:12:40 tebas sshd[22220]: SSH: Server;Ltype: Kex;Remote: 172.16.14.222-56209;Enc: aes128-ctr;MAC: hmac-sha2-256;Comp: none [preauth]
May 6 12:12:40 tebas sshd[22220]: SSH: Server;Ltype: Authname;Remote: 172.16.14.222-56209;Name: swinds [preauth]
May 6 12:12:41 tebas sshd[22220]: Accepted password for swinds from 172.16.14.222 port 56209 ssh2
May 6 12:12:41 tebas sshd[22277]: SSH: Server;Ltype: Kex;Remote: 172.16.14.222-56209;Enc: aes128-ctr;MAC: hmac-sha2-256;Comp: none
May 6 12:12:41 tebas sshd[22277]: SSH: Server;LType: Throughput;Remote: 172.16.14.222-56209;IN: 0;OUT: 896;Duration: 0.2;tPut_in: 0.0;tPut_out: 5277.9


Any help?

thinks in advice!.
B1tzk.

SSH Server Signature

by wodSupport, Wednesday, May 06, 2020, 17:16 (26 days ago) @ Bitzk

Hi.

Can you please be more specific, what exact component and version are you using when this happens? This sounds like familiar problem, but I believe it was fixed long time ago, so I want to make sure if it appears again or it's an old issue?

Regards,
Jasmine.