Should be possible to sanitise option values containing sensitive information before storing the result into the history

[martijnbrinkers]

If a shell command supports a password option, the password will be stored in the history. To prevent logging the password, as a workaround I added a rule to ignore the complete line if the line contains the keyword "password":

history-ignore: "password"

It would however be nice if I can add an annotation to an option which will result in sanitizing the option value, i.e., replace the option value by '***'

[jvalkeal]

Having something like sensitive flag would be nice idea. Other parts could then use that info for making better decisions.