News for hackers. Stuff that matters.
Re:Kernel.org has been hacked (see site news) by blinkingled on Wednesday August 31, 2011 @07:25PM (#2948018)
They gained root access. So some one could do

sudo su - linus

cd /path/to/linux-2.6.git

modify/exploit code and git commit

I for example do a daily git pull - I will get the the tainted code and not notice it at all.

NO?

Re:Kernel.org has been hacked (see site news) by ajross on Wednesday August 31, 2011 @07:45PM (#2948066)
But that's just HEAD. No offense, but so what? Clearly anyone (sane) running off of a development branch isn't doing so on a security sensitive system. It's an exploit, but only of development systems and a tiny handful of hacker's personal boxes. The value there to an attacker is very low.

What you can't do is inject code that ends up in 3.1-rc5, because before that gets tagged Linus (and a lot of other people) would have to do a merge that would fail inexplicably.

But to be clear: yes, with access to the repository you can (for a brief moment until it's noticed) inject exploit code that will be picked up by anyone building and running an untagged branch HEAD.

Re:Kernel.org has been hacked (see site news) by blinkingled on Wednesday August 31, 2011 @08:01PM (#2948111)
Ubuntu does daily kernel builds and many people run that kernel - to see if some bug has been fixed, to get support for their newer hardware etc. Lots of reasons perfectly sane people can end up testing a daily build.
Re:Kernel.org has been hacked (see site news) by rpearl on Wednesday August 31, 2011 @09:22PM (#2948274)
The code would not be signed by Linus; you do not know his private key.

If I as a developer then pull and verify signatures, I would note that commit was unsigned and expect the commit to be compromised.

Re:Kernel.org has been hacked (see site news) by danieldk on Thursday September 01, 2011 @02:51AM (#2948913)
But you cannot sign commits in git, only tags, right?