Linked by Jordan Spencer Cunningham on Mon 14th Jun 2010 23:58 UTC
Thread beginning with comment 430048
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
While the source tarball was tainted, they didn't fix the md5 string file...anyone caring about security would have run an md5sum and compared it to what the original developers put up there as the original md5 sum.
All done automatically and with better security if you use the package manager system.
Since this package was open source, why didn't they simply submit it to the distributions? That way it would have been part of the various distribution package management systems, as a bonus the original website would not have had bandwidth worries nor the need to find mirrors, and this incident would have been avoided.




Member since:
2005-06-29
While the source tarball was tainted, they didn't fix the md5 string file...anyone caring about security would have run an md5sum and compared it to what the original developers put up there as the original md5 sum.