Difference between revisions of "Google Authenticator"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
== See also == | == See also == | ||
* [[ThreatFabric]] | * [[ThreatFabric]] | ||
| − | * | + | * {{Yubikey}} |
* [[FIDO2]] | * [[FIDO2]] | ||
| + | * {{Google Authenticator}} | ||
* {{MFA}} | * {{MFA}} | ||
{{CC license}} Source: wikipedia | {{CC license}} Source: wikipedia | ||
[[Category:Security]] | [[Category:Security]] | ||
Revision as of 11:18, 11 November 2020
wikipedia:Google Authenticator (2010) is a software-based authenticator by Google that implements two-step verification services using the Time-based One-time Password Algorithm (TOTP; specified in RFC 6238) and HMAC-based One-time Password algorithm (HOTP; specified in RFC 4226), for authenticating users of software applications.[1]
The Android OS allows apps to protect their users by blocking other apps from screenshotting their content. This is done by adding a "FLAG_SECURE" option inside the app's configuration.
Related terms
- Authy (Twilio) (TOTP)
- Duo
- Ubuntu:
apt-get install libpam-google-authenticator - FreeOTP
- Hashcat
- brew install google-authenticator-libpam
See also
- ThreatFabric
- YubiKey, Yubico, FIDO security keys, FIDO2, WebAuthn, 5C Nano, YubiKey Manager,
ykman - FIDO2
- Google Authenticator, sync,
libpam-google-authenticator,google-authenticator-libpam(macOS),google-authenticator - MFA: FreeOTP, Google Authenticator, Okta Verify, Duo Security, Microsoft Authenticator, Strong customer authentication, Dualshield, HOTP, TOTP, OATH, Authy, Push authentication, google-authenticator, Duo Mobile,
DenyAllExceptListedIfNoMFA, Configure MFA on AWS, LastPass Authenticator mobile app
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Source: wikipedia
- ↑ "GitHub - google/google-authenticator: Open source version of Google Authenticator (except the Android app)". GitHub.
These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (TOTP) algorithm specified in RFC 6238.
<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Advertising:
