Too late for me, but a pleasingly fast and pro-active response from AWS (which rather shows Google up) just received by email: "If you are an AWS customer who uses Google Authenticator for iOS as a multi-factor authentication device to secure your AWS account via AWS MFA ( http://aws.amazon.com/mfa/ ), please read on. We are writing to inform you that Google has recently released an update to the Google Authenticator…
Warning: Google Authenticator upgrade loses all accounts
121–130 of 176 posts
Re: Warning: Google Authenticator upgrade loses all accounts
#122Re: Warning: Google Authenticator upgrade loses all accounts
#123Too late for me, but a pleasingly fast and pro-active response from AWS (which rather shows Google up) just received by email: "If you are an AWS customer who uses Google Authenticator for iOS as a multi-factor authentication device to secure your AWS account via AWS MFA ( http://aws.amazon.com/mfa/ ), please read on. We are writing to inform you that Google has recently released an update to the Google Authenticator…
Re: Warning: Google Authenticator upgrade loses all accounts
#124Re: Warning: Google Authenticator upgrade loses all accounts
#125Re: Warning: Google Authenticator upgrade loses all accounts
#126Too late for me, but a pleasingly fast and pro-active response from AWS (which rather shows Google up) just received by email: "If you are an AWS customer who uses Google Authenticator for iOS as a multi-factor authentication device to secure your AWS account via AWS MFA ( http://aws.amazon.com/mfa/ ), please read on. We are writing to inform you that Google has recently released an update to the Google Authenticator…
What's even worse is with a certain iOS update that may or may not be launching in the next few weeks will make this advice impossible. 3 words for you - Auto updating apps
Re: Warning: Google Authenticator upgrade loses all accounts
#127Earlier quoted context omitted.
Have you tested this? Are the barcodes not time pertinent?
(I've studied two-factor authentication using HOTP and TOTP, and built a node.js implementation of it.) The QR codes simply divulge a URI with the secret key for generating tokens. They look like: otpauth://totp/[keyname]?secret=[secretkey] The secret key is used in the app in conjunction with a moving factor (usually 30-second intervals of time) to generate a numerical hash of sorts for that interval of time, which…
Re: Warning: Google Authenticator upgrade loses all accounts
#128Earlier quoted context omitted.
Luckily I was still logged into all my accounts (my Dropbox account suddenly dropped from Google's app like a week ago) Duo seems to be quite nice, I doubt I'll end up using the backup codes. Incidentally, GitHub has it right - "download a text file of your backup codes" is much easier than "print this page nad hope you don't lose it"; I find find(1) outpaces my frantic drawer-emptying.
I've just noticed that Google has the download-as-text functionality now too.
Re: Warning: Google Authenticator upgrade loses all accounts
#129Earlier quoted context omitted.
(I've studied two-factor authentication using HOTP and TOTP, and built a node.js implementation of it.) The QR codes simply divulge a URI with the secret key for generating tokens. They look like: otpauth://totp/[keyname]?secret=[secretkey] The secret key is used in the app in conjunction with a moving factor (usually 30-second intervals of time) to generate a numerical hash of sorts for that interval of time, which…
Would this mean that these two values are stored locally? Could they be extracted from the GA app?
One thing to note is that neither Google Authenticator nor Duo Security let you display the secret itself in the app. Another thing to note is that Google Authenticator keys seem to be backed up if you back up your iPhone to a computer using iTunes (mine were still there after a restore).
Re: Warning: Google Authenticator upgrade loses all accounts
#130I guess Google support might get too many reset requests to show due diligence in verifying authenticity of the requests.