Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

How to support older protocols even though they are not secure

Open
#2,411 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
powershell

Research direction

Start by reproducing the shown ssh command with OpenSSH_for_Windows 9.5p1 and review how its algorithm negotiation handles the offered ssh-rsa host key and diffie-hellman-group1-sha1. Done should mean the documented legacy connection reaches authentication without weakening unrelated defaults, while preserving the security rationale for disabled algorithms.

Written by the indexing model from the issue text.

Description

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

C:\Users\user>ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -l didi 10.0.7.1
Unable to negotiate with 10.0.7.1 port 22: no matching host key type found. Their offer: ssh-rsa

Expected behavior
%Trying 10.0.7.1, 22,...open
[email protected]'s password:
Actual behavior
Unable to negotiate with 10.0.7.1 port 22: no matching host key type found. Their offer: ssh-rsa
Error details

Environment data
PS C:\Users\XX> $PSVersionTable

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

PS C:\Users\XX> ssh -V OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2

Visuals

No response

Dominant language
No language data
Stars
8.3k
Forks
820
Avg merge
12m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/Win32-OpenSSH

All issues in PowerShell/Win32-OpenSSH

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.