3 ms·
sha1sum is giving different results. /tmp$ echo "p@55w0rd" | sha1sum 8633c4a8b38a8826132414d8861af7b6a8371976 - This is a different value from the o
by AlexCoventry 9y ago
sha1sum is giving different results.
/tmp$ echo "p@55w0rd" | sha1sum
8633c4a8b38a8826132414d8861af7b6a8371976 -
This is a different value from the one given in the blog post: "ce0b2b771f7d468c0141918daea704e0e5ad45db".
The python sha-1 hexdigest comes out right, though:
In [13]: import sha
In [14]: sha.new('p@55w0rd').hexdigest()
Out[14]: 'ce0b2b771f7d468c0141918daea704e0e5ad45db'
In case anyone else has passwords they want to check, this will binary-search them: https://gist.github.com/coventry/5df7885fb0d5caeabb39fcd0e2bf4864 https://gist.github.com/coventry/5df7885fb0d5caeabb39fcd0e2b...
- nsillik 9y agoYou need to use `echo -n` in order to not have `echo` generate a newline.
- AlexCoventry 9y agoAh, thanks.
- mrob 9y agoYou can also binary search with "look -b". The version included with Debian Unstable doesn't support large files, but it will search multiple files at once, so you can split without breaking lines, eg. with "split -C 1999m", and search with "look -b SHASUM splitfile*".
- AlexCoventry 9y agoThanks, I knew there had to be an easier way, but couldn't find it.
- rrauenza 9y agoMake sure you clean your .history if you're using echo to pipe the password...
- AlexCoventry 9y agoThanks. I had done so.