Find Sensitive Information

github.com

23 points·eladkaplan··7 comments

I typically just start commands that contain secrets with a space. In most shells, that means "don't add this to the history".

shellclear is a security tool that provides a simple and fast way to secure your shell command history. Sensitive data can be stored in your history file when exporting a token of something or running a script with a token. Sometimes those secrets can be visible to others when sharing your terminal / autocomplete command and more.

* Shellclaer can be a shell plugin that shows a summary of sensitive data when opening a new terminal * Get a list of sensitive data found in the history shells * Clear the sensitive information

What's wrong with:

read -s -r MY_PASSWORD

export MY_PASSWORD

curl -u "admin:$MY_PASSWORD" https://example.com

Env variables are exposed via the /proc filesystem.

I’d just unset histsize and histfile cars for the duration of doing sensitive stuff.

> Env variables are exposed via the /proc filesystem.

Sure, but only your user can read it. How bad is the exposure, really?

If your account gets compromised attackers can use the details from the history to move laterally in the network, because if you have passwords etc in the history then the attackers have access to it as well.

This is especially true for bridge / bastion systems that control access to internal servers. If the passwords/secrets to access the internal servers are in the history they get compromised as well.

Love the project. I'm assuming this is useful for when your using a computer accessible to other people. What would the other applicable uses be?

Reply on news.ycombinator.com