yubikey-agent is a seamless ssh-agent for YubiKeys.
I cannot do `yubikey-agent -config` even after trying to reset the yubikey. Sometimes the error is `the default PIN did not work` and sometimes the error is `the default management key did not work`. Fresh out of package yubikey nano 5c. (Firmware 5.4.3) macOS: 12.3.1 on M1 Apple Silicon yubikey-agent 1.5 from homebrew ``` user@host:[/]$ printenv |grep sock SSH_AUTH_SOCK=/opt/homebrew/var/run/yubikey-agent.sock user@host:[/v]$ ls /opt/homebrew/var/run/ yubikey-agent.sock user@:[/var/log]$ brew services info yubikey-agent yubikey-agent (homebrew.mxcl.yubikey-agent) Running: ✔ Loaded: ✔ Schedulable: ✘ User: user PID: 12071 ``` ``` user@host:[/]$ ykman piv reset WARNING! This will delete all stored PIV data and restore factory settings. Proceed? [y/N]: y Resetting PIV data... Success! All PIV data have been cleared from the YubiKey. Your YubiKey now has the default PIN, PUK and Management Key: PIN: 123456 PUK: 12345678 Management Key: 010203040506070801020304050607080102030405060708 user@host:[/]$ yubikey-agent -setup � The PIN is up to 8 numbers, letters, or symbols. Not just numbers! ❌ The key will be lost if the PIN and PUK are locked after 3 incorrect tries. Choose a new PIN/PUK: Repeat PIN/PUK: � Reticulating splines... ‼️ The default PIN did not work If you know what you're doing, reset PIN, PUK, and Management Key to the defaults before retrying. If you want to wipe all PIV keys and start fresh, use --really-delete-all-piv-keys ⚠️ user@host:[/]$ yubikey-agent -setup --really-delete-all-piv-keys Resetting YubiKey PIV applet... � The PIN is up to 8 numbers, letters, or symbols. Not just numbers! ❌ The key will be lost if the PIN and PUK are locked after 3 incorrect tries. Choose a new PIN/PUK: Repeat PIN/PUK: � Reticulating splines... ‼️ The default PIN did not work If you know what you're doing, reset PIN, PUK, and Management Key to the defaults before retrying. If you want to wipe all PIV keys and start fresh, use --really-delete-all-piv-keys ⚠️ ```
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by AriESQ and has received 1 comments.