You already did.
At long last, Rogue Trader.
Does not computeIf only vatniks could be trusted
Strong vibes of P*lack ancestryDoes not computeIf only vatniks could be trusted
If only Nafoids encryption was descent, need to put those coding socks tranny brigade on overtime.If only vatniks could be trusted to not break into people's accounts and sabotage the post database by mass deleting everything for teh epic lulz then maybe we wouldn't have to be 2FAcucked.
You know, I have kind of a crazy idea...I couldn't log in the codex, on my phone, for 2 weeks, because every code sent to me didn't work until today.
Yay...
Authy just had a massive data leak:You'd rather rely on the retard ratings of an app than the direct advice of this site's administrator?amazing shit with 1.7/5 rating on playmarket
Authy is extremely easy to use, 100% free, and, so far, infallible.
Whatever.
Twilio Confirms Data Breach After Hackers Leak 33M Authy User Phone Numbers
Twilio this week confirmed suffering a data breach after hackers leaked 33 million phone numbers associated with the Authy application.
The notorious ShinyHunters hackers announced on the relaunched BreachForums website in late June that they were leaking 33 million random phone numbers associated with Twilio’s two-factor authentication app Authy.
The leaked information also included account IDs and some other non-personal data associated with Authy users.
In a security alert posted on its website, Twilio confirmed the data breach.
“Twilio has detected that threat actors were able to identify data associated with Authy accounts, including phone numbers, due to an unauthenticated endpoint. We have taken action to secure this endpoint and no longer allow unauthenticated requests,” the company said.
Twilio found no evidence that the hackers gained access to its systems or that they obtained other sensitive data, but as a precaution urged Authy users to install the latest Android and iOS security updates.
“While Authy accounts are not compromised, threat actors may try to use the phone number associated with Authy accounts for phishing and smishing attacks; we encourage all Authy users to stay diligent and have heightened awareness around the texts they are receiving,” Twilio said.
It works across the most platforms compared to the rest, which is an advantage for many users. And the breach wasn't critical, which would obviously get it removed from the list.
Not when passwords are stored using different hashing algorithms, and possibly salt.Taluntain, a honest question: Is there any point to the 2FA other than stopping people who use passwords stolen from some leak? Because, if that is the point, can't you just run once a week a script that matches the (hashed) passwords with those on the list of stolen ones and see of anyone is using a bad one? Then you could remove access to those who do until the create a new one. Would avoid all this trouble and be almost as safe, I think.It works across the most platforms compared to the rest, which is an advantage for many users. And the breach wasn't critical, which would obviously get it removed from the list.
There isn't a single list of stolen logins. There are literally dozens if not hundreds of such lists at this point. Some known and public, some not. Websites and various forums have been getting hacked left and right for years now, so the amount of user databases floating out there is huge and expanding every week, basically. So there's really no way to do what you suggest; some stolen databases are revealed only much later after the breach occurs and others are never posted publicly anywhere. Only checking against what's public would be ineffective, even if we ignore other problems with this idea.Taluntain, a honest question: Is there any point to the 2FA other than stopping people who use passwords stolen from some leak? Because, if that is the point, can't you just run once a week a script that matches the (hashed) passwords with those on the list of stolen ones and see of anyone is using a bad one? Then you could remove access to those who do until the create a new one. Would avoid all this trouble and be almost as safe, I think.
Those lists have the untransformed password (they are, after all, compromised). Just hash and salt using the same algorithm that is used on the codex.Not when passwords are stored using different hashing algorithms, and possibly salt.Taluntain, a honest question: Is there any point to the 2FA other than stopping people who use passwords stolen from some leak? Because, if that is the point, can't you just run once a week a script that matches the (hashed) passwords with those on the list of stolen ones and see of anyone is using a bad one? Then you could remove access to those who do until the create a new one. Would avoid all this trouble and be almost as safe, I think.It works across the most platforms compared to the rest, which is an advantage for many users. And the breach wasn't critical, which would obviously get it removed from the list.
If you used the same one Chrome uses to check your stored passwords, I think it would be good enough for government work. Although I admit I didn't consider the computational cost of checking every password on the list against all the stored passwords on the database. 2FA is still a pain and way overkill for an old discussion board.pictures one huge public list with all stolen passwords in the history of the internet