PowerShell / PowerShell/Win32-OpenSSH

Post quantum algorithms supported version that updates with Windows update

Open
#2,433 2 comments 13 reactions 1 assignee View on GitHub

@mgreenegit is already working on this.

Since Apr 6, 2026.

Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

Summary of the new feature / enhancement

@tgauth

I know that there are some issues already report on post quantum algorithm support and I know that it is being worked on, and maybe even incorporated into v 10 of Windows OpenSSH but it most certainly has not been incorporated into the standard upgrade / updates within Windows updates.

You still have beta tags on any new releases and any of those new releases would need to manually be installed on each server. I am neither going to try and battle to get something labeled beta installed on my production systems, nor am I going to ask my server admins to download and install the OpenSSH updates separately.

Can you please tell us:

  • When will a non-beta version of Windows OpenSSH support post quantum algorithms?
  • What are Microsoft's plans for upgrading Windows OpenSSH versions via Windows updates? Are we stuck at OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2 for eternity?

As the upstream OpenSSH developer mentioned in a closed issue post, "It's a little embarrassing"

Proposed technical implementation details (optional)
  • Tell us when we will see post quantum algorithms in a release that is not tagged as a beta release
  • Tell us what the release schedule is for updating OpenSSH on Windows systems via support monthly updates. If there currently is none, then please make that happen. I've been following MSFT Open SSH for a few years now and this beta release tagging has been the same all along. The only progress that I have seen is to actually declare OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2 as the standard release. This seemed to coincide with the release of Server 2025 and nothing has changed since then (well over a year now)
  • I suggest a quarterly release schedule

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.