3 ms·
That story takes me back. With today's increased paranoia, one wonders if the Bitkeeper fiasco was just a smokescreen to obscure malicious additions to the kern
by gnu8 13y ago
That story takes me back. With today's increased paranoia, one wonders if the Bitkeeper fiasco was just a smokescreen to obscure malicious additions to the kernel.
- luckydude 13y agoI'm not sure what you are trying to say here (I'm lm, the BK guy). It's not clear if you are suggesting that BK was helping add backdoors or if all the fuss over the BK license was so they could move to something less paranoid so it would be easier to add backdoors or $something_else.
- gnu8 13y agoIt recently became known that the forces that would do evil encourage and exploit situations like the one that occurred with Bitkeeper. I don't suggest that Bitkeeper was complicit with any such scheme though.
- luckydude 13y agoNot sure what to say to this. First of all, BK had nothing to do with this exploit other than to find it. The article was vague on the details if I remember correctly. We found the problem because the code we wrote to export the BK tree to the CVS tree validated the results. The code managed by BK was fine, the code in the CVS tree had been hacked. It was the validation step that caught it. The statement "forces that would do evil encourage and exploit situations like the one that occurred with Bitkeeper" just makes no sense (to me at least, if someone else can parse it please share).
- dTal 13y agoSeems clear enough to me. The forces that would do evil [if they had the chance] = NSA etc. Thus, "The NSA encourage and exploit situations like the one that occurred with Bitkeeper".
- luckydude 13y agoI am dismayed and disgusted with the NSA as much as the next guy, maybe more than the next guy, but suggesting they had anything to do with stick a root backdoor in the kernel is a stretch. I guess it is possible but seems pretty unlikely. Saying it had anything to do with BK just means you didn't read the original article. BitKeeper found the problem that was in the CVS tree. BitKeeper itself was never compromised.
- dTal 13y agoI was not defending the GP, merely clarifying its syntax.