Ticket Information - ID: #981
| ID: | Category: | Severity | Reproducibility | Date Submitted | Updated By: |
|---|---|---|---|---|---|
| 0000981 | Bug Reporting | normal | always | 07/31/19 02:19PM | Jerl |
|
|
| Summary: | WebM: Reported hash on website differs from actual hash. |
| Description: | Example: /index.php?page=post&s=view&id=3204532 Website reports c21410adcf54658be4c79f4ebdb8a453 as the md5 for the above post. However if you download the file and run md5sum on it, the actual md5 differs: $ md5sum c21410adcf54658be4c79f4ebdb8a453.webm e0783829e869bee4a58837a6dd1e24ae c21410adcf54658be4c79f4ebdb8a453.webm More examples: /index.php?page=post&s=view&id=3646405 /index.php?page=post&s=view&id=3910713 /index.php?page=post&s=view&id=3910925 /index.php?page=post&s=view&id=3646387 /index.php?page=post&s=view&id=3638415 |
| Additional Info: | Bug is always reproducible _for the same file_. However, some webms seem not to be affected by this bug. Example: /index.php?page=post&s=view&id=3071929 The site reports the correct md5 for the above post (3b840022e9374fc8f25678b4a9b3472b). |
lozertuser replied at 2019-07-31 15:24:25  |
| This is a known issue. The problem is that the original file being uploaded is forced to be encoded and it's not an immediate process, so we grab the source file's hash as we need to make sure THAT file isn't re-uploaded. |
chiyachan replied at 2019-07-31 16:01:28 |
| Are there any plans to fix it? Checking the computed md5 against the md5 reported in the API is useful for checking data integrity. |
Jerl replied at 2019-08-08 20:44:04 |
| We tried really hard to avoid having to do it this way in the first place. If we can find a way to fix it, we will. |
