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
Doing some tests in the console during the Stax porting, I noticed the generated password varied from what is typed through USB and what is displayed on the device.
On top of that, while writing this post, I also noticed that typing the password in my browser (Chrome 111.0.5563.64) does not have the same behavior as on the console.
Example
Let's say I have OWA3u8afHKxGijFD7rCx displayed on the device, whatever the keyboard.
On the console:
OWA3u8afHKxGijFD7rCx < Qwerty
owa3u8afHKxGijFD7rCx < Qwerty International
OZQ#u*qfHkxGijfD&rCx < Azerty
On the browser:
OWA3u8afHKxGijFD7rCx < Qwerty
OWA3u8afHKxGijFD7rCx < Qwerty International - changed to be the same as plain Qwerty
OZQ#u*qfHKxGijFD&rCx < Azerty
The text was updated successfully, but these errors were encountered:
Doing some tests in the console during the Stax porting, I noticed the generated password varied from what is typed through USB and what is displayed on the device.
On top of that, while writing this post, I also noticed that typing the password in my browser (Chrome 111.0.5563.64) does not have the same behavior as on the console.
Example
Let's say I have
OWA3u8afHKxGijFD7rCx
displayed on the device, whatever the keyboard.On the console:
OWA3u8afHKxGijFD7rCx
< Qwertyowa3u8afHKxGijFD7rCx
< Qwerty InternationalOZQ#u*qfHkxGijfD&rCx
< AzertyOn the browser:
OWA3u8afHKxGijFD7rCx
< QwertyOWA3u8afHKxGijFD7rCx
< Qwerty International - changed to be the same as plain QwertyOZQ#u*qfHKxGijFD&rCx
< AzertyThe text was updated successfully, but these errors were encountered: