Article <vq7392.162c.1@ID-201911.user.individual.net>

Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <vq7392.162c.1@ID-201911.user.individual.net>

Deutsch English Français Italiano

<vq7392.162c.1@ID-201911.user.individual.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Frank Slootweg <this@ddress.is.invalid>
Newsgroups: comp.mobile.android
Subject: Re: Google will no longer send SMSs with six digit codes for verification
Date: 4 Mar 2025 13:38:32 GMT
Organization: NOYB
Lines: 23
Message-ID: <vq7392.162c.1@ID-201911.user.individual.net>
References: <803e9lxp44.ln2@Telcontar.valinor> <vq21n7$rq33$1@dont-email.me> <vq5lo0$3sv4j$1@matrix.hispagatos.org> <vq5v83$1nj23$1@dont-email.me>
X-Trace: individual.net I0mc4e1vTxzIu9UQoujCaAb//fmezhqhn79STHnfdiUjBC6L3d
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:dU7D7Z0DaF68mowBQxAA5EYPZ7s= sha256:gOCEQBSbCP29m72cwGGl9BodUppnFTzyrwjisXO87Is=
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>