121–130 of 194 posts
Earlier quoted context omitted.
Just pop a space at the beginning and it won't go into shell history.
That's a bash-ism that's controlled by the $HISTCONTROL environment variable, not universally-applicable advice. $HISTCONTROL set to "ignorespace" or "ignoreboth" may or may not be the default, depending on your distribution.
www.wasmylinkedinpasswordleaked.com
Earlier quoted context omitted.
http://www.inutile.ens.fr/estatis/password-security-checker/ (BTW, be sure to type some gibberish into the provided box and hit submit, so you can see why I think this is a very relevant link.)
The Terms and Conditions are hilarious: c. You agree to pay $ 100,000 for your use of the Estatis Free Password Security Checker if we ever ask for it.
oh dear.
I quickly wrote a script to do this locally, not the most efficient, but I'm at work ;) https://github.com/hungtruong/LinkedIn-Password-Checker
$ cat combo_not.txt | grep `printf linkedintrouble | sha1sum`
3ac85868a20c977661a12f770f0d116f87c74831
$ cat combo_not.txt | grep `printf nathanlinkedin | sha1sum`
a4d28368130ad555c77ec6a4dd18b8977ac0f589
$ cat combo_not.txt | grep `printf mypassword | sha1sum`
$ cat combo_not.txt | grep `printf yourpassword | sha1sum`
$Mine was not in the list. I had a non-dictionary password with letters and numbers, 8 characters, and it was at least several months old. (If we can collect enough data points of whose passwords are on it or not, how old they are, and how complex the password was, we should be able to narrow down a potential date range for the list and the odds that the compromised list is full or partial.)
You're confusing "not on the list" with "not in the hacker's possession".