-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I wonder why the checksum of DSM files was switched from SHA256 to MD5. #99
Comments
大部分的 sha校验都是为了确定文件的完整性,防止下载出现错误, pat 下载完成进行一次校验就好了, |
In the future, I may allow users to upload local PAT, allowing them to create some intermediate versions as loader. |
TTG should not be updated, so there is no need to worry about merging it in the future when modifying it. To be honest, if fbelavenuto keeps iterating ARPL, I won't do this repo. |
From my point of view, both of these values were set in ARPL's config for each model, and it seems to be to unify unnecessary dual management into one MD5.
Is that right?
Doesn't MD5 have other advantages?
And, the difference between ARPL and TCRP’s core mechanism is that ARPL uses jun mode, so it is handled as a 7.0.1 version file created before encryption, and TCRP, on the contrary, requires reassembly of pat files encrypted after 7.1.0. And the sha256 checksum of the pat file resulting from this recombination is recorded and managed once again in the configuration file.
I also think this part is a bit out of principle.
Perhaps even if TCRP adopts MD5, this part seems unavoidable right now.
In the case of TCRP, only SHA256 is used in the loader build phase.
In the installation phase of the DSM file, MD5 is involved through rss.xml and rss.json.
The text was updated successfully, but these errors were encountered: