Skip to content
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

Distinguishing lowercase L from uppercase I (l vs I) #33

Open
erjoalgo opened this issue Jun 9, 2021 · 5 comments
Open

Distinguishing lowercase L from uppercase I (l vs I) #33

erjoalgo opened this issue Jun 9, 2021 · 5 comments

Comments

@erjoalgo
Copy link

erjoalgo commented Jun 9, 2021

When trying to make use of the "Show password" feature in #13, I've been repeatedly locked out of my account due to too many failed password attempts. The problem is that it is impossible to distinguish between lowercase L and uppercase I.

Can we change the font so that these two characters can be distinguished from each other?

09-Jun-2021-01:28:45

@erjoalgo
Copy link
Author

erjoalgo commented Jun 9, 2021

Here's an example. Is it lI (108, 73) or lI (73, 108)? Is it an O or a zero?

@erjoalgo
Copy link
Author

erjoalgo commented Jun 9, 2021

20210609_013523_HDR

@erjoalgo erjoalgo changed the title Distinguishing lowercase l from uppercase I Distinguishing lowercase L from uppercase I (l vs I) Jun 9, 2021
@lpascal-ledger
Copy link
Contributor

I'm keeping this opened, however in this matter I fear we are dependent from OS implementation here.

@SeekerFS
Copy link

Then can we forward this to the people who can do something about it?

@SeekerFS
Copy link

The responses on official ledger keeps being: "Ledger apps don't have this problem, because they use base-58 for encoding that solves this exact issie".
So maybe Passwords should start using it too, could a new enforcing option be added, that would be off by default?
https://learnmeabitcoin.com/technical/keys/base58/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants