We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The (new) "Allow accessories to connect" dialog on MacOS Ventura (13):
(example for other device)
When I insert me Solo Key V2 this diealog only appear for a few milliseconds and the device is connected but not matched and registered:
ioreg -p IOUSB | grep Solo | +-o Solo 2 Security Key@01100000 <class IOUSBHostDevice, id 0x10000cd26, !registered, !matched, active, busy 0, retain 13>
If I disable accessories security (autom. allow when unlocked), the token is connected correctly and works as expected:
ioreg -p IOUSB | grep Solo | +-o Solo 2 Security Key@01100000 <class IOUSBHostDevice, id 0x10000cd46, registered, matched, active, busy 0 (52 ms), retain 45>
This doesn't happen with other USB device on this machine (unfortunately I don't have another macOS 13 device here to cross check this).
Anyone has the same problem? May that have to do with some timeout behaviour of the token?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The (new) "Allow accessories to connect" dialog on MacOS Ventura (13):
(example for other device)
When I insert me Solo Key V2 this diealog only appear for a few milliseconds and the device is connected but not matched and registered:
If I disable accessories security (autom. allow when unlocked), the token is connected correctly and works as expected:
This doesn't happen with other USB device on this machine (unfortunately I don't have another macOS 13 device here to cross check this).
Anyone has the same problem? May that have to do with some timeout behaviour of the token?
The text was updated successfully, but these errors were encountered: