On: Bashhub – Bash History in the Cloud

[nodesocket]

Not saying I make of habit of this, but sometimes you have to pass sensitive things as arguments (passwords, api tokens, customer data, etc), it happens.

I think client side encryption by Bashhub would alleviate this security concern.

[dllthomas → nodesocket]

That doesn't have to mean typing it at your command line. My approach is typically to set shell variables with read (if I need to type it) or xclip (if I need to paste).

Of course, client side encryption would be great in any case.

[voltagex_ → nodesocket]

One of the AWS config utilities comes to mind - you have to paste in your AWS key if running interactively.

[nodesocket → voltagex_]

Actually `aws configure` is interactive when it asks for input. Those values won't be stored in `history`.