-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot authenticate SSH after any GPG operations #59
Comments
AFAIK this is common gpg issue, it exclusively locks tokens. It was reproduced in my environment on ubuntu 18 host. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm using a YubiKey 5 NFC with WinCryptSSHAgent. I've generated a certificate in PIV certificate Slot 9a:
![image](https://user-images.githubusercontent.com/8758566/131289494-aee55415-b801-48cd-b8d1-cb318bde3dfa.png)
and it works well with WinSSH. However, after each time I perform any GPG operation (e.g., gpg --card-status, gpg --sign, etc.), I can no longer use my YubiKey with WinCryptSSHAgent to authenticate SSH connections:
![image](https://user-images.githubusercontent.com/8758566/131289775-ddfb7718-1dbd-4d75-b412-f112b3e47460.png)
"The smart card cannot perform the requested operation or the operation requires a different smart card."
Seems like that once I've performed any GPG operation, Windows will no longer read the PIV certificates stored in YubiKey until replugging.
Any idea or solution on this issue? Thanks a lot!
The text was updated successfully, but these errors were encountered: