You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the key import process we have to put the client secret key into a command for importing. This poses a security risk since the history file will keep this information for likely either the next 500 or 1000 commands.
There are some options we have that we can provide users to get this information off of their system:
Have the command prefixed with a space character. This depends on the HISTCONTROL environment variable. If it is set to ignoreboth it will not include the command in the history
The above are two possible solutions we can give to users as options for not committing the secret key to their history. They will need to be explored and I am just putting this here as a starting point
The text was updated successfully, but these errors were encountered:
As part of the key import process we have to put the client secret key into a command for importing. This poses a security risk since the history file will keep this information for likely either the next 500 or 1000 commands.
There are some options we have that we can provide users to get this information off of their system:
HISTCONTROL
environment variable. If it is set toignoreboth
it will not include the command in the historyhistory -d $(history 1)
is added onto the end of a command it will remove the command from the history (reference: https://www.tecmint.com/run-linux-command-without-saving-in-history/)The above are two possible solutions we can give to users as options for not committing the secret key to their history. They will need to be explored and I am just putting this here as a starting point
The text was updated successfully, but these errors were encountered: