It's just the servers. The kernel repositories weren't modified, and even if they were, git makes it pretty impossible to modify history if you're paying attention -- the next push would fail as a non-fast-forward.
Also, in the mailing list thread, someone actually went back and verified the contents of all the old tarballs and compared them to the bits from Git, since otherwise someone could have changed the tarball releases.
Comments
Is it just their servers, or was the kernel distribution itself compromised? I can't tell from this.
It's just the servers. The kernel repositories weren't modified, and even if they were, git makes it pretty impossible to modify history if you're paying attention -- the next push would fail as a non-fast-forward.
Also, in the mailing list thread, someone actually went back and verified the contents of all the old tarballs and compared them to the bits from Git, since otherwise someone could have changed the tarball releases.