![]() ![]() Google is not open about why they do this limit, but it would seem obvious that they do it because of the character limit QR codes have. So if you have 32 accounts inside your Google Authenticator app you will have 4 QR codes, 3 will be for 1 to 30 and the 4th will be the last 2. The Google Authenticator app will only export 10 accounts at a time when you export. The Google Authenticator app or Aegis app can read this data and import your codes (10 at a time) at any time and without the need of an internet connection. What it basically means is that this string of text is OTP migration, and all your data is inside the gibberish of letters and numbers. What’s inside the export QR Code looks like this: otpauth-migration://offline?data=CkoKDZePmX7z8qHgFlH9yVcSIlRoaXNfaXNfYW5fRXhhbXBsZTplbWFpbEBlbWFpbC5jb20aD0V4YW1wbGVfV2Vic2l0ZSABKAEwAhABGAEgAA%3D%3D What’s In The Google Authenticator Export QR Code? ![]() And (for now) I trust Apple more than Google (Authenticator) or Microsoft (Authenticator).Here is just a short list of TOTP apps that I consider better than Google Authenticator: It syncs between iOS/iPadOS and MacOS and I keep the verification codes in the Notes/Comments field. I use the Authenticator feature in Apple's Keychain. Then all the time and effort we spend dealing with passwords and 2FA can be used on something more fun or more productive. In any case, I hope passkeys ('') become widely adopted soon. ![]() But for logins that aren't for anything that needs to be kept private or secure, syncing via your Google account probably is OK in most circumstances. That way you maintain complete control over critical information and avoid any exposure to the cloud. If you use GA 2FA codes for anything sensitive or confidential, such as banking (risk: losing control over a checking account or credit card) or mobile phone carrier accounts (risk: becoming the victim of a SIM swapping attack), it's probably better to copy the codes over to another device manually. I think the desirability of this new feature depends on how you use Google Authenticator. The latest version of the app is required, and on iPhone and iPad, it can be downloaded from the App Store for free. Adding Google Account support will require signing into the account in the Google Authenticator app, and once that is done, codes will be automatically backed up and restored on any new device where you sign in to your Google Account. ![]() Google Account integration for Google Authenticator is available on both iOS and Android devices. Google says with one-time passwords available in a Google Account, users are "better protected from lockout," increasing convenience and security. Prior to the integration of Google Account support, all codes in the Google Authenticator app were stored on device, which is problematic when a device is lost. With Google Account support, one-time passwords can be saved in the cloud, so if you lose the device with your Google Authenticator app installed, you won't lose access to all of your authentication codes. The Google Authenticator app used to store one-time access codes for account security now supports backups and syncing across devices using a Google Account, Google announced today. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |