PowerShell / PowerShell/Win32-OpenSSH
Authenticate using Windows Credential Providers
Nobody has claimed this yet.
- 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
When I attempt to authenticate using OpenSSH on Windows 10, it does not appear to be using the Windows Credential Providers, so using a 3rd-party credential provider does not work with OpenSSH. This can lead to unexpected behavior, such as the credential provider requiring two-factor authentication but OpenSSH only requiring a single factor. Can OpenSSH on Windows be integrated with Windows Credential Providers so no matter which method you use to connect to Windows (e.g. local logon, RDP, or SSH), the same logon process and rules are utilized?
Proposed technical implementation details (optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Windows authentication path in Win32-OpenSSH and the linked Windows Credential Providers documentation first. Define done as consistent use of the Windows Credential Provider authentication process for local logon, RDP, and SSH connections, with the relevant behavior verified on Windows 10.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100