When the Google Authenticator is asking for you to scan a code, it's essentially saying, "Hi! In order for me to generate one time passwords for this, I need to know what the seed is!".īoth the QR code/bar code and the "enter a key" option do the same thing. That underlying seed lives on both the server (aka the service you're trying to log into) and the authenticator itself (which can be a YubiKey or Google Authenticator, etc) The TL DR way that one time passwords work is such that you have an underlying seed that all future one time passwords are based off of, and the password that is generated can only be used once. In its initial design, the Google Authenticator was, and still is designed to support a protocol known as One Time Password (OTP) Provided by whom, when? Nothing about a u2f device. I started the begin setup and it gave me two options, to scan a barcode (even though they have a QR code pictured) or to Enter provieded key. I read something about google authenticator and installed it.
Until Amazon allows for far more secure multi-factor authentication, unfortunately there isn't any way around that unless they allow for a better "lock" (like U2F)
The only thing that will work with that lock are the codes they are sending to your cellphone. and Amazon only has one lock (SMS One Time Passwords) To speak metaphorically, it sounds like you have three different "keys".
0 kommentar(er)
