Tim wrote: > On Tue, 2010-03-02 at 20:24 -0500, Andre Robatino wrote: >> I use the rawread script from >> >> http://www.troubleshooters.com/linux/coasterless.htm#rawread >> >> which automatically reads the correct size of the ISO, and runs a dd >> command reading exactly that much off the disc. > > I have to ask: Why doesn't the installer's self test routine work that > way? This problem has been around for *years*. How would you embed the checksum in the image, without knowing what the image's checksum is? To put it another way, when you put the checksum in the image, the checksum of the image changes due to the embedding. Usually, with a ROM, say, one writes an image, and computes the checksum in such a manner that by putting it into the location reserved for it (which was originally filled with all zeroes), the checksum of the whole image is zero. However, this is only reasonable for small, not cryptographically secure, checksums. It won't work for MD5 or SHA1, for example, because there is no reasonable way to do it. That's what we mean by "cryptographically secure". It isn't feasible. A smaller, and less robust checksum isn't adequate for checking an image which is GB in size. A 16 bit CRC is ok for a 1MB ROM. It isn't robust enough for a 5GB ISO image. Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} Oppose globalization and One World Governments like the UN. This message made from 100% recycled bits. You have found the bank of Larn. I speak only for myself, and I am unanimous in that! -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
