3 ms·
He did try to cover his tracks, right? Seems like a lot of effort and risk for "innocuous code". No, he did not try to "cover his tracks". He was clearing his
by chrisbennet 12y ago
He did try to cover his tracks, right? Seems like a lot of effort and risk for "innocuous code".
No, he did not try to "cover his tracks". He was clearing his bash history because it also had his password. I'm not a Linux guy so I don't know details.
- dreamweapon 12y agoThat's my recollection from the original VF article, yes. And yes, his explanation was perfectly plausible. If I were in charge of loss prevention at GS, I'd be more worried about folks who don't clear their shell history when sensitive passwords are used.