Earlier quoted context omitted.
and receive no meaningful legal consequences. These people should be on the hook for all damage done with this dump, but they won't be, so it doesn't really matter. It's not ironic, it's just business as usual. Collecting data on users should be extremely risky, even if they consent to it's collection.
I think it's time for an external, trustworthy entity to spawn that would vet and endorse companies that respect their users. Something like the "USDA Organic" label but for user privacies. Maybe it'd be an EFF-like entity that audits companies in exchange for a fee and endorse that "Company X, and the product/services it uses, are respecting user privacy". We could then derive a chain of trust between companies, may…
The 773M Record “Collection #1” Data Breach
31–40 of 128 posts
Re: The 773M Record “Collection #1” Data Breach
#32Earlier quoted context omitted.
The slightly annoying thing here is that I already use a password manager, so while the impact to me is minimal, I wish I knew which password specifically I have to rotate, instead of assuming that I need to rotate, like, all of them...
Why not use Pwned Passwords to check your passwords to see if any of them need to be rotated due to this breach or any other?
They do have an API that allows you to search for your password based on a truncated checksum, so you can find out if your password was leaked, without revealing the password.
Re: The 773M Record “Collection #1” Data Breach
#33Troy won’t store the passwords associated with the username, which is a choice I can absolutely respect. But as he discusses in the post, that leaves users knowing that their email address was in the data dump, but with no way of knowing which site it came from, or what password was breached. So while this increases the number of records in HIBP, and perhaps makes the password popularity tracker a bit more comprehens…
He has a service that lets you enter a password to check if it’s been pwned though. I guess these are disassociated from user emails?
Re: The 773M Record “Collection #1” Data Breach
#34Earlier quoted context omitted.
Why not use Pwned Passwords to check your passwords to see if any of them need to be rotated due to this breach or any other?
Seems really weird to advocate people reveal their passwords to a random untrusted 3rd party. They do have an API that allows you to search for your password based on a truncated checksum, so you can find out if your password was leaked, without revealing the password.
Re: The 773M Record “Collection #1” Data Breach
#35Earlier quoted context omitted.
Why not use Pwned Passwords to check your passwords to see if any of them need to be rotated due to this breach or any other?
Seems really weird to advocate people reveal their passwords to a random untrusted 3rd party. They do have an API that allows you to search for your password based on a truncated checksum, so you can find out if your password was leaked, without revealing the password.
https://www.troyhunt.com/ive-just-launched-pwned-passwords-v...
Re: The 773M Record “Collection #1” Data Breach
#36All my passwords are randomly generated so they are different for all websites.
Re: The 773M Record “Collection #1” Data Breach
#37Earlier quoted context omitted.
Seems really weird to advocate people reveal their passwords to a random untrusted 3rd party. They do have an API that allows you to search for your password based on a truncated checksum, so you can find out if your password was leaked, without revealing the password.
The password itself is not sent. You can read about it here: https://www.troyhunt.com/ive-just-launched-pwned-passwords-v...
Which does upload your password, which I think is an unacceptable risk.
Re: The 773M Record “Collection #1” Data Breach
#38What's the latest consensus on the best password manager these days. I see he is recommending 1Password, but I recently found Bitwarden which looks quite good.
Re: The 773M Record “Collection #1” Data Breach
#39Troy won’t store the passwords associated with the username, which is a choice I can absolutely respect. But as he discusses in the post, that leaves users knowing that their email address was in the data dump, but with no way of knowing which site it came from, or what password was breached. So while this increases the number of records in HIBP, and perhaps makes the password popularity tracker a bit more comprehens…
The slightly annoying thing here is that I already use a password manager, so while the impact to me is minimal, I wish I knew which password specifically I have to rotate, instead of assuming that I need to rotate, like, all of them...
Re: The 773M Record “Collection #1” Data Breach
#40Troy won’t store the passwords associated with the username, which is a choice I can absolutely respect. But as he discusses in the post, that leaves users knowing that their email address was in the data dump, but with no way of knowing which site it came from, or what password was breached. So while this increases the number of records in HIBP, and perhaps makes the password popularity tracker a bit more comprehens…
Even if it's not in the HIBP base, you should always assume that. That's why you should always enable MFA everywhere it's possible and consider all services where it's not already compromised.