When computing md5sums for photos having images.md5sum=null (basically all photos added by sync), the add_md5sum function randomly assign md5sum to provided list of photo ids. If you ask to add the md5um to 10 photos, photo number 2 might get the md5sum of photo 7... Not good.
We haven't seen the problem in 7 years because Piwigo only searches for missing md5sums. Not "inaccurate" md5sums. This might change in the future with advanced file integrity checks.
When computing md5sums for photos having `images.md5sum=null` (basically all photos added by sync), the `add_md5sum` function randomly assign md5sum to provided list of photo ids. If you ask to add the md5um to 10 photos, photo number 2 might get the md5sum of photo 7... Not good.
We haven't seen the problem in 7 years because Piwigo only searches for missing md5sums. Not "inaccurate" md5sums. This might change in the future with advanced file integrity checks.
<!-- github-sync-id:2827876855 -->
In https://github.com/plegall/Piwigo-virtualize/commit/03be498a8c118d40b7843798cc526e9604aaf449 I have decided to forbid virtualization if you have missing md5sums
<!-- github-comment-id:3065663669 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When computing md5sums for photos having
images.md5sum=null(basically all photos added by sync), theadd_md5sumfunction randomly assign md5sum to provided list of photo ids. If you ask to add the md5um to 10 photos, photo number 2 might get the md5sum of photo 7... Not good.We haven't seen the problem in 7 years because Piwigo only searches for missing md5sums. Not "inaccurate" md5sums. This might change in the future with advanced file integrity checks.
In https://github.com/plegall/Piwigo-virtualize/commit/03be498a8c118d40b7843798cc526e9604aaf449 I have decided to forbid virtualization if you have missing md5sums