News for hackers. Stuff that matters.
Re:I quit my job to work full time on my open source project by euos on Wednesday January 10, 2024 @01:15AM (#38936850)
What do you have in the history that’s sensitive? Keys, passwords should not be in shell history anyways (e.g. I delete them from bash history if I enter by mistake)
Re:I quit my job to work full time on my open source project by the_arun on Wednesday January 10, 2024 @02:41AM (#38937359)
Shell history is wiped out after user logged out for a reason. More details are here - https://www.securityhq.com/blog/security-101-dont-bash-your-....
Re:I quit my job to work full time on my open source project by wswope on Wednesday January 10, 2024 @12:44PM (#38941073)
Please read the page you linked; it’s flushed to a file, not wiped.
Re:I quit my job to work full time on my open source project by euos on Thursday January 11, 2024 @09:53PM (#38963065)
It is not. I definitely use months-old bash history through !? shortcuts.
Re:I quit my job to work full time on my open source project by extheat on Wednesday January 10, 2024 @01:23AM (#38936906)
I don't think it's that unusual. What comes to mind immediately is it's not unusual for me to clone something from a private git repo, where a username+password would be needed for permissions. In which case it's possible to put in `git clone http://username:[email protected]` or another git command that interacts with remotes. (To be clear the "password" is typically a token and not human generated string, but still functions like a password).
Re:I quit my job to work full time on my open source project by drbaba on Wednesday January 10, 2024 @01:39AM (#38937001)
For that example: Any reason the server doesn’t just have an SSH server? Then you can use `git clone` in the “usual way”, using SSH certificate authentication.