Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Advisor: A user may temporarily verify that app reported as "... as a drop-in replacement for apps such as Google Authenticator" statement is wrong

Open
  • Is something wrong?
#41 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authentication, security

Research direction

No files, tests, or entry points are named. Start by locating the Advisor messaging and the app-clock synchronization flow, then clarify which warning, suggestion, and tracking behavior are required before defining what completion means.

Written by the indexing model from the issue text.

Description

Advisor: A user may temporarily verify that 'Authenticator: 2FA Client' app reported as "... as a drop-in replacement for apps such as Google Authenticator" statement is wrong (even if not yet also reported from 'Microsoft Edge Add-ons' site). :-o 0:-)
This may happen right after scanning a QR code typically meant for Google Authenticator and so if/when this happens, and the need to use 'Authenticator: 2FA Client' app is related to its use with a Financial Institution or a Bank, then user may immediately think to remove app and immediately get another Extension with same functionality.
But Advisor might however even better help to prevent that and to also further help user to understand that main reason for failed acceptance of a numeric code provided by Authenticator is another one.
So it could also provide user the additional suggestion to use [ Sync clock with Google ] and even the additional feature to track if doing that has already been done or not (and maybe it could even be quite nice to know how often it might be useful to do it, unless for instance Advisor may even start to do a quick background own check to better be sure of how much time difference there might already be with Google clock before suggesting user to do a [ Sync clock with Google ] to avoid any issue related to any such time difference).
P.S. I'm also saying this because for instance I've always decided to keep my Windows client clock some minutes in advance (but anyway always less than 5 minutes maximum required to fit Kerberos specifications), and quite obviously because of this numeric code generated by 'Authenticator: 2FA Client' app only started to work perfectly after I completed a [ Sync clock with Google ] and even some months after that I was able to correctly configure 'Authenticator: 2FA Client' with test account and then even use it correctly to enable 2FA authentication with Discord. 0:-)
Also, since it's only 'Authenticator: 2FA Client' app usage of PC clock that gets synchronized with Google, and not PC clock itself, it would be more correct to say to user [ Sync app clock with Google ].
Regards

Dominant language
HTML
Stars
57
Forks
243
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Authenticator-Extension/authenticator.cc

All issues in Authenticator-Extension/authenticator.cc

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.