-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
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
Different keyboard layouts cause different passwords outputs #5
Comments
I also noticed, sometimes on Android the passwords doesn't get typed like usual. Sometimes there's duplicate characters inserted. Maybe some kind of unrelated driver problem. |
we'll have an update supporting different layouts soon - thanks for the report on Android, we'll also have a look. Might have been fixed by our recent modifications too. |
Update pushed if you can give it a try |
Amazing, I'll test this release. Will it wipe my password database when deleting/updating? Just curious before proceeding. Thanks! |
I see the same on Android... though typically it manifests as only typing 5-10 characters of the password. |
Is this still happening with latest version (>1.0.0) ? |
This could be related to #41. I'll keep this issue opened for now. |
Hi! I just noticed this issue while trying out my Ledger in an Android tablet. Everything seems to work but when it types the password it seems to use a different keyboard layout thus my passwords are all invalid.
I replicated that on OS X as well, when I switch between Canadian French and English US the passwords get typed differently. I doubt this is something we can prevent from the Ledger software itself right? Since the system is the one who picks the layout?
So I should in this case, always use US keyboard if I want my password to reliably work?
For example a password in CF:
fj;IE8 H1Ti_lL/TOF¨Q
and in US:
fj;IE8 H1Ti_lL`TOF{Q
Some special chars aren't the same as you can see.
Just thought I'd share this here, don't know if we can call that a bug but I think it should be mentioned somewhere that this could lead to big issues while trying to login from another machine.
Keep up the amazing work!
The text was updated successfully, but these errors were encountered: