Long time no C ( by me ;-) )
Sandip Bhattacharya wrote: [snip]
Whenever a distribution ISO is offered for download, the ISO creators also include an MD5SUM checksum for people to verify both the authenticity and integrity of the image. This is a check against:
1. Somebody distributing malware in the name of the original CD
2. Problems in the download which can corrupt the CD image.
[snip]
Now the problem is that the whole process of copying of CDs from one media to another, introduces artifacts in the image which cause the CD image to start differing from the original downloadable image. The results show in wildly different md5sums of the first generation and second generation copies.
[snip]
So a volunteer CD distributor like me have no way to find out whether a difference in Md5sum is because the image is corrupted or because the copying process modified the image in some harmless way.
Have faced this problem many times before. I solved it by rsyncing the .iso dump to the original .iso file on a known authentic server, whenever I extracted it from a CD with tools such as dd or cdrdao.
Works peacefully!
For the uninitiated, rsync is used here to download only the "difference" bytes between the remote (correct) .iso image and the local (damaged) .iso dump.
-- Vipul Mathur vipul[at]linux-delhi.org http://vipulmathur.org/
_______________________________________________ ilugd mailinglist -- [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/[EMAIL PROTECTED]/
