PowerShell / PowerShell/Win32-OpenSSH

Can not use with KeeAgent - Client service problem?

Open
#2,004 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Setup Community-Help
Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

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

Hello everyone,

In advance - I am not the sharpest tool in the shed, and propably not as technically versed as I should be.
I have the following usecase:

I want to use ssh signing for github. This does not work with current openssh version built in into windows. 8.1p1.
I therefore go ahead and istall OpenSSH beta with winget as suggested in the manual here.

I uninstall OpenSSH client from optional features and add C:\Program Files\OpenSSH to Path, otherwise ssh -V returns 8.1p1.
I then can successfully sign my commits with ssh keys, which is great.

What is not great, is that then my key based authentication stops working.
I use KeePass, and Keeagent, which seem to continue working -
image

Expected behavior
I would expect it to login with key as 8.1p1 does.

image

Actual behavior
Instead, I get a password prompt.
Error details

No response

Environment data
Sorry, not sure what to do here.
Version

8.9.1.0

Visuals

No response

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.

Research direction

Start by reproducing the reported difference between the built-in Windows OpenSSH 8.1p1 client and the beta installed with winget, using the KeePass/KeeAgent setup and version 8.9.1.0. Compare ssh signing and key-based authentication behavior, then document the relevant environment details; the issue names no source file or test, so the affected entry point must first be located.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
authentication, operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.