If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
pls, md5 or sha1 for ati-driver-installer-10-10-x86.x86_64.run
That's basically not needed, because they are embeeded. Same for nvidia installers and every other self extracting package based on makeself. You could only use it to verify that ati replaced the installer later than official release, that was rarely done when there have been missing control files and such things.
[QUOTE=Kano;155380]That's basically not needed, because they are embeeded. Same for nvidia installers and every other self extracting package based on makeself.
Not true. While it may be good for file/download integrity checking, it does nothing for detecting tampering/haxoring. The bad guy could change the whole package to whatever he wanted, and changed the embedded checksum.
Now, i'm not so paranoid that I think anyone would ever attempt such a complicated man in the middle attack... none the less, its good to have an external checksum.
I have got a script to repackage ati installers I can even change the compression. But it is very unlikely that somebody exchanges the file on the ati server.
Comment