wp-plugin-hostgator
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114ol-scrapes
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114Source:https:\/\/techcrunch.com\/2023\/04\/24\/google-authenticator-can-now-sync-2fa-codes-to-the-cloud\/<\/a><\/br> Google Authenticator just<\/a> got an update that should make it more useful for people who frequently use the service to sign in to apps and websites.<\/p>\n As of today, Google Authenticator will now sync any one-time two-factor authentication (2FA) codes that it generates to users\u2019 Google Accounts. Previously, one-time Authenticator codes were stored locally, on a single device, meaning losing that device often meant losing the ability to sign in to any service set up with Authenticator\u2019s 2FA.<\/p>\n To take advantage of the new sync feature, simply update the Authenticator app. If you\u2019re signed in to a Google Account within Google Authenticator, your codes will automatically be backed up and restored on any new device you use. You can also manually transfer your codes to another device even if you\u2019re not signed in to a Google Account by following the steps on this support page<\/a>.<\/p>\n Some users might be wary of syncing their sensitive codes with Google\u2019s cloud \u2014 even if they did originate from a Google product. But Christiaan Brand, a group product manager at Google, asserts it\u2019s in the pursuit of convenience without sacrificing security.<\/p>\n \u201cWe released Google Authenticator in 2010 as a free and easy way for sites to add \u2018something you have\u2019 2FA that bolsters user security when signing in,\u201d Brand wrote in the blog post announcing today\u2019s change. \u201cWith this update we\u2019re rolling out a solution to this problem, making one time codes more durable by storing them safely in users\u2019 Google Account.\u201d<\/p>\n Of course, Google hasn\u2019t always maintained an abundance of transparency around Authenticator\u2019s roadmap. The app began as an open source project, but later became proprietary; the official open source forks of the Android, iOS and BlackBerry apps haven\u2019t been updated in years.<\/p>\n Fortunately, if Authenticator doesn\u2019t float your boat, there are loads of alternatives for 2FA. Authy is among the most popular, but Duo is another popular choice \u2014 and, for what it\u2019s worth, The New York Times\u2019 top pick<\/a>.<\/p>\n<\/p><\/div>\n <\/br><\/br><\/br><\/p>\n
\nGoogle Authenticator can now sync 2FA codes to the cloud<\/br>
\n2023-04-24 21:49:43<\/br><\/p>\n