Live data from Hacker News

Two billion email addresses were exposed

troyhunt.com

271–280 of 470 posts

Re: Two billion email addresses were exposed

#271

Earlier quoted context omitted.

Yes! Me too. Not adding anything here except a confirmation on the above approach. You kind of need your email password as a "break glass" scenario. But mostly, you just need your password manager.

and root disk encryption, unless you have some alternative method set up.

That's the default in this day and age, no?

Re: Two billion email addresses were exposed

#272

Earlier quoted context omitted.

I used per-account email with alias services and password managers. Also started migrating old accounts in free time. Now its pretty easy to tell the source of leak by email addresses as well as sources of spam. --- Per-account alias might sound much, but using sieve filtering [1] is amazing, and you can get a comprehensive filtering solution going with 'envelope to' (the actual address receiving the email) + 'header…

I just use + @gmail.com At the end of day day it’s all delivered to myname@gmail.com mailbox, but I can use filters based on part after “+”.

Anyone who’s looked at breach data knows to try yourname+service for any service.

This does help in filtering spam though

Re: Two billion email addresses were exposed

#273

Earlier quoted context omitted.

No, it doesn't mean that, that's ridiculous. How would that work? Magic?

Download all the hashes first - not practical.

It's more practical than you may think. Just needs about 40 GBs right now. I did it a couple years back in a fit of peculiar paranoia, downloaded the full hash list and checked all my KeePass-stored passwords at that time against it.

https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader

Re: Two billion email addresses were exposed

#274
post #124
post #56

On the plus side, Troy can save a lot of DB space now. Instead of storing which emails have been compromised at this point he can replace that with just def email_compromised(email): return True

Not necessarily. Both my main addresses still come back clean after years in use. The one I use for random crap has 9 hits though.

In that case he could just store the emails that haven’t been compromised yet.

Re: Two billion email addresses were exposed

#275

Earlier quoted context omitted.

I used per-account email with alias services and password managers. Also started migrating old accounts in free time. Now its pretty easy to tell the source of leak by email addresses as well as sources of spam. --- Per-account alias might sound much, but using sieve filtering [1] is amazing, and you can get a comprehensive filtering solution going with 'envelope to' (the actual address receiving the email) + 'header…

I just use + @gmail.com At the end of day day it’s all delivered to myname@gmail.com mailbox, but I can use filters based on part after “+”.

I do this as well, but there are a number of service providers that just do not handle subaddressing at all. Like creating an account will result in never receiving a confirmation or verification code because the system failed to parse the address.

I've started using grouped aliases instead for a bunch of things.

Re: Two billion email addresses were exposed

#276

Earlier quoted context omitted.

+1 for Bitwarden. It is literally the best solution out there. Been getting to increase uptake in personal circles with (very) limited success. The wife keeps trying to convince me that the ship has sailed in trying to protect info online. She's probably right.

Can anyone with experience with 1Password and Bitwarden share their opinions on each. I've been on 1Password for years and am wondering if I'm missing anything.

1P is closed source and have had a number of breaches in the past. Bitwarden have had none that I'm aware of, and they're FOSS. I however have been preferring ProtonPass lately (also FOSS) and really like the layout over BW.

Re: Two billion email addresses were exposed

#277
This is a massive PITA for any users who exclusively use unique passwords and various unique addresses, as it sounds like the source of the breach(es) is unknown (so hard to judge which accounts would be affected without using Troy's sites to test everything or find some searchable dump online somewhere dubious).

Re: Two billion email addresses were exposed

#278
post #113

Interestingly, the HIBP data seems to have an expiration date. My email address from the Dropbox data breach [0] is now shown as having no recorded breaches, although it did back in 2016 after HIBP acquired that dataset. [0] https://haveibeenpwned.com/breach/Dropbox

Are you sure you typed the right email address?

My 2012 Dropbox leak still shows up for my account.

Re: Two billion email addresses were exposed

#279
I’m unclear how the new data helps anyone? If you identify you’ve been in a data breach with Adobe for instance, you change your Adobe password. But if you’re in this new dataset there’s no service being pointed at - just “you’ve been breached” which doesn’t really help anyone apart from those who have the same pwd for everything. Maybe they’re the audience, I’m unclear.

Re: Two billion email addresses were exposed

#280
post #229

Earlier quoted context omitted.

Now that I'm not only using a Macbook and iPhone, I've been looking for cross-platform solutions. For a week I've been using KeePassXC + Syncthing between four devices. Syncthing is also syncing my Obsidian vaults which has replaced Apple-only Notes.app. Bitwarden is definitely more polished, and Syncthing is definitely (much) more fiddly than using Bitwarden's and Obsidian's ($5/mo) native syncing tools. But I like…

strongbox is a reasonable app for iOS and you can set it up for sftp to your main self hosted server.

Unfortunately strongbox was sold a few months ago to a somewhat notorious app firm that has the nasty habit of buying popular apps and adding a whole bunch of telemetry. Not something I'd want in a password app.

I've switched to KeePassium. Not quite as polished UX, but works for me

Post reply on HN