News for hackers. Stuff that matters.
Re:Phishing attack against Lastpass by DyslexicAtheist on Saturday January 16, 2016 @07:15PM (#10917535)
have been tinkering with this idea also something like

   *echo -n 'my unique passphrase' |sha512sum*
only issue is this shows up in your memory and on disk (e.g. .bash_history)
Re:Phishing attack against Lastpass by veddan on Saturday January 16, 2016 @07:33PM (#10917604)
Prefix the command with a space and bash won't save it in its history.
Re:Phishing attack against Lastpass by Sophira on Sunday January 17, 2016 @01:53AM (#10918609)
This doesn't seem to be true in 4.3.42, at least not by default. " echo test" shows up in both the output of the 'history' builtin and in ~/.bash_history.

Is it an option that needs to be set?

Re:Phishing attack against Lastpass by reader_1000 on Sunday January 17, 2016 @05:17AM (#10919028)
Yes, you need to have HISTCONTROL=ignorespace option in your .bashrc
Re:Phishing attack against Lastpass by DyslexicAtheist on Sunday January 17, 2016 @06:59AM (#10919213)
great thanks didn't know this one. Just checked and there is also

# don't put duplicate lines or lines starting with space in the history.

# See bash(1) for more options

HISTCONTROL=ignoreboth