Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ripemd160 HMAC support #2289

Open
3 tasks done
krz101 opened this issue Oct 18, 2024 · 1 comment
Open
3 tasks done

ripemd160 HMAC support #2289

krz101 opened this issue Oct 18, 2024 · 1 comment
Labels
Waiting on Author Need more information to diagnose

Comments

@krz101
Copy link

krz101 commented Oct 18, 2024

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.

Steps to reproduce

When using ssh command I am getting error "no matching MAC found. Their offer: hmac-ripemd160, hmac-sha1".

In older version 8.1 I did not have this issue with the same ssh command.

Expected behavior

Expected ssh command to create tunnel connection with no errors

Actual behavior

"no matching MAC found. Their offer: hmac-ripemd160, hmac-sha1"

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      5.1.19041.5007
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.5007
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Version

9.5

Visuals

No response

@tgauth tgauth transferred this issue from PowerShell/openssh-portable Oct 18, 2024
@maertendMSFT
Copy link
Collaborator

This is a result of a change that was made upstream in OpenSSH 7.6: https://www.[openssh.com/txt/release-7.6](https://www.openssh.com/txt/release-7.6)

Did you have it explicitly added after 7.6 was released?

We also removed SHA1 in release 9.5, so you may have just been relying on SHA1. Once that was removed and pushed out, then you were no longer supported by default.

@maertendMSFT maertendMSFT added the Waiting on Author Need more information to diagnose label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Waiting on Author Need more information to diagnose
Projects
None yet
Development

No branches or pull requests

2 participants