Tiny Core Base > Final Releases
Core v4.7.1
yoshi314:
there is some glitch in scmapps, when attempting to check for updates :
"you are running 4.7.1 . The latest release is 4.7"
i assume it's related to the mirror situation ?
curaga:
Yes, the latest version check is done on ibiblio, and the latest version on ibiblio is 4.7. Please ignore it for now.
roberts:
--- Quote from: yoshi314 on November 30, 2012, 02:49:57 AM ---there is some glitch in scmapps, when attempting to check for updates :
"you are running 4.7.1 . The latest release is 4.7"
i assume it's related to the mirror situation ?
--- End quote ---
I keep hoping for a miracle, but not seeing one...
I have updated the webpage on ibiblio to reflect that the latest relesee is 4.7.1.
I have updated the download page to redirect to Google Code.
genec:
--- Quote from: roberts on November 26, 2012, 04:11:00 PM ---I understand that it will not be as easy or convenient to upgrade.
--- End quote ---
1) Although it is possible to provide direct links, the SHA1 checksums would not be seen
2) I'm not sure the opinion of the community at large but I've regarded MD5 checksums as a borderline integrity check due to the computational feasibility of a collision. I don't know how computationally feasible it would be to have a collision and pass decompression checks. I certainly welcome seeing SHA1 checksums for the ISOs.
curaga:
FWIW, sha1 sums are embedded in the zsync files. If you download via zsync, it checks that for you - if not, you can view the .zsync file in a text editor.
Not sure if those were posted to google code though.
That said, I still would trust md5sum. Being able to get a collision - sure. But to do that so that the compression is still valid ups the ante a lot.
I do believe that's possible. However, doing that without significantly changing the file size, that feat I do regard as improbable enough.
If there was a TinyCore iso at 37mb, that should raise a red flag ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version