266 emails whose domain end with .gov Very interesting.
.gov is not just Obama and super-secret crytpo scientists. It's also the person who makes sure that every form they send out has an OMB Control Number.
11–20 of 49 posts
266 emails whose domain end with .gov Very interesting.
.gov is not just Obama and super-secret crytpo scientists. It's also the person who makes sure that every form they send out has an OMB Control Number.
Thats great, thanks. I was relieved to not find my email in the list, although I could swear I've commented on gawker sites.
This, btw, is a great example of when using a trusted 3rd party login is a big win.
Fuck. What the fuck did I even need a Gawker account for? (Thanks for making this. I was going to download the torrent, but assumed that I did not ever visit their site, much less make an account. Wrong!)
Thats great, thanks. I was relieved to not find my email in the list, although I could swear I've commented on gawker sites.
You probably used Facebook Connect. This, btw, is a great example of when using a trusted 3rd party login is a big win.
sadly, I'm on the list, and it was an account i was banned from posting with about 2 years ago. I wish I could have deleted it.
For some reason every md5 from this spreadsheet I try to decrypt, I get nothing. I'm using online tools like md5decrypter.com to do this. Am I missing something?
md5decrypter would just be a big database of tested strings and their MD5 hash,
For some reason every md5 from this spreadsheet I try to decrypt, I get nothing. I'm using online tools like md5decrypter.com to do this. Am I missing something?
1) they are hiding. You (theoretically) can't reverse the function by any method other than brute-force.
2) they are *binding. You (theoretically) can't find any other input that hashes to the same output by any method other than brute-force.
Any tool that "decrypts" md5 hashes most likely does so by generating what is called a rainbow table -- a giant list of many possible inputs, and the hashes they generate. If you look at the spreadsheet and find a hash from your rainbow table, voila, you know what it came from. To make it harder to use rainbow tables, any security-conscious site will "salt" the passwords before hashing them, by adding a random string prefix. The point is for the random "salt" to be different for each password you are hashing, so a standard (unsalted) rainbow table won't work, and further, the same rainbow table won't work for every password.
(md5 itself has been shown to be vulnerable to collision attacks, which is why I said "theoretically")