Describe the bug
After the macOS 13.2 update vegas-crendetials no longer can use a yubikey directly even though it is plugged in
System (please complete the following information):
- OS: macOS
- OS Version: 13.2
- Tool Version: 0.14.4
- Tool Installation Method: brew
- Credential Process invoked via: awscli
To Reproduce
Steps to reproduce the behavior:
- Just run any command with aws, eg,
aws s3 ls
- The prompt given no longer asks for the yubikey password, just prompts for:
🔑 MFA: Input Token (via CLI stdin / Yubikey touch):
Expected behavior
A clear and concise description of what you expected to happen.
- Open up an aws commend with
aws s3 ls
- vegas-credentials prompts for a yubikey password
- vegas-credentials prompts to touch the yubikey to complete the auth
- Command completes
Additional context
With identical configuration, this worked just fine in macOS 13.1. With the new 13.2 update, something broke and it looks like vegas-credentials is unable to detect that the yubikey is indeed plugged in and ready.
Describe the bug
After the macOS 13.2 update vegas-crendetials no longer can use a yubikey directly even though it is plugged in
System (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
aws s3 lsExpected behavior
A clear and concise description of what you expected to happen.
aws s3 lsAdditional context
With identical configuration, this worked just fine in macOS 13.1. With the new 13.2 update, something broke and it looks like
vegas-credentialsis unable to detect that the yubikey is indeed plugged in and ready.