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 : 07. Mar 2025, 11:00:19
Autres entêtes
Organisation : NOYB
Message-ID : <vqejjv.14ks.1@ID-201911.user.individual.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14
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
VanguardLH <
V@nguard.lh> wrote:
[...]
I really hate to graft my smartphone to my hand to ensure it is readily
accessible for this security theater machinations. I'm too old for all
this jumping through hoops of fire. Rather than run through the house
looking for my smartphone (it's usually on a different floor of the
house in a charging cradle next to the side door by the garage where I
enter), I'll just forego the security theater, and go somewhere else for
e-mail service. Logging in is getting more complicated to the user and
at the server than the e-mail service itself.
In this context, i.e. Google services, there's no "run through the
house" at all:
- Google phone number verification: *one* time action.
- Google 2SV for login: *one* time per device, then mark the device as
trusted.
- Gmail access via the webUI: same as Google login.
- Gmail access via POP/IMAP/SMTP: no changes AFAIK, i.e. OAUTH2 or app
passwords (I still use app passwords).
This (non-)discussion is only about the first situation, but you keep
throwing in the other three as if they have anything to do with it.
In another response, you talk about the "security theater
machinations" of *other* (than Google) services, i.e. webshops, etc..
Please don't pollute this Google-related discussion with irrelevant
mud.
[...]