5 ms·

Or call shasum or sha1sum and input your password on stdin so your shell history doesn't contain your password in plain text.

• corin_ 14y ago
  Just pop a space at the beginning and it won't go into shell history.
  • eridius 14y ago
    It does for me > echo test test > history ... 6730 echo test 6731 history
    • corin_ 14y ago
      Set this in your .bashrc HISTCONTROL=ignorespace Or even better, though unrelated to this topic... Also get it to ignore duplicates that come next to each other. HISTCONTROL=ignoredups:ignorespace
  • tomku 14y ago
    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.
    • corin_ 14y ago
      Yeah already replied below specifying that - I was under the impression that it's default to on in most distros, but don't actually have a clue which do/don't.
  • ibotty 14y ago
    it will still be in ps output for a short while...
    • sjs 14y ago
      Ultra paranoid. I like the way you think.
    • mhluongo 14y ago
      python -c 'import hashlib; from getpass import getpass; s = hashlib.sha1(); s.update(getpass()); print s.hexdigest()'
• ibotty 14y ago
  how do you get rid of the carriage return as last char that way?
  • sjs 14y ago
    Use Ctrl-d to end input without hitting return and you shouldn't get a newline.
    • Peaker 14y ago
      bash, at least, only handles Ctrl-d on its own line.
      • 1zq 14y ago
        If you're not on a new line, you can type Ctrl-d twice.