this post was submitted on 13 Oct 2023
215 points (88.5% liked)

Mildly Infuriating

35045 readers
4 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago
MODERATORS
 

EDIT: You know, after some time to cool off, Google Authenticator 2FA can still be enabled and isn't being phased out like the less secure SMS 2FA, so it's really not the end of the world here. The chance of permanent lockout is avoided, even if the whole Google Prompt system is still wack.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 1 year ago* (last edited 1 year ago) (1 children)

The problem is they are turning OFF the SMS and instead sending a special dialogue to a nonexistent device for the user to hit a prompt. The device was never used, though, and it was never set up for 2FA. My default has always been SMS which they are now disabling.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

Deprecating SMS authentication is a good thing, in all honesty. SMS is not a secure form of data transfer, and is trivially intercepted. You can buy and setup an illegal Stingray device relatively easily, and capture basically all wireless data from a phone within range.

That said, if the device was truly never used for 2FA, then there wouldn't be any push-based 2FA on the account to begin with. Unless there's another device that's been authenticated with your account somewhere, like an old phone. In which case, that's where your login requests are being pushed to. That's a setting that can only be enabled by successfully authenticating with a device at least once in the past.

If there was never any other authenticated device, then that setting on your account isn't there. Enabling that feature is a two-step process, and step 1 involves configuration on a local device before it can be enabled remotely on your account.

[–] [email protected] -1 points 1 year ago* (last edited 1 year ago) (2 children)

SMS could potentially be a secure form of Data Transfer if companies weren't allowed by limp dinosaur legislators to gut your phone for any useable data with a simple app, but yeah I can see how it's current state is lackluster.

You're wrong, btw, the Google Prompts feature is Default and cannot be turned off.

[–] [email protected] 2 points 1 year ago

The SMS vulnerability is not because of your apps. It's because of the LTE protocol itself. It can be intercepted or redirected without touching your phone.

[–] [email protected] 1 points 1 year ago (1 children)

You’re wrong, btw, the Google Prompts feature is Default and cannot be turned off.

Only if there's a previously-authenticated device. That setting can't be enabled without a key, and one of the required keys is produced locally by a logged-in device (which is why your device is trusted to stay logged in indefinitely). If enabled without a key, it's nonfunctional and should error itself out and revert to a disabled state.

If that somehow hasn't happened (which, in all honesty, would be very surprising to learn) and the setting is enabled on your account, then that'd be something you'd need to submit a request to Google to have fixed, otherwise you have zero recovery on that account.

Are you a thousand percent sure you've never had any other device logged into that Google account? When you attempt to log in, it should show you the device name it's sending the request to. For instance, when I log into my Gmail from an Incognito window right now, it says to check my Pixel 6 Pro. What's it saying for you?

[–] [email protected] 1 points 1 year ago (1 children)

No, I'm telling you, it's on by default when you purchase a Google Device. It doesn't need to be set up.

[–] [email protected] -1 points 1 year ago (1 children)

What device does it say it's sending the request to?

[–] [email protected] 1 points 1 year ago (1 children)

A device. The fact that any device is getting a google prompt and it cannot be disabled is the issue.

[–] [email protected] 1 points 1 year ago (1 children)

Right. I think you can see where I'm going with this. The fact that you're being dodgy with the question is making me question your motives with this post.

So, what device? You don't have to tell me the name, but describe it to me. Is it the device that you flashed a new OS onto?

[–] [email protected] 1 points 1 year ago (1 children)

It's not constructive to answer your question instead of explain the situation to you for the 8th time. There is only one device and it was wiped and can never be recovered, not even by restoring the OS, but the Google Prompt is still the default option forever now. I found this mildly infuriating.

The best solution is to use something like Google Auth since only the SMS is being phased out. Do you understand now or de we need to repeat this again and again?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

So, when you said "The device has never existed", you realize how that was a bit misleading, right? The way you've been presenting this situation would suggest that Google enabled 2FA in an impossible manner.

The device existed. You ignored the warnings and wiped the device before transferring your authentication elsewhere. There's plenty of things to be critical of Google over, but flagrant user error like this isn't one of them.