PowerShell / PowerShell/Win32-OpenSSH

ssh-agent should support '-c' and '-t' options of ssh-add

Open
#1,056 24 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0 - Backlog Area-ssh-agent
Dominant language
No language data
Stars
8.3k
Forks
819
PR merge metrics
No merged PRs in 30d

Description

"OpenSSH for Windows" version
1.0.0.0

OperatingSystem
Windows 10 Pro

I've set ssh-agent service startup type to Automatic. I've also set a passphrase protected key at %USERPROFILE%\.ssh\id_rsa. The passphrase in question is not the same as my user password.
After rebooting my PC, if i type ssh-add -l I can see that my key has been loaded by default (without any prompt for my passphrase). I've also noticed that I can connect to ssh -T git@github.com without problems.

My question is: How is the ssh-agent startup service able to add id_rsa without asking for my passphrase? Is it storing my passphrase somewhere? If so, where?

I'm familiar with services such as PAM, as well as software such as GNOME Keyring, KWallet, etc. Just want to understand exactly what is the Win32 implementation doing and possible customize OpenSSH's security policy to ask for my passphrase at least once after login.

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 with the Win32 ssh-agent service and the ssh-add entry points mentioned in the issue, comparing the requested -c and -t options with the existing -l behavior. Review the discussion to reconcile option support with the passphrase and startup-policy questions; done should include a clearly defined behavior and corresponding validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
authentication, operating-systems, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.