HMAC failure

Hello,

Could you please verify that the algorithms are enabled in the Advanced menu of your SSH entry?

You can set them by switching the Algorithm support option to Custom and enabling all required missing algorithms.



Let us know if that helps.

Best regards,

Hello, thanks for the update.

I already did it , I mean I use all the options and also I use specific options, but I always got the same result.

I only could get it to work when I downgrade RDM.

Hello,

Would it be possible to send us a screenshot of your configurationsin the Advanced menu of your SSH entry?

Best regard

Hello , here are the outputs



also I think it is important to share

Hello,

After reviewing he error message a second time you provided, this line is quite strange: [5/18/2024 12:39:16 PM] Received userauth failure: publickey,keyboard-interactive,password.

This seems to indicate that the password or private key is incorrect.

Can you tell us if you are using a private key to connect to the SSH session?

If not, I think it would be better to have a remote session so I can see your issue firsthand.

Please let me know if this would work for you.

Best regards,

Hello,
I have the same issue after upgrade.
Authentication: Password

[6/24/2024 1:18:30 PM] Devolutions Protocols version: 2024.6.11.1 Windows
[6/24/2024 1:18:30 PM] Terminal font: Courier New [Courier New, fixed=True]
[6/24/2024 1:18:30 PM] Starting SSH, verbose level: 2
[6/24/2024 1:18:30 PM] Setting up connection
[6/24/2024 1:18:30 PM] Connecting to port: 443 (IPv4 - 6)
[6/24/2024 1:18:31 PM] SSH banner: SSH-2.0-9.37 FlowSsh: Bitvise SSH Server (WinSSHD) 9.37: free only for personal non-commercial use

[6/24/2024 1:18:31 PM] Received kex init
[6/24/2024 1:18:31 PM] Sending kex init
[6/24/2024 1:18:31 PM] Selected algorithms: diffie-hellman-group-exchange-sha256, rsa-sha2-256, aes256-ctr, aes256-ctr, hmac-sha2-256, hmac-sha2-256, none, none
[6/24/2024 1:18:31 PM] Sending diffie-hellman group exchange request
[6/24/2024 1:18:31 PM] Received diffie-hellman group of size: 3072
[6/24/2024 1:18:31 PM] Sending diffie-hellman group exchange kex init
[6/24/2024 1:18:31 PM] Received diffie-hellman group exchange kex reply
[6/24/2024 1:18:31 PM] Server authenticated by provided public key
[6/24/2024 1:18:31 PM] Sending new keys message
[6/24/2024 1:18:31 PM] Received new keys message
[6/24/2024 1:18:31 PM] Sending userauth service request
[6/24/2024 1:18:31 PM] HMAC verification failed
[6/24/2024 1:18:31 PM] Disconnection in progress
[6/24/2024 1:18:31 PM] Bytes sent: 1632, Bytes received: 2772
[6/24/2024 1:18:31 PM] Packets sent: 5, Packets received: 4
[6/24/2024 1:18:31 PM] Kex completed: 1
[6/24/2024 1:18:31 PM] Disconnecting

I'll downgrade the installation again

Hello,

Thank you for the logs.

Would it be possible to tell us if the issue reappears in other applications?

Best regards,

Hi I've upgrade from 2023.3.39.0 64-bit to 2024.2.13.0 64-bit and the SSH port forwarding stop working and show the same issue

Hello,

Thank you for updating us. As the error message suggests, it seems like there is an incompatibility between the server and the client. In these cases, I usually ask if the issue arises in another application to be sure if the issue is related to RDM.

Could you please verify if the problem persists when using another SSH client? This will help us determine if the issue is specific to RDM or if it might be a broader compatibility issue.

If the problem is specific to RDM, we can investigate further on our end.

Best regards,

Hi Carl
I've created the ticket 00065329, however to let you know when I used another clients as Putty or Bitvise, it worked.
When I move back to version RDM version 2023.3.39.0 it works fine.
Thanks
Francisco

Hello,

I have spoken with the technician handling your case, and we will send you a link for a session. During this session, we will record the issue and ensure all details are thoroughly documented. This will help us either recreate the issue accurately or provide enough information for the developers.

Best regards,

Hey Guys,
I have the same Problem. I'm using RDM 2024.2.12.0. I'm trying to connect with an SSH Tunnel to a Bitvise SSH Server Version 9.38.
When doing so, I'm getting the same HMAC Verification failed message.
Best Regards, Johannes

Hello,

The issue was “fixed” on the client side by reverting to Version 9.29 of Bitvise and using RDM 2024.2.16, and we were not able to reproduce the issue from our end.

Can you try reverting to Version 9.29 of Bitvise and see if it works for you as well?

If this workaround works, I will create a bug report as the issue likely stems from how we push the console command in the backend.

Best regards,

Hi Carl,
I can confirm that it works with Bitvise SSH Server 9.29. (RDM Version i tested with was 2024.2.12.0)
As soon as Upgrading to the next Version of Bitvise SSH Server (9.32) the connection doesnt work anymore.
Please have a look at the Bitvise SSH Server Changelogs from Verison 9.32, which addresses changes with the algorithms due to CVE-2023-48795.
As the Changelog states, the SSH Client has to support Strict Key Exchange. Unfortunately I cant find any options for this, even though it was introduced with RDM Version 2024.1.1.3.
Best Regards, Johannes

Hello,

Thank you. I have created an internal ticket for this issue.

We will attempt to recreate your issue, and I will keep you updated on any progress.

Best regards,