Could ReactOS files: 'BootCD', 'LiveCD' and files from Trunk Daily Builds have shasums (sha256sum and sha512sum) to verify its integrity?
Or at least md5sums?
GNU/Linux uses verification hashes sums.
verification hashes sums
Moderator: Moderator Team
Re: verification hashes sums
SF download page has SHA1 and MD5 sums for BootCD and LiveCD files.
- Swyter
- Posts: 114
- Joined: Sun Apr 10, 2011 11:21 am
- Location: Spain ← Europe ← Planet Earth ← Milky Way ← Universe
Re: verification hashes sums
It's not the same thing, but most of the builds get served from HTTPS. Just check the chain of trust.
I added HTTPS and SHA1 support for RAPPS packages (many of which are downloaded from their original locations using plain HTTP), and some other dev added HTTPS certificate pinning for the RAPPS database update.
Overall, I think we are mostly covered in that front.
I added HTTPS and SHA1 support for RAPPS packages (many of which are downloaded from their original locations using plain HTTP), and some other dev added HTTPS certificate pinning for the RAPPS database update.
Overall, I think we are mostly covered in that front.
External patch contributor for ux/user-mode/l10n/winapi. Sometimes I fix a bit of everything everywhere.
Re: verification hashes sums
There are two reasons to use checksums:
1) check if the archive was downloaded properly without errors
2) check whether the storage wasn't tampered with
HTTPS covers the issue 2). The ISOs from build server are compressed into an archive, so there should be a checksum as part of the file format, but IIRC only CRC32 is used, that may not be enough to cover issue 1).
1) check if the archive was downloaded properly without errors
2) check whether the storage wasn't tampered with
HTTPS covers the issue 2). The ISOs from build server are compressed into an archive, so there should be a checksum as part of the file format, but IIRC only CRC32 is used, that may not be enough to cover issue 1).
Who is online
Users browsing this forum: No registered users and 48 guests