Agreed, it's just an unnecessary risk you're taking. Even though the people at kernel.org claim that the git tree easily recognizes changes in the code, the changes in build 187 were minor so there really is no point. Just wait till everything is back to normality
This, this and THIS.
I'm content with waiting until the git tree has been audited and we're sure nothing naughty slipped through--I'd prefer waiting and being careful, rather than being impatient and potentially getting a compromised system.
And to folks wondering WTF would do this--there's a large list, including state actors (including an apparent state actor that widely compromised one of the two main Netherlands SSL certificate authorities to the point it will have to shut down--there's plenty of news coverage on the Internet, just google "DigiNotar hack"), malware creators linked to Russian cybercrime (most spam sent now and most malware developed is done by all of six or seven known spam-gangs tightly connected to the Russian mob), and possibly even misguided cyberactivism (a la Antisec et al).
The first two would be the major things to worry about, IMHO--unlike Antisec et al, state actors and cybercrime gangs (as in spammers/malware producers) would be going in to specifically insert system compromises--specifically placing in back doors for fast-flux networks or man-in-the-middle attacks to defeat VPNs and the like. (Spamgangs are known anymore for the former, whilst the DigiNotar hack involved man-in-the-middle attacks and bogus SSL certificates.)
Main thing now is getting things locked back up and making sure the folks who broke in didn't leave any nasty surprises.
Last edited:
