Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Shell Productivity Tips and Tricks

blog.balthazar-rouberol.com

Post reply on HN
Print view View original

21–30 of 97 posts

Re: Shell Productivity Tips and Tricks

#21

Post by tyingq »

jpxw wrote: post #11

> If you want to remove a sensitive command from your history, you can simply edit your $HISTFILE history file and remove it. It’s already too late at this point. Anybody on your machine can read the commands you are running, for example with ps. You should instinctively avoid entering anything in plaintext into a terminal which you don’t want other people to see. Any command line tool worth its salt will provide alt…

Not a real solution, but you can assign new values to argv/argc to hide things from ps.

With Perl, for example, assign to $0.

$0="what /bin/ps will see";

Re: Shell Productivity Tips and Tricks

#22

Post by jedimastert »

cassiet wrote: post #18
jpxw wrote: post #11

> If you want to remove a sensitive command from your history, you can simply edit your $HISTFILE history file and remove it. It’s already too late at this point. Anybody on your machine can read the commands you are running, for example with ps. You should instinctively avoid entering anything in plaintext into a terminal which you don’t want other people to see. Any command line tool worth its salt will provide alt…

How exactly?

I think what OP meant was closer to "if it could have been entered into the bash history than there's other ways it could be seen".

Most CLI programs that need sensetive information as input should either do it interactively (a la sudo), as standard input, or configuration file. If worst comes to very worst, you can put the sensitive info in a text file and use backticks. For example:

  some-command --username=jedimastert --password=`cat secret.txt`

Re: Shell Productivity Tips and Tricks

#23

Post by rrmm »

jpxw wrote: post #11

> If you want to remove a sensitive command from your history, you can simply edit your $HISTFILE history file and remove it. It’s already too late at this point. Anybody on your machine can read the commands you are running, for example with ps. You should instinctively avoid entering anything in plaintext into a terminal which you don’t want other people to see. Any command line tool worth its salt will provide alt…

The worst is when you expect a password prompt so you type the password and hit enter, but you mistyped the original command and you end up typing your password in plaintext onto the command line. oops.

Re: Shell Productivity Tips and Tricks

#24

Post by lmz »

jedimastert wrote: post #22
cassiet wrote: post #18

Earlier quoted context omitted.

How exactly?

I think what OP meant was closer to "if it could have been entered into the bash history than there's other ways it could be seen". Most CLI programs that need sensetive information as input should either do it interactively (a la sudo), as standard input, or configuration file. If worst comes to very worst, you can put the sensitive info in a text file and use backticks. For example: some-command --username=jedimast…

How would backticks help with hiding it from ps?

Re: Shell Productivity Tips and Tricks

#26

Post by ptzz »

rwnspace wrote: post #20
tcoff91 wrote: post #3

fzf fizzy history search with ctrl-r is my favorite new shell trick. Fzf is a wonderful program

I too prefer fizzy history. It's like Sodastream for your shell! Skim [0] is a nice alternative to fzf [1], mainly for the fact you can call additional commands dynamically like so [2]: sk --ansi -i -c 'rg --color=always --line-number "{}"' [0] https://github.com/lotabout/skim [1] https://github.com/lotabout/skim#difference-to-fzf [2] https://github.com/lotabout/skim#interactive-mode

Would that correspond to piping the output of the additional command to fzf?

Re: Shell Productivity Tips and Tricks

#27

Post by alufers »

The single best shell productivity tip for me was to use z:

https://github.com/rupa/z

It automatically makes a list of directories you frequently use in your shell and if you type `z a-small-substring-of-the-directory-path` it does a cd to that directory. (e.g. I type `z and` and it changes my current directory to $HOME/Work/Projects/android`). Saved me tons of typing.

Re: Shell Productivity Tips and Tricks

#29

Post by Spivak »

alufers wrote: post #27

The single best shell productivity tip for me was to use z: https://github.com/rupa/z It automatically makes a list of directories you frequently use in your shell and if you type `z a-small-substring-of-the-directory-path` it does a cd to that directory. (e.g. I type `z and` and it changes my current directory to $HOME/Work/Projects/android`). Saved me tons of typing.

A somewhat less fancy version of this is $CDPATH.

   export CDPATH="/path/to/my/projects:$HOME/Work/Projects"
   # From anywhere.
   cd andr

Re: Shell Productivity Tips and Tricks

#30

Post by bhaak »

lolive wrote: post #8

Whoever can point me at a robust method to save/restore bash histories of a tmux session would save my life!!! [And yes i use tmux inside tmux]

I'm using a variant of this: https://spin.atomicobject.com/2016/05/28/log-bash-history/

Logging the entire bash history in files sorted by day: export PROMPT_COMMAND='if [ "$(id -u)" -ne 0 ]; then echo "$(date "+%Y-%m-%d.%H:%M:%S") $(pwd) $(history 1)" >> ~/.logs/bash-history-$(date "+%Y-%m-%d").log; fi'

I haven't overloaded ctrl-r yet to search in these files but that would be a possibility.

Post reply on HN