Skip to content
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

[macOS] Yklocker locks access to Yubikey, when verifying it is connected #78

Open
stefan-ivarsson-sciber opened this issue Mar 21, 2024 · 0 comments

Comments

@stefan-ivarsson-sciber
Copy link

stefan-ivarsson-sciber commented Mar 21, 2024

At the very moment Yklocker checks if the Yubikey is still connected there is a slight possibility for an access issue.
For instance when using gpg-agent to sign git commits, should the access to the key happen simultaneous you may experience the following error message.

gpg: signing failed: Bad file descriptor
gpg: [stdin]: clear-sign failed: Bad file descriptor

A similar error message may happen when the gpg-agent is used in order to use the Yubikey as SSH key storage

sign_and_send_pubkey: signing failed for RSA "cardno:00 000 000" from agent: agent refused operation
sign_and_send_pubkey: signing failed for RSA "(none)" from agent: agent refused operation

Both issues are dependent on timing and repeated tries usually allow you to use the key as intended at some point, when the Yubikey is available for use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant