NK3A mini in semi-broken state - chrome stopped reading stored keys

[noerw]

here's what i did:

1. register the authenticator via fido2/webauthn on 5 sites
2. set a pin
3. update firmware from 1.1.0 to 1.2.2
4. store a resident ssh ed25519 key (generated with ssh-keygen -t ed25519-sk -O application=ssh:git -O resident)
5. store another resident ssh ed25519 key with a different name

here's the issues i encountered:

1. after the last action, chrome settings page stopped being able to read out 'sign in data', i.e. the two resident ssh keys.
2. at an unknown point after step 2 the webauthn login on one site intermittently stopped working. this can very well be a bug in that application, but i can't be sure. feel free to ignore this until i got to a reliable way to reproduce this
3. nitropy nk3 test reports no errors

i'd love to help debugging this, but i have no idea how, pointers would be helpful.

[robin-nitrokey]

Thanks for the report! I will try to reproduce it locally and add some tests to pynitrokey to reproduce the Chromium issue. Does the stick still respond to other commands after the Chromium issue (without removing it)? Does the LED color change?

[szszszsz]

Can you see anything in the device log after seeing this error message? The log is under this URL:

• chrome://device-log/ (you might need to copy and paste this into the URL bar)