News for hackers. Stuff that matters.
Re:Coinbase user emails and full names leaked by josephwegner on Tuesday April 01, 2014 @11:42AM (#7509093)
If you use gmail, you can use [email protected], and it will all get forwarded to [email protected]. This is incredibly handy for noticing who is sending you spam.

I'll also use it for sites that I know are going to send me spam, and then immediately create a filter than deletes emails sent to [email protected] (note: that's not my real email)

Re:Coinbase user emails and full names leaked by thetrb on Tuesday April 01, 2014 @01:54PM (#7510265)
In general spammers deal with those things pretty quickly. They can just quickly add a regex to remove everything starting with the "+" and then you don't have any unique identifier any more.
Re:Coinbase user emails and full names leaked by kisielk on Tuesday April 01, 2014 @11:48AM (#7509146)
That does nothing to increase the security of your accounts, since effectively the email address is the same.
Re:Coinbase user emails and full names leaked by oijaf888 on Tuesday April 01, 2014 @12:16PM (#7509398)
It keeps phishing attacks from being able to cross services (since if you get a citibank email to your coinbase email that would be a big flag) and it reduces the attack surface on other sites.

I use [email protected] for this purpose and it makes it handy to see who has somehow lost/disclosed my email to third parties and not informed me (FreshDirect for example)

Re:Coinbase user emails and full names leaked by claudius on Tuesday April 01, 2014 @12:46PM (#7509637)
> It keeps phishing attacks from being able to cross services (since if you get a citibank email to your coinbase email that would be a big flag) and it reduces the attack surface on other sites.

Or, more importantly, it lets you authenticate the sender in some way. Citibank has to send you email to [email protected] and it is unlikely for a spammer to guess that exact wording (without also trying hundreds of others, which would give it away by filling your inbox).

Re:Coinbase user emails and full names leaked by kisielk on Tuesday April 01, 2014 @12:39PM (#7509566)
[email protected] is at least a distinct email address, unlike using +. Especially if you use different passwords for each account, it means if one of the emails is compromised then the attacker can't use it to recover passwords of your other sites.
Re:Coinbase user emails and full names leaked by oijaf888 on Tuesday April 01, 2014 @12:43PM (#7509603)
+ can be a distinct email address, just as . can be an alias. It really depends on how your email server is configured. Postfix makes it really easy to adjust what character you use.
Re:Coinbase user emails and full names leaked by Uehreka on Tuesday April 01, 2014 @12:04PM (#7509296)
I'm kind of surprised that this still works. I would guess that diligent spammers will soon catch on and start stripping anything that comes after the + sign.
Re:Coinbase user emails and full names leaked by jonknee on Tuesday April 01, 2014 @11:58AM (#7509252)
That won't help here, your real Gmail address is exposed which lets everyone know that you have BTC on web wallets.
Re:Coinbase user emails and full names leaked by eli on Tuesday April 01, 2014 @01:32PM (#7510059)
Actually it would help you here. In this case your real address isn't exposed unless someone guessed the exact version you used to sign up.
Re:Coinbase user emails and full names leaked by jonknee on Tuesday April 01, 2014 @02:14PM (#7510451)
What do you mean? If [email protected] is in the leaked list you know that that [email protected] is the "real" user and also is someone who has BTC.
Re:Coinbase user emails and full names leaked by eli on Tuesday April 01, 2014 @02:23PM (#7510518)
There was no leak. The API allowed you to see whether a given email had an account associated, so someone churned through a big list of known email addresses to find accounts.
Re:Coinbase user emails and full names leaked by ttty on Tuesday April 01, 2014 @01:59PM (#7510304)
If you do a filter like this: All mail that arrives to [email protected] is important. Everything else is spam. Of course you might not get emails from people who sends emails to [email protected] nor [email protected] because the emails go to spam.
Re:Coinbase user emails and full names leaked by crazcarl on Tuesday April 01, 2014 @11:56AM (#7509219)
Does this actually prevent true spammers, or only emails you consider spam, but the sender thinks is worthwhile?

Otherwise, as a 'true' spammer, why wouldn't you just always strip off everything after the plus when adding the email to your distribution list?

Re:Coinbase user emails and full names leaked by wpietri on Tuesday April 01, 2014 @02:03PM (#7510347)
Depends on how smart the spammer is, and how much they care. Most spammers a) are not very bright, and b) are in a volume business. Even the ones smart enough to do this may not think it worth the time to possibly improve a tiny percentage of harvested addresses. Especially since those of us who are dedicated enough to maintain tagged addresses are unlikely to respond positively to spam no matter what address we receive it on.
Re:Coinbase user emails and full names leaked by claudius on Tuesday April 01, 2014 @12:41PM (#7509590)
I use _, not "+" and anybody else might use "." or "-" depending on the configuration of their mail server. Sure, you can always add the full email and every possible stripped email to your lists, but in practice, few people seem to do that (judging by the amount of spam I get to [email protected] as compared to [email protected]).
Re:Coinbase user emails and full names leaked by SomeCallMeTim on Tuesday April 01, 2014 @12:56PM (#7509725)
I use "-" with an alias to "_". It turns out that when you give an email address to random people, they sometimes don't know the difference between "dash" or "hyphen" and an underscore.
Re:Coinbase user emails and full names leaked by flanbiscuit on Tuesday April 08, 2014 @08:06PM (#7556869)
I've found that when signing up for things, a lot sites don't allow the "+" in the email. They'll throw a email validation error. But at one point this was a good technique, I just think many sites have either don't allow it or can easily get around it