Vandalizing Open-Source Drivers?

[V!NCENT]

I'll take it as a hint since I registered in 2009.

[Delgarde]

The moral of the story: lulz were had, no permanent damage was done, some people got butthurt.

No. Moral of the story, someone with root access on those servers thinks playing pranks is a good use of the trust people have given him. Harmless or not, this is a pretty bad look for FD.o...

[DeepDayze]

And even if rebasing published repositories is not recommended, in this case it is probably a good idea, there is no need to tolerate vandalism even if the project is not thriving.

Exactly, so what is there to gain by even pulling such really childish crap like that on some project that's been rather moribund? Security needs to be tightened up and git's the better way to go about managing a source tree.

Vandalism like this should NEVER be tolerated at any level. It would be good to remove the entire vandalized tree and replace with a last known good version of the tree.

[DeepDayze]

At least you could post "Fck microsoft" instead.
Just joking )

Wish the prankster put "Steve Ballmer was here" instead into the commit so even more lulz would be had :^)

[V!NCENT]

No. Moral of the story, someone with root access on those servers thinks playing pranks is a good use of the trust people have given him. Harmless or not, this is a pretty bad look for FD.o...

You know what concerns me? If somebody can delete an entire git tree without anyone knowing, then how can one detect a simple backdoor?

[stikonas]

You know what concerns me? If somebody can delete an entire git tree without anyone knowing, then how can one detect a simple backdoor?

I doubt that this would be unnoticed unless the tree is unused. If the tree is used, then there are lots of its copies and git will complain if somebody tries to introduce some backdoor into the tree (git check SHA1 hashes of the commits).

[Michael]

It was Adam Jackson: http://lists.x.org/archives/xorg-dev...er/015901.html

[md1032]

Exactly, so what is there to gain by even pulling such really childish crap like that on some project that's been rather moribund? Security needs to be tightened up and git's the better way to go about managing a source tree.

Vandalism like this should NEVER be tolerated at any level. It would be good to remove the entire vandalized tree and replace with a last known good version of the tree.

The vandalism was one added commit on a new branch, so restoring the tree is as simple as deleting the branch. Git is pretty good about guaranteeing that nothing else was changed as long as the commit IDs for the other branches weren't changed. Somebody will obviously have to verify those against known good copies, though.

[mattst88]

You know what concerns me? If somebody can delete an entire git tree without anyone knowing, then how can one detect a simple backdoor?

Where the hell are you getting that a git tree was deleted?

[crazycheese]

It was Adam Jackson: http://lists.x.org/archives/xorg-dev...er/015901.html

He is VERY lucky not being in some corporate entity. Sorry won't be enough - they'd claim $100 Bln compensation from him. Bad moral mood my *** (sorry).