Is this one of those "shrink-wrapped" deals that has to be installed before the clock runs out, or can I sit on it for a bit until needed?

Okay, so here is the deal The owner had setup the Authy 2fa app on there phone to access their account at (for simplicity sake, let's call it) a banking site.

And then they lost their phone...

So... now, after reinstalling the Authy app on their new phone. They cannot add the site to the authy app - to get access to the site - without scanning a QR code from the site, that is apparently only on the site, that they cannot access... Did you just think of a word that rhymes with firetruck??? I did.

Which for me...begs the question: Is this kind of idiotic catch 22 level circle jerk "normal" for these (security theater fad) 2fa authentication schemes?!?

And is there any - hopefully simple - way of reuniting this poor sole with their funds?



Also (to prevent this from sounding too easy): in the long version of this story, this is not a conventional banking institution that has a brick-and-mortar storefront that someone can enter while brandishing a drivers license in front of an actual human to resolve the issue. Oh hell no...it just can't be that easy...no, this is Crypto stuff.

So maybe it is a currently active network nearby that is being redetected..

1) Would redetected networks show up with the specific names that I'd allocated to them? I'll trawl the registry and see if and where those names are still present.

-cranioscopical (July 10, 2019, 08:50 AM)

If it is a popular in the area ISP generated name, then it could be the neighbors just close enough to look the same SSID.

2) If other machines on my network retain the names of the defunct connections, would that 're-infect' the machine from which the names were expunged?

-cranioscopical (July 10, 2019, 08:50 AM)

While I'm really tempted to say no here …(at the risk of throwing gas on the fire)... It does occur to me that there was a feature similar to that built into Windows devices that shared a Microsoft Account login.

But I believe the act of deleting it from one should also be shared with the others as well. I never played with it because I hate the vary idea of a locally used (Microsoft Controlled) Microsoft Account...I just vaguely recall running across the feature once many moons ago.


Also I really like Ath's angle above.