Re:Yahoo Triples Estimate of Breached Accounts to 3B
by skytreader on Tuesday October 03, 2017 @07:22PM
(#15397069)
+1. I did the same. At the time I had to do this (around 2015), Yahoo was the least concerned about identifying duplicate accounts. I was testing for an actual paying job, not some side interest investigation, mind you. Some of the services I had to test were clever enough to reject fakeinbox accounts so I used Yahoo.
[ Parent
| on HN ]
Re:Yahoo Triples Estimate of Breached Accounts to 3B
by jstanley on Wednesday October 04, 2017 @04:02AM
(#15398944)
> I was testing for an actual paying job, not some side interest investigation
What difference would it make?
Do you mean to imply that creating test accounts is a little bit "wrong", and would be wrong for an individual to do at home, but it's OK to do it if someone else is paying you for it?
If so, I disagree on both counts: it's not wrong to create test accounts, but if it was, it would still be wrong even if someone is paying you to do it.
Re:Yahoo Triples Estimate of Breached Accounts to 3B
by skytreader on Friday October 06, 2017 @12:27AM
(#15414424)
Hmm just a detail I thought to add, not trying to imply anything about the morality of it.
Re:Yahoo Triples Estimate of Breached Accounts to 3B
by rollcat on Wednesday October 04, 2017 @04:18AM
(#15399004)
We've created a catch-all *@test.company.com with AWS SES & Lambda, all forwarded to a single [email protected] (a GApps group where the QA staff had access). Took a few tries to get right, but worked flawlessly from then on, saving testers' time every single day.