If you're on Windows, you can calculate it in PowerShell like this:

$password = "foobar"

([Security.Cryptography.SHA1CryptoServiceProvider]::Create().ComputeHash([Text.Encoding]::ASCII.GetBytes($password)) | %{'{0:x2}' -f $_}) -join ""

And people say that PowerShell isn't readable or intuitive.

You can also do it like this:

  "foobar" | Out-File password.txt -Encoding ASCII -NoNewline

  Get-FileHash password.txt -Algorithm SHA1

  del password.txt

That's readable and intuitive, but the downside is it puts your password in a file.

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/5df7885fb0d5caeabb39fcd0e2b...

You need to use `echo -n` in order to not have `echo` generate a newline.

Ah, thanks.

You 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*".

Thanks, I knew there had to be an easier way, but couldn't find it.

Make sure you clean your .history if you're using echo to pipe the password...

Thanks. I had done so.