#2089 closed defect (fixed)
Hashes for installation files
Reported by: | stdedos | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 2.5 |
Component: | packaging | Version: | 2.4.x |
Keywords: | Cc: |
Description (last modified by )
Files with hashes for the "official" version are wrong:
https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe.md5 https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe.sha
Also, is there a reason files are named '.sha' for the SHA-1 hash?
HashCheck (at least v2.4.0, https://github.com/gurnec/HashCheck) recognizes (and binds automatically during installation) .sha1
files to match & check them.
Unless there is some reason, would you consider renaming them?
Change History (4)
comment:1 Changed 2 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:2 Changed 2 years ago by
Maybe I should've been more specific (or opened a separate ticket?)
The dist files contain wrong data for verification purposes:
https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe.md5 bfbf0f47cbb7c8df9e4468c161aa3053 Xpra-x86_64_Setup_2.4.2-r21077.exe https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe.sha e2da148f53f4147d99dd63a529e7e0217f21910c Xpra-x86_64_Setup_2.4.2-r21077.exe
whereas the setup filename is Xpra-x86_64_Setup.exe (https://www.xpra.org/dists/windows/Xpra-x86_64_Setup.exe)
I understand why, but it impedes automatic verification.
comment:3 Changed 2 years ago by
Oh, now I get it.
Wontfix: those are symlinks, apache doesn't know how to show them.
comment:4 Changed 5 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2089
Done, we still have both in the download directories for now.
Just in case there are links to those.