#11325 closed enhancement (wontfix)
Provide jar checksum in status report
Reported by: | naoliv | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
JOSM should also include in its status report a checksum/hash (MD5, SHA1 or other) of the jar file, if possible.
This would allow the developers to see if the file differs from the official one (for example, in #11300 it could be used to see if users are really using the latest JOSM release or if their jar has been modified/corrupted).
Attachments (0)
Change History (3)
comment:1 by , 10 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:3 by , 10 years ago
Replying to naoliv:
But it won't hurt to have this...
Well, that's not so easy. First we provide download options to strip certain parts of the jar (e.g. the signatures or the language files). Second debian and others do their own builds. And third calculating the checksum is not that trivial, as it requires access to the system which may not always be easy (i.e. webstart). So a lot of trouble and only little benefit... :-)
Happens to seldom to be necessary.