Am 07.10.23 um 06:43 schrieb John Lussmyer:
I doubt there is a way.
It's most likely that the signing code makes a MD5 checksum (or similar)
of the file when it is signed.
If the file is changed, checking the signing will re-calculate the
checksum and find that it is different. There isn't a
It's a lot more subtle than that. I wrote the MDP code for Adobe Acrobat
9 (June 2008). Certainly there are the obvious changes: something in a
content stream changed, but then there are less obvious changes
(appearance string changes for annotations that are locked). One which I
just ran into
I doubt there is a way.
It's most likely that the signing code makes a MD5 checksum (or similar)
of the file when it is signed.
If the file is changed, checking the signing will re-calculate the
checksum and find that it is different. There isn't any info on what
changed, just that SOMETHING c
On 06.10.2023 19:50, Marc Kaufman wrote:
I find myself debugging PDF files where Acrobat claims "Document has
been altered or corrupted since it was signed." I would dearly love to
see which objects belong to the last xref (color code is OK). Has
anyone added that feature to PDF Debugger, or kn
4 matches
Mail list logo
