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

Improve usability by adoptiny an alternative Base32 charset #119

Closed
wants to merge 1 commit into from
Closed

Improve usability by adoptiny an alternative Base32 charset #119

wants to merge 1 commit into from

Conversation

evilaliv3
Copy link

@evilaliv3 evilaliv3 commented May 20, 2021

This commit propose to use the charset ABCDEFGHJKLMNPQRSTUVWXYZ23456789 in place of ABCDEFGHIJKLMNOPQRSTUVWXYZ234567.

The proposed charset is more usable as it do not contain any character in the set [O, 0, I, 1]

This commit propose to use the charset ABCDEFGHJKLMNPQRSTUVWXYZ23456789 in place of ABCDEFGHIJKLMNOPQRSTUVWXYZ234567.

The proposed charset is more usable as it do not contain any character in the set [O, 0, I, 1]
@kislyuk
Copy link
Member

kislyuk commented May 21, 2021

Thanks for the PR. This is a good idea, unfortunately it is outside the scope of this library because using such an alphabet would make PyOTP inconsistent with the key URI format specification (https://github.com/google/google-authenticator/wiki/Key-Uri-Format#secret) and incompatible with other OTP implementations. Specifically, the key URI format spec mandates the use of the default RFC 3548 base32 alphabet without padding.

@kislyuk kislyuk closed this May 21, 2021
@evilaliv3
Copy link
Author

Thank you @kislyuk; yep @zenmonkeykstop noticed the same and i was about to close this pull myself.

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

Successfully merging this pull request may close these issues.

2 participants