 |
Proposed changes include: * Use the official TDM server is the master for the crc_info.txt file (to prevent compromised hosts distributing infected files) * The above can also be used to check if a particular mirror is up to date (although, we can easily add a file to the mirrors indicating the current version) * Include SHA256 hashes of all the files in addition to the CRC. Also provide SHA256 hashes of the updaters on the TDM download page so that users can verify the integrity of the updater. * Access the updater and crc_info.txt files over HTTPS with a valid certificate (and enforce strict server verification in the updater) |
 |
Do we need this for 2.04, or can it wait for 2.05? |
|
|
It isn't needed for any release in particular. I've removed the target version for now. On a side note, I've started reacquainting myself with the TDM codebase after my lengthy hiatus from development. I've been working on some designs of how I want the updater and mirrors to work, so I'll be implementing that in a branch sometime during the beginning of this year. |
|
|
Ok. Keep track of 2.04 progress here: http://forums.thedarkmod.com/topic/17382-tdm-204/ |
 |
Superseded by 4833 |
 |
Well, 4833 probably does not supersede it, but the new idea described on forums definitely does: http://forums.thedarkmod.com/topic/19486-tdm-update-single-algorithm-to-rule-them-all/#entry430804 |
- Anonymous
