-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow spaces in OTP base32 secret #136
Comments
Can you provide an example please? I am not sure I fully understand what groups you are referring to. |
Groups of four characters, e. g. `1234 5678 9012 3456`.
|
robinkrahl
added a commit
to robinkrahl/nitrocli
that referenced
this issue
Apr 9, 2021
Some sites as GitLab display their OTP secrets as base32 strings in groups separated by spaces. Previously, the user had to manually remove the spaces before passing the secret to nitrocli. But as the space can never be part of the base32 string itself, we can unambigously identify it as a separator and remove it from the secret before processing it. Fixes d-e-s-o#136.
d-e-s-o
pushed a commit
that referenced
this issue
Apr 10, 2021
Some sites, such as GitLab, display their OTP secrets as base32 strings in groups separated by spaces. Previously, the user had to manually remove the spaces before passing the secret to nitrocli. But as the space can never be part of the base32 string itself, we can unambiguously identify it as a separator and remove it from the secret before processing it. Fixes #136
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some sites display the base32 secret for OTP authentication in groups, separated by spaces. nitrocli should be able to handle such input without requiring the user to manually remove the spaces.
The text was updated successfully, but these errors were encountered: