News for hackers. Stuff that matters.
Re:GitHub sued for aiding hacking in Capital One breach by cgb223 on Sunday August 04, 2019 @11:57AM (#20607266)
Wait...

Given enough SSNs as training data, could someone make an ML model that churns our mostly valid SSNs?

Because that could be really really bad

Re:GitHub sued for aiding hacking in Capital One breach by JumpCrisscross on Sunday August 04, 2019 @12:02PM (#20607298)
> Given enough SSNs as training data, could someone make an ML model that churns our mostly valid SSNs?

Most SSNs are deterministically derived. Given a single valid SSN, you can often generate millions of valid preceding values.

Re:GitHub sued for aiding hacking in Capital One breach by ageitgey on Sunday August 04, 2019 @12:05PM (#20607320)
That changed in 2011. Now they are random. But it is still true for older numbers.

https://www.ssa.gov/employer/randomization.html

Re:GitHub sued for aiding hacking in Capital One breach by pliny on Sunday August 04, 2019 @12:02PM (#20607303)
Don't you need at least one other piece of identifying info to make that useful? Like, I could churn out mostly valid gmail passwords all day, but I have no idea which users have those passwords.
Re:GitHub sued for aiding hacking in Capital One breach by jakelazaroff on Sunday August 04, 2019 @12:29PM (#20607479)
No need to get that involved:

for (let i = 0; i < 1000000000; i++) console.log(i);

Every single valid social security number, and several (e.g. 000-00-0000) that probably aren't. You can store the whole thing in about a gig.

Re:GitHub sued for aiding hacking in Capital One breach by throwawaywego on Sunday August 04, 2019 @03:15PM (#20608646)
Worse. You can make the ML model spit out the SSNs it was trained on. That's a problem when you can't manually curate billions of documents. If you didn't look, you wouldn't even know they were there.