Fixes #80. * * * Example secret provided by Google when trying to enable MFA for Google account (with the note that spaces can be ignored): ``` qea4 ptmn kvd5 ampv wm6d rc6m bbh4 urbo ``` Example respective URI: ``` otpauth://totp/Google%3Adaniel%40buttercms.com?secret=qea4ptmnkvd5ampvwm6drc6mbbh4urbo&issuer=Google ``` Result: ``` $ otp add uri google Enter URI: Repeat for confirmation: Usage: otp add uri [OPTIONS] ALIAS Try 'otp add uri -h' for help. Error: invalid Base32 value; Non-base32 digit found ``` This _is_ Base32-encoded, **however**, Google ignores the [official spec](https://datatracker.ietf.org/doc/html/rfc3548#section-5) that instructs to use **uppercase** letters for Base32-encoded value. On the other hand, the spec also mentions case insensitivity of the value: > The Base 32 encoding is designed to represent arbitrary sequences of > octets in a form that needs to be case insensitive So maybe the issue comes from the spec being ambiguous. We should make the `secret` parameter case-insensitive.

Commits

Commits on Dec 28, 2023

Fix secret not being case-insensitive

Fix `secret` not being case-insensitive