- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
The Naz.API dataset is a massive collection of 1 billion credentials compiled using credential stuffing lists and data stolen by information-stealing malware.
Credential stuffing lists are collections of login name and password pairs stolen from previous data breaches that are used to breach accounts on other sites.
Information-stealing malware attempts to steal a wide variety of data from an infected computer, including credentials saved in browsers, VPN clients, and FTP clients. This type of malware also attempts to steal SSH keys, credit cards, cookies, browsing history, and cryptocurrency wallets.
A stern reminder that we should all use a password management tool and use unique, unrelated passwords with every service.
And unique email-aliases for bonus points
Remind me how to do this, please. I always forget this part…
SimpleLogin and Addy.io are a good start
You can integrate this with Bitwarden to auto generate email aliases too
For Gmail users, you can add a plus sign to the end of your email username, and then any set of characters you’d like.
So if your address was [email protected], and wanted an easy-to-remember login for Hot Dog Hut, you could append it in the following way:
[email protected]
That used to be my go-to method but I found it works less and less. Places know the gmail tricks and auto-strip them out of the address.
Started using Proton’s Hide-my-email and never going back. It’s time to move away from google anyways.
Many privacy centric mail companies now offer email aliases and temporary mail ids in built.
I used to use that approach, but found in the last several years more than half the web sites I use reject email addresses with “+” characters.
I even use several sites that used to take those addresses just fine now reject them. That made me wonder if some common JS package for parsing email addresses got changed.
Duck.com is what I use, I generate a unique email for every website. I even started changing my old logins recently for old accounts
I agree with doing this, but the main drawback is that you can’t easily check all of your unique aliases in HaveIBeenPwned without scripting something and paying for API access.
I have hundreds of unique aliases for my accounts, but no simple way to see when/if the services that use them are breached.
The free version of Proton Pass is a decent option.
[email protected]
[email protected]
That is not a standard mail feature, it won’t work with all mail servers and not all that do have it use + as the separator.
While it’s not formalised in the email specs, support for it is pretty consistent, and only needs to work for whichever provider you use
I always get funny looks when in person and I give my email address as [email protected]
I used to explain the how’s and the why’s but now I just say I’m a geek and move along. But if I start getting spam or bullshit to that address best believe I know who fucked up.