I enrolled in Google's Advanced Protection and lost access to my personal Google account on my phone. When attempting to log in, got their "We can't be sure you're actually you" error. Unenrolled. Still can't access on phone; password is correct but I'm tripping something.
-
Show this thread
-
I still have access on my personal laptop; my account still shows the phone (which has not changed) as being on the list of devices used in last 30 days. What are my options here? Google is suggesting the account recovery flow but I am terrified that will lock out laptop, too.
2 replies 0 retweets 25 likesShow this thread -
Sidenote: and this is the experience that a relatively sophisticated engineer with a material security background has when dealing with account lifecycle management. Imagine how fun it is for civilians.
3 replies 2 retweets 104 likesShow this thread -
Patrick McKenzie Retweeted Patrick McKenzie
Aha, I have successfully blackboxed Google's authentication product decisions to determine the problem: you just can't use iPhones and FIDO/etc keys together without a backup 2FA method. (They don't tell you that.)https://twitter.com/patio11/status/1140412173593636864 …
Patrick McKenzie added,
Patrick McKenzie @patio11Think I found the bug. Here, friendly Googler followers, are the reproduction steps: 1) Turn on 2FA via FIDO/etc keys on your Google account 2) Turn off backup 2FA options because you're conscientious 3) Attempt to login on an iPhone 4) Get a useless error message Fix please. https://twitter.com/patio11/status/1140404696256937984 …Show this thread2 replies 3 retweets 42 likesShow this thread -
Replying to @patio11
Are you using Google Smart Lock? That supports Bluetooth FIDO.
1 reply 0 retweets 0 likes
I think I have a Bluetooth-compatible FIDO key (80% confidence? It's not the one work issued, for obvious reasons.) and was using Google Smart Lock. And re-checked product sheet; seems was NFC rather than Bluetooth.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.