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

TOTP does not automatically add base32 padding for Amazon secret keys #3825

Closed
derekjc opened this issue Nov 9, 2019 · 1 comment
Closed

Comments

@derekjc
Copy link

derekjc commented Nov 9, 2019

I'm trying to "setup TOTP" for my amazon login. It's failing with the error You have entered an invalid secret key. The key must be in Base32 format. Example: JBSWY3DPEHPK3PXP

Expected Behavior

OTP key should be accepted

Current Behavior

OTP key is invalid

Possible fix

Automatically add base32 padding (like oathtool and other authenticator apps). For example, adding ==== to the keys below fixes the issue

Steps to Reproduce

Generate an OTP key using Amazon. Following are examples(no longer in use).
5FT7WWLR3OWA26NWZ6DFCRLM3NGEWVUE7ZYWFMGCWBGJ7K3IEWDA
QGRCOIYTPUPG37U54CDNHJEZU323J7QV63ZMKOMVPT2CCA7ZVWYA

Debug Info

KeePassXC - Version 2.5.0
Revision: 1ab8a9f

Qt 5.12.4
Debugging mode is disabled.

Operating system: Pop!_OS 19.10
CPU architecture: x86_64
Kernel: linux 5.3.0-20-generic

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (signed and unsigned sharing)
  • YubiKey

Cryptographic libraries:
libgcrypt 1.8.4

@derekjc derekjc added the bug label Nov 9, 2019
@varjolintu
Copy link
Member

This is fixed with #3622.

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

No branches or pull requests

2 participants