Cannot add second PicoKey to Microsoft #185
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
No matter which one added first, the second one will not be able to add.
Waveshare RP2350-One
RequestData
ResponseData
Waveshare RP2350-Zero
RequestData
ResponseData
But is this allowed by MS?
Yes, the
OneI added into MS can use for login.Where do you get the logs from?
I use
Charles Proxyto record HTTP Request, data is from this API.https://account.live.com/API/Proofs/ProvisionPasskeyPlease steps to reproduce.
I have email you a video with subject
Reproduce about failing add second Picokey to MS.Did you try it with a Yubikey?
Sadly, I don't have genuine Yubikey.
But I can add IdemKey to MS after adding any PicoKeys.
RequestData
ResponseData
It’s hard to figure out what’s going on Microsoft’s backend without a more explicit message. It’s even harder by the fact that the 1st key can be registered without problems but not the 2nd, no matter the order.
I think the problem is
CRED_PROTO_RESIDENT, allPicoKeysuse the same 4 Bytes make MS thought is identical Key.Therefore, I change
CRED_PROTO_RESIDENTstring toYUBIon anotherPicoKey, then I can add this key to MS.I pushed a fix for this. I tested with MS and Bitwarden and both work smoothly. As usual, nightly available tomorrow.