Linux is known as a very secure operating system. But, it is not going to save us if we voluntarily or unknowingly expose ourselves to unnecessary danger. For instance, a password-authenticated command may allow you to specify the password right on the command-line.

$ mysql -u root -pMyPassword

The command you just executed - with the mysql root password - gets recorded in the shell command history file. For bash, the history file is ~/.bash_history. This is not desirable for security.

$ tail ~/.bash_history
...
mysql -u root -pMyPassword
$ 

The most effective solution is to break the bad habit: don't enter any password on the command line. For the above example, make mysql prompt you for the password:

$ mysql -u root -p 
Enter password: 
mysql> 

Failing that, you can mitigate the security risk by hiding a command from the command line history. Note: the technique below only works for the bash shell. It won't work for zsh, tcsh, etc. (If you do know the trick for these shells, please let us know through comments).

The bash trick is to enter one or more leading spaces before the actual command.

 
$   mysql -u root -pMyPassword

A leading blank. Just like that, and the command you enter won't be written into the command history file.

• http://alien.slackbook.org/ktown/
• rsync URI: rsync://alien.slackbook.org/alien/ktown/
• http://taper.alienbase.nl/mirrors/alien-kde/
• rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/
• http://repo.ukdw.ac.id/alien-kde/
• rsync URI: rsync://repo.ukdw.ac.id/alien-kde/
• http://slackware.org.uk/people/alien-kde/ 
• rsync URI: rsync://slackware.org.uk/people/alien-kde/

• lxc upgraded to 1.0.5
• automake upgraded to 1.14.1
• llvm upgraded to 3.4.2
• calligra upgraded to 2.8.5
• lesstif removed and replaced by motif
• tetex rebuilt against new motif
• ddd rebuilt against new motif
• xpdf upgraded to 3.0.4