Search Criteria
Package Details: md5jpegdata 1.2-1
| Git Clone URL: | https://aur.archlinux.org/md5jpegdata.git (read-only) |
|---|---|
| Package Base: | md5jpegdata |
| Description: | Tool to calculate the MD5 hashsum of the pure data part of a jpeg-file |
| Upstream URL: | http://www.first.in-berlin.de/software/tools/md5jpegdata/ |
| Licenses: | |
| Submitter: | oriba |
| Maintainer: | oriba |
| Last Packager: | oriba |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2013-02-18 01:21 |
| Last Updated: | 2015-06-09 22:45 |
Latest Comments
oriba commented on 2013-09-26 15:08
There was a bug in the former version, which is now corrected.
The bug was: x and y of the pic were exchanged in calculating the md5-sum.
If you already have a database with the checksums, they now will be different,
so recalculation would be necessary.
In principle it does bot matter, for a checksum if x and y are exchanged, but it was donbe wrong, and it was necessary to fix that bug, because it resulted in crashes (reading x and y wrongly, into non-existing mem-areas (sigsegv).
As this problem is now fixed with version 1.2, anything should be fine now.
oriba commented on 2013-05-17 20:45
This tool makes sense, if you have jpeg-files, where comments were added (e.g. some programs allow to save tags inside jpeg-comments, instead using a seperate database), and you want to find those files with same pictural contents.
If using simple file-checksums, then the files with same picture-data but different jpeg-comments would show up as different files.
If you want to find out if files have SAME PICTURE DATA, even though they differ because of different jpeg-comments, this tool is the right one for solving the problem.