5 ms·
The negligence was only in losing control of the code. I guess successfully maintaining tight control of the code would be a mitigating factor (or, more likely,
by mseebach 9y ago
The negligence was only in losing control of the code. I guess successfully maintaining tight control of the code would be a mitigating factor (or, more likely, lead to not getting caught), but taking the code from Apple for the purpose of sharing it with these researchers in the first place is clearly premeditated (so, showing intent) theft.
- yeukhon 9y agoYes, it’s stealing afterall. Taking screenshots using one’s phone is still possible to steal the code, although the effort would be tedious for a large codebase. But for an active adversary, if that’s the only method, he/she would do it. I fear there is no way around that, even with logging enabled (there will be thousands of accessing the codebase per day). If the proposal is to lock down the repository and requires approval, that will make the development very slow. Not even in the banking would a manager want to ask “why” all the time...
- mseebach 9y agoI have no idea what they might do, but it's not a law of nature that they have to crack down on access. They have tens of thousands of employees, a single breach isn't evidence that a trusting, open environment doesn't work.