You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most likely cause of this is based on the difference between the js webauthn crypto functions and the implementation in solidity. The solidity interface is fixed length and can likely handle left padded zeros on randomly generated keys. The JavaScript version is not set up for zero padding. The function we have to extract keys will remove the padding.
This is likely causing problems with solidity functioning.
The text was updated successfully, but these errors were encountered:
I tried removing the isLeadingZero key length check and it instantly fails the existing tests, so I no longer think that's the culprit here. I'm going to try running the tests many times in a row to see if I can capture the exact bad signature. I was able to replicate this once with my local embedded-wallet-test setup, but at the time I thought it was an human introduced error since I was copying challenge and signature data back and forth via copy & paste.
The most likely cause of this is based on the difference between the js webauthn crypto functions and the implementation in solidity. The solidity interface is fixed length and can likely handle left padded zeros on randomly generated keys. The JavaScript version is not set up for zero padding. The function we have to extract keys will remove the padding.
This is likely causing problems with solidity functioning.
The text was updated successfully, but these errors were encountered: