4 ms·
By that logic anyone using private browsing mode on a web browser should is suspect. And personally, I would delete shell history on principle when leaving a j
by fluidcruft 12y ago
By that logic anyone using private browsing mode on a web browser should is suspect.
And personally, I would delete shell history on principle when leaving a job. I also delete my browser cookies and stored passwords etc. With the big plastered on warnings everywhere that all computer activity is monitored and recorded, it should be entirely reasonable to assume that these copies are redundant and disposable.
I have a lot of people I have to interact with that insist on force me to login to their stupid sftp servers using plaintext passwords and they configure their servers to force interactive mode. And I very likely have PHI in my command history, too. There's absolutely no reason to not delete shell history when leaving a job, particularly now that HITECH means that I can be personally criminally prosecuted for data breaches.
Besides, what constitutes "deleting shell history"? The way bash works by default, the last closed terminal deletes all the history of the other terminals.
Does Goldman Sacks require users to maintain full shell history files as a condition of employment or as part of their expected work behavior or work product? I very, very much doubt it.
- tptacek 12y agoI would be wary of hiring someone who told me that it was their habit upon leaving a job to erase all traces of what they'd done while working at that job. That does not seem like sound engineering practice to me.
- fluidcruft 12y agoWho said anything about erasing all traces? If you want to use keyloggers to record the minutiae your employee's behavior, by all means record them. That has nothing at all to do with sound engineering. Sound engineering is always about process and documentaion, not surveillance.