5 ms·
It's a little harsh to say he deleted the audit trail. He deleted his bash history. Something I do on a near daily basis.
by kasey_junk 13y ago
It's a little harsh to say he deleted the audit trail. He deleted his bash history. Something I do on a near daily basis.
- ig1 13y agoThe exact details (which aren't disputed) are covered in: http://online.wsj.com/public/resources/documents/021110aleynikovindictment.pdf http://online.wsj.com/public/resources/documents/021110aleyn... Basically he'd written a backup program which was specifically designed to compress both his home directory and propriety code from elsewhere on the system into a file (which it would do depended on parameters passed). On his last day of employment he ran it several times with different parameters which including copying propriety code. He then encrypted the file and then uploaded it to a SVN hosting service before deleting the encryption program and his bash history. Because it was encrypted it bypassed GS's automated scanners. He then downloaded the source files to both his laptop and external flash drive and took them to work at his new employer. Given the (undisputed) facts, he clearly broke several laws, the question is whether he was doing it innocently and just being stupid or if he did it with serious criminal intent.
- nvarsj 13y agoIt's hard to believe he did it accidentally. He probably just underestimated GS's reaction and didn't think it was a big deal. Firms like GS and other HFTs are excessively sensitive about their IP - especially the code base. Whenever an employee leaves, especially to go to a competitor, they're going to have a team of people checking what that person did. When you get in bed with the devil, you need to accept the rules.
- walshemj 13y agoYes he probably had the Russian laissez faire attitude to IP and had obviously not been listening at all to the training courses all big companies have on ethics and computer security. I agree its pretty obvious that this was a deliberate action
- kasey_junk 13y agoI don't doubt he did something illegal and I don't care particularly what his reason is. What is way more troubling to me is how apparently easy it is for Goldman to get the highest levels of government involved and throw the criminal book at someone over what is typically a civil matter.
- ig1 13y agoAny company can ask for a criminal referral on a corporate espionage case (United States v. Nosal is a major one), and while it's becoming more common it's still pretty unusual for companies of all sizes because it's often expensive for the company involved (legal counsel, staff time, etc) and means that they lose control of the case.
- smacktoward 13y ago"The highest levels of government" and "Goldman Sachs" are pretty much interchangeable: http://www.cbsnews.com/8301-31727_162-20001981-10391695.html http://www.cbsnews.com/8301-31727_162-20001981-10391695.html
- foobarqux 13y agoHow was he caught?
- deleted 13y ago[deleted]
- dekhn 13y agoWhy do you delete your bash history daily. For "security"? He deleted his bash history (AFAICT) because it had passwords in it. if you are entering passwords on the command line such that it lands in your history, then you "delete it at the end of the day", you're not securing anything. you can turn off history for one command. That's better than deleting bash_history (well, I don't know what an auditor would say about that). But you should be storing your passwords in secure files, not entering them on the command line.
- kasey_junk 13y agoI rarely nuke my entire history, but frequently prune commands out of it. As I develop I frequently change parameters/calling conventions on the applications I'm writing. While scanning the history I don't want bad commands to still be there. Bash history was never meant to be an audit trail and treating manipulating it as some form of security violation is idiotic.
- mindslight 13y agoWhat are the benefits of not simply putting 'unset HISTFILE' in your shell rc?