Sujet : Re: Google will no longer send SMSs with six digit codes for verification
De : this (at) *nospam* ddress.is.invalid (Frank Slootweg)
Groupes : comp.mobile.androidDate : 04. Mar 2025, 14:38:32
Autres entêtes
Organisation : NOYB
Message-ID : <vq7392.162c.1@ID-201911.user.individual.net>
References : 1 2 3 4
User-Agent : tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
AJL <
noemail@none.com> wrote:
[...]
When I fire up a NEW Android device and sign into my Google accounts for
the first time, after I put in my user name and password it sends a
white screen to my other Android devices on which I pick one and push a
"Yes it's me" button for verification and the new device is then signed on.
I always thought that Google Authenticator was responsible but after my
last post I looked at it and don't see any indication that it is or is
not responsible for this verification. Perhaps one of the more technical
folks here can explain how this (non-SMS) verification process works...
The 2SV mechanism you're using is called 'Google prompt', i.e. you get
a prompt on your device(s).
See the '2-Step Verification' section of your Google account [1].
There you will see 'Google prompt' as one of the options in 'Second
steps'. It will list the number of devices which can get the prompt and
('>') which devices (in my case my phone and a tablet).
[1] <
https://myaccount.google.com/signinoptions/twosv>
List of your 'Google prompt' devices:
<
https://myaccount.google.com/two-step-verification/prompt>