Snapchat Phone Number Database Leaked • Hacker News Board

Re: Snapchat Phone Number Database Leaked

#231

Post by igorgue » Thu, Jan 02, 2014, 4:38 PM UTC

thezilch wrote: post #195

seldo wrote: post #193

Earlier quoted context omitted.

And while we're here, "cock sucker" is not an insult, and my fellow gay hackers and I would prefer if you didn't use it as one.

And we wonder why no women are in tech...

Do you know any women? Seriously, most of them are OK when calling assholes (like many of HN users) "cock suckers".

You guys need to go out more, since women are more than OK when people swear, you're not talking to toddlers here.

Now, this is a comment, not a fucking essay or interview (haha PG fucked up really bad huh? So bad he's gonna have a women only conference).

Now I sound like a troll, so I'll shut up, but seriously, women are OK with swearing (that includes all George Carlin's 7 words).

Re: Snapchat Phone Number Database Leaked

#232

Post by aneisf » Thu, Jan 02, 2014, 5:07 PM UTC

21echoes wrote: post #218

eli wrote: post #200

Earlier quoted context omitted.

I strongly disagree that your street address being linked to your name is the same as your pseudonymous snapchat username being linked to your cell phone number.

I hope you're agreeing that the street address is way more private than a snapchat user name...

I think the point is that we expect our phone numbers to identify us in the real world but don't expect them to point to our handles online. If I use the same username on Snapchat that I do for something embarrassing like, say, my tumblr, someone who knows me IRL can look me up and find my more private online presence. This is just as real an issue as the reverse scenario in which Internet stalkers find out my phone number or something.

Now generally it's advisable to use a unique handle (or your real name) for a service so closely tied to a piece of real life identification like your phone number, but I don't think a lot of people do it.

Re: Snapchat Phone Number Database Leaked

#233

Post by nitrogen » Thu, Jan 02, 2014, 6:17 PM UTC

fat0wl wrote: post #230

fat0wl wrote: post #225

Earlier quoted context omitted.

obvious logic, link to wiki for explanation of common term -- u my friend are due for about 5 upvotes in the HN chain of circular validation. i understand it as a way for SNR sure, but mostly its just a way to fade the text of people you disagree with. it doesn't solve much for people who can skim, & it usually just makes me more curious about what got downvoted (some of the comments are very insightful but just piss…

also i wasn't gonna say anything but can't help from chuckling about it -- i am an audio DSP engineer so by nature I've probably done more work/research concerning SNR than 99% of people on the planet ever will lol. i didnt want to come of as indignant tho, its just a funny coincidence. you never quite know who you are condescending to on here

I've worked with audio DSP, too. I think the comparison to audio SNR is appropriate. The wiki link was as much for other readers as for you or me.

Re: Snapchat Phone Number Database Leaked

#234

Post by cheshire137 » Thu, Jan 02, 2014, 8:38 PM UTC

21echoes wrote: post #217

mgulaid wrote: post #118

Earlier quoted context omitted.

Here is a video of guy hacking SnapChat and finding out Mark Zuckberg's logging info like phone#, email. The video was posted on Dec 26th. How come they did not fix this.. https://www.youtube.com/watch?v=JEWugKX98P0

> How come they did not fix this.. How would you fix it? The app needs to know if your phone contacts are on snapchat, and if they are, what their usernames are. In other words, the API needs to exist.

Don't allow bulk matching for one. Or require the same secret key with the phone number match that is required for other API actions.

Re: Snapchat Phone Number Database Leaked

#235

Post by admbrinkka » Fri, Jan 03, 2014, 3:40 AM UTC

mgulaid wrote: post #118

antimatter15 wrote: post #74

The top comment on Reddit r/netsec's corresponding coverage has mirrors on Mega.co.nz for the files [1] I couldn't find my own data in the set, and actually it seems like lots of entire area codes are missing. Assuming `cat schat.csv | uniq | cut -c1-4 | wc -l` is the proper command, there are only 76 of 322 [2] US area codes represented. It appears there are two Canadian area codes represented in the database: 867 a…

Here is a video of guy hacking SnapChat and finding out Mark Zuckberg's logging info like phone#, email. The video was posted on Dec 26th. How come they did not fix this.. https://www.youtube.com/watch?v=JEWugKX98P0

thanks for share a video.. It was help my trouble

By: http://malemarkets.com

Re: Snapchat Phone Number Database Leaked

#236

Post by telnet44 » Fri, Jan 03, 2014, 5:39 AM UTC

scaramanga wrote: post #105

CSV: magnet:?xt=urn:btih:bab9548c3770188c70d27ded9b22348f5b979713&dn=Snapch at+database+CSV&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80 &tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftrack er.istole.it%3A6969&tr=udp%3A%2F%2Ftracker.ccc.de%3A80&tr=udp% 3A%2F%2Fopen.demonii.com%3A1337 SQL: magnet:? xt=urn:btih:f7b1cec6280edb8169d63550ba2dfb224df7810d&dn=Snapch at+database+SQL&tr=udp%3A%2F%2Ftracker.openbit…

actually these links are bullshit. only PARTIAL NUMBERS. I have over 80 million US nembers myself and 20 million cellphones. I sell numbers cheap. Hit me up through LeadPro.net cheers!

Re: Snapchat Phone Number Database Leaked

#237

Post by stouset » Fri, Jan 03, 2014, 7:06 PM UTC

ja27 wrote: post #176

untog wrote: post #21

Not at all surprised. Anyone that used the app would be suspicious of the backend behind it. Should have taken that $3bn while you had the chance.

Unless it's changed recently, the phone number is user-supplied and I'm not sure if it's verified at all. They do claim that the phone number "will be stored as unique mathematical representations (or 'hashes')..." rather than plaintext, but I imagine if you know it's a non-salted phone number that's been hashed, it's pretty easy to brute force. But were they lying about hashing the phone numbers? I guess it doesn't…

Salts, in a cryptographic context, are considered to be public. Salting does not mitigate a brute force attack against a limited search space.