4 ms·
You may also want to consider running `unset HISTFILE` before that to ensure that the line containing your password doesn't end up sitting around in your bash h
by mnutt 9y ago
You may also want to consider running `unset HISTFILE` before that to ensure that the line containing your password doesn't end up sitting around in your bash history.
- r1ch 9y agoAnother way is to prefix the command with whitespace.
- baliex 9y agoOnly if.. export HISTCONTROL=ignorespace ..is set (either by default or explicitly)
- deathanatos 9y agopython3 -c 'import getpass, hashlib; print(hashlib.sha1(getpass.getpass().encode("utf-8")).hexdigest())' Avoids history, doesn't echo to the terminal. In fact, you should be able to just make a rudimentary CLI into Troy's API simply with: #!/bin/bash HASH="$(python3 -c 'import getpass, hashlib; print(hashlib.sha1(getpass.getpass().encode("utf-8")).hexdigest().upper())')" curl -sS "https://api.pwnedpasswords.com/range/${HASH:0:5}" | grep "${HASH:5}" (It'll emit the line from the API response matching your pass; if it does, then that password was compromised. Bash isn't real good at error handling though, so my biggest concern would be what this might do if an HTTP/TCP error happened. I've attempted to throw -S there to catch that, but use with your head screwed on.)