3 ms·

Mistake happen. Yesterday I was tired and working on a friend serveur. The ssh prompt was different and I entered the password from a account while the remote

Mistake happen. Yesterday I was tired and working on a friend serveur. The ssh prompt was different and I entered the password from a account while the remote port has hang up on me. So effectively typing “password” straight on my shell. His password is in my history now. I removed it but that type of thing happen all the time. ( Not that much in a professional settings, password tends to fade away )

capableweb 4y ago
Pro-tip: if you wanna hide stuff from your shell history, enter a space/blank before the actual command. Not that it probably would have helped in this situation, but maybe useful for others. Usually if I have to enter secrets in my shell, I do something like this in order to save the useful stuff to history but hiding the secrets: - ` export PASSWORD=hunter2` (notice the space before "export") - `service-cli login username $PASSWORD` (no space before, gets saved to shell history)
- ddworken 4y ago
  +1 to prefixing with a space. hiSHtory supports this out of the box so that anything prefixed with a space isn't recorded (even if your shell doesn't do that by default!). And if you do ever mess up, `hishtory redact` can be used to delete history entries.
- remram 4y ago
  Other options: - read -s PASSWORD - service-cli login username $(cat) At least you probably don't want to use `export` when setting the variable.
- Cockbrand 4y ago
  While ignoring commands preceded by a space character is absolutely one of my very favorite shell features, it usually isn't enabled by default (YMMV). HISTCONTROL=ignorespace # bash setopt hist_ignore_space # zsh These go into ~/.bashrc or ~/.zshrc, respectively. zsh is really smart about this and always enables you to retrieve the immediate previous line with arrow-up, no matter whether it's got preceding whitespace or not.
- 400thecat 4y ago
  why use `export` ? That is a terrible idea.

capableweb 4y ago

Pro-tip: if you wanna hide stuff from your shell history, enter a space/blank before the actual command. Not that it probably would have helped in this situation, but maybe useful for others. Usually if I have to enter secrets in my shell, I do something like this in order to save the useful stuff to history but hiding the secrets: - ` export PASSWORD=hunter2` (notice the space before "export") - `service-cli login username $PASSWORD` (no space before, gets saved to shell history)

ddworken 4y ago
+1 to prefixing with a space. hiSHtory supports this out of the box so that anything prefixed with a space isn't recorded (even if your shell doesn't do that by default!). And if you do ever mess up, `hishtory redact` can be used to delete history entries.
remram 4y ago
Other options: - read -s PASSWORD - service-cli login username $(cat) At least you probably don't want to use `export` when setting the variable.
Cockbrand 4y ago
While ignoring commands preceded by a space character is absolutely one of my very favorite shell features, it usually isn't enabled by default (YMMV). HISTCONTROL=ignorespace # bash setopt hist_ignore_space # zsh These go into ~/.bashrc or ~/.zshrc, respectively. zsh is really smart about this and always enables you to retrieve the immediate previous line with arrow-up, no matter whether it's got preceding whitespace or not.
400thecat 4y ago
why use `export` ? That is a terrible idea.