Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#41 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
authentication, security

Línea de trabajo

No se nombran archivos, pruebas ni puntos de entrada. Empieza por localizar la mensajería de Advisor y el flujo de sincronización de app-clock; después, aclara qué comportamiento de advertencias, sugerencias y seguimiento se requiere antes de definir qué significa que esté completado.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
HTML
Estrellas
58
Forks
245
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Authenticator-Extension/authenticator.cc

Todos los issues de Authenticator-Extension/authenticator.cc

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.