You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this project searching for a SSH Agent working with PowerShell as well as GitBash (MSYS).
I do (currently) not use the Windows-Cert (YubiKey) features, but use it as a "normal" SSH agent. While testing, I realized, ssh-add -c <key-file> does not work as expected. The key gets added, but no confirmation has to be done on usage. I took the following steps in a GitBash as PoC:
$ ssh-add -c <path-to-key-file>
Enter passphrase for<path-to-key-file> (will confirm each use):
Identity added: <path-to-key-file> (<name-of-key>)
The user must confirm each use of the key
When subsequently opening a ssh connection using this key from the agent, no confirmation is needed.
Is there any plan to implement the -c flag correctly? I tested -t (timeout) and this seems to work properly.
The text was updated successfully, but these errors were encountered:
Hi,
I found this project searching for a SSH Agent working with PowerShell as well as GitBash (MSYS).
I do (currently) not use the Windows-Cert (YubiKey) features, but use it as a "normal" SSH agent. While testing, I realized,
ssh-add -c <key-file>
does not work as expected. The key gets added, but no confirmation has to be done on usage. I took the following steps in a GitBash as PoC:When subsequently opening a ssh connection using this key from the agent, no confirmation is needed.
Is there any plan to implement the
-c
flag correctly? I tested-t
(timeout) and this seems to work properly.The text was updated successfully, but these errors were encountered: