News for hackers. Stuff that matters.
Re:Find Sensitive Information by denysvitali on Wednesday August 24, 2022 @06:47PM (#32586855)
What's wrong with:

read -s -r MY_PASSWORD

export MY_PASSWORD

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

?

Re:Find Sensitive Information by electric_mayhem on Wednesday August 24, 2022 @06:51PM (#32586896)
Env variables are exposed via the /proc filesystem.

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

Re:Find Sensitive Information by yjftsjthsd-h on Wednesday August 24, 2022 @09:01PM (#32588012)
> Env variables are exposed via the /proc filesystem.

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

Re:Find Sensitive Information by suramya_tomar on Saturday August 27, 2022 @12:23AM (#32615669)
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.