Skip to content

Scanning QR codes with SHA-512 (or SHA-256) generates wrong codes unless added manually #1593

Description

@Alisalimi11

Describe the issue

Hi,

I noticed an issue when scanning QR codes that use SHA-512 for two-factor authentication.

When I scan a QR code where the algorithm is set to SHA-512, the extension produces an incorrect code that does not match the actual token. However, if I enter the same account using "Manual Entry" and change the algorithm to SHA-512 in the advanced settings, it works completely fine and generates the correct code.

I also tested the exact same QR code on other authenticator apps like 2FAS and Aegis, and both of them scan and handle the SHA-512 algorithm out of the box without any problems.

It seems that during the QR scan/import process, the algorithm parameter is not being recognized properly and defaults back to SHA-1, while manual entry saves it correctly.

Could you please look into this so that scanned QR codes with SHA-512 (and other algorithms like SHA-256) are automatically detected and saved with the right algorithm?

Thank you!

Browser

Chrome

Browser Version

153.0.8010.53

Extension Version

8.0.1

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions