Hacker News Reader

Comment by kitotik | Hacker News Reader

An envvar with a fallback of read -s might be the best compromise?

These can be recorded also, the best way is likely a password/key file.

Tip: if you prefix your command by a space in bash (and maybe other shells) that command doesn't get recorded in history.

Don’t go doing this and expecting it’s the default behavior. It’s not. Your bash session must have set, at minimum:

   HISTCONTROL=“ignorespace”

Issue is /proc/$pid/environ if enabled. Envvars are visible just like args. I think there are other ways to recover if on same uid.