ssh-add on Windows explicitly forbid host constraint specifications

Open Beginner friendly
#2,458 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
authentication, cli, operating-systems

Research direction

Start in ssh-add.c at the referenced lines 876 and 896, where host constraint specifications are explicitly disabled for Windows. Compare this path with the agent functionality described in the issue and verify ssh-add can accept host constraints on Windows. Done means the command no longer reports "Feature disabled" for this supported use case.

Written by the indexing model from the issue text.

Description

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

Access to SSH servers that only accept the presentation of a single certificate for authentication is impossible without the ability to specify host constraints.

Although this functionality is properly implemented in the SSH agent, it is explicitly disabled in the Windows version of the ssh-add command.

References:

Expected behavior
Enable the feature
Actual behavior
Feature disabled
Error details
Environment data
Name                           Value
----                           -----
PSVersion                      5.1.26100.9444
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.9444
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Version

OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2 / OpenSSH_for_Windows_10.0p2 Win32-OpenSSH-GitHub, LibreSSL 4.2.0

Visuals

No response

Dominant language
No language data
Stars
8.3k
Forks
820
No merged PRs in 30d

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.

More from PowerShell/Win32-OpenSSH

All issues in PowerShell/Win32-OpenSSH

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.