2011-01-05, 11:57
HEY! Great project, xbmc fokes!!!!
Late on 2011-01-04, I fetched my copy of xbmc-10.0-live.iso
$ md5sum xbmc-10.0-live.iso
calculates out to be:
11f91f6ba0a0f710068a5ee0f9a4aa66
EDIT - and that matches the master copy of that particular release, now available at URL:
http://mirrors.xbmc.org/releases/liv...iso.mirrorlist
THANKS TheUni and all the xbmc team!!
for prompt response (following post)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Further Reading: What the heck is an md5sum?
Before burning a coaster with a nice large _flawed_ ISO image, it can be a nice wee exercise to generate an integrity check 'signature' by reading the humongous file, and then compare your results with the 'signature' of the original master copy. Usually hosts&mirrors of large files will put similarly-named files near the big files, (maybe beside the xbmczzzz.ISO file, we'd see xbmczzzz.ISO.md5). These helpful extra information files would simply contain the 32 bytes of ascii (plain vanilla) text of the integrity-check 'signature', as generated by the creator elves in the actual sweatshop.
The two popular Posix/Unix/Linux/BSD/BeOS tools to generate unique 'signature' strings (often mistakenly called 'checksum') ARE:
md5sum <--32 chars (adequate)
sha256 <- - - 64 chars
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"The beatings will continue, until morale improves."
Late on 2011-01-04, I fetched my copy of xbmc-10.0-live.iso
$ md5sum xbmc-10.0-live.iso
calculates out to be:
11f91f6ba0a0f710068a5ee0f9a4aa66
EDIT - and that matches the master copy of that particular release, now available at URL:
http://mirrors.xbmc.org/releases/liv...iso.mirrorlist
THANKS TheUni and all the xbmc team!!
for prompt response (following post)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Further Reading: What the heck is an md5sum?
Before burning a coaster with a nice large _flawed_ ISO image, it can be a nice wee exercise to generate an integrity check 'signature' by reading the humongous file, and then compare your results with the 'signature' of the original master copy. Usually hosts&mirrors of large files will put similarly-named files near the big files, (maybe beside the xbmczzzz.ISO file, we'd see xbmczzzz.ISO.md5). These helpful extra information files would simply contain the 32 bytes of ascii (plain vanilla) text of the integrity-check 'signature', as generated by the creator elves in the actual sweatshop.
The two popular Posix/Unix/Linux/BSD/BeOS tools to generate unique 'signature' strings (often mistakenly called 'checksum') ARE:
md5sum <--32 chars (adequate)
sha256 <- - - 64 chars
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"The beatings will continue, until morale improves."
