MikelKlink
Advocate
MikelKlink
Advocate
Activity
‎Jan 06, 2025
12:32 PM
The problem is the same as explained in this answer and in multiple others here and elsewhere; there is a small error in the original version of the document that usually is ignored by PDF viewers (including Acrobat) but that makes Acrobat reject signatures not covering the full document. The error is that this initial document revision has a PDF object cross reference table that is split into multiple subsections and has gaps: xref
0 5
0000000000 65535 f
0000000023 00000 n
0000000252 00000 n
0000000321 00000 n
0000000448 00000 n
6 39
0000000727 00000 n
... Both aspects are forbidden. The initial revision of your document claims to be created by Aspose.PDF for .NET 24.11.0; the Aspose PDF components have a long history of producing PDFs with this error. For details see the answer referenced above and more answers referenced from there.
... View more
‎Jan 06, 2025
07:56 AM
2 Upvotes
For the main error see this answer - The revision with the troublesome signature contains errors causing the modification detection checks for later incremental updates to fail. Additionally, though, the files attached to this question are slightly different from the file attached there, they contain some streams whose contents have been overwritten with space characters. As those streams at the same time claim to be flate encoded, this gives rise to additional errors in these files here which may cause even weirder effects.
... View more
‎Jan 06, 2025
07:46 AM
See this answer to your duplicate question: The revision with the troublesome signature contains errors: The Length entries of all streams are incorrect. When validating the file as is, with the troublesome signature covering the whole file, Acrobat essentially only checks the signed hash value when checking for file changes, and so can succeed. But when validatingf the file with additional incremental updates, Acrobat applies additional checks when checking for file changes, and these checks are very sensitive to structural PDF errors. You ask "Acrobat bug?" - the actual bug is that Acrobat (and virtually every other PDF viewer) don't immediately reject test.pdf or at least warn their users that test.pdf has multiple structural errors which may result in any kind of later misbehavior.
... View more
‎Jan 06, 2025
07:33 AM
1 Upvote
I had another look at your file, and I think I found the cause of the issue: In the final revision of test.pdf (the revision with the troublesome signature) all stream Length entries are incorrect, in some cases they even claim stream lengths that would make the stream exceed the end of the file. I added an annotation with Acrobat and then fixed the stream Length entries in a hex editor; now Acrobat shows "Document has been altered or corrupted since it was signed" - yes, of course, my changes did alter the document bytes. To compare with that I applied some arbitrary but harmless changes after adding an annotation; in this case, even though the hash of the signed bytes also was changed, Acrobat continues showing "The signature byte range is invalid". Thus, fixing the stream lengths makes a difference! Effectively those streams with the incorrect Length entries are broken, so your test.pdf document (and all similarly signed documents) will show that error in Acrobat after adding an incremental update.
... View more
‎Jan 06, 2025
03:09 AM
The Application instructions indicate that you may need to "print as PDF" to save as a new PDF file before you can sign, but neither Reader nor Acrobat Pro allows this! The online instructions say: This is possible using the current Acrobat Pro. That been said, where exactly did you get your PDF file from and which Acrobat version do you use? I just googled and found https://www.canada.ca/en/immigration-refugees-citizenship/services/application/application-forms-guides/imm5532.html for which the security settings in the current Adobe Acrobat Pro indicate that signing is allowed. (I tested with the current Windows version.)
... View more
‎Jan 06, 2025
02:45 AM
There is an error in the way that "Assinado digitalmente" has been added to each page of the document. For example on page 1: That symbol has been added to the page by additionally showing a form XObject FFT0 which in turn shows a form XObject F0 which then shows a bitmap image Im1. The error is in the form XObject F0: q
1 0 0 1 2.8346 3.8346 cm
0.1867 0 0 0.1867 0 0.0934 cm
q
167 0 0 166 0 0 cm
/Im1 Do
Q
Q
Q As you can see, there is a closing Q (restore-graphics-state) too many. Some viewers ignore this kind of error. But while this error is indeed easy to ignore technically, it often indicates that somewhere there is a missing q (save-graphics-state) before that extra Q, and that the content between that missing q and the final extra Q is displayed incorrectly (at the wrong position, at the wrong scale, in wrong colors, ...). Thus, it is sensible that Acrobat does not show that broken XObject but warn instead. You should inform the producer of that PDF about the error in their PDFs and ask them for a copy without it.
... View more
‎Jan 06, 2025
02:04 AM
Ich fürchte, für eine tatsächliche Analyse werden nicht nur solche Metadaten sondern das tatsächliche PDF benötigt. Ich selbst habe allerdings nicht die notwendige Erfahrung, um solch eine Analyse ernsthaft durchzuführen.
... View more
‎Jan 04, 2025
01:59 AM
1 Upvote
Nicht nur der Klammervermerk ist verschoben, die ganze folgende Dokumentseite ist verschoben. Dies kann auf eine Manipulation hinweisen, es kann aber auch ein Verrutschen der Seite beim Scannen gewesen sein. Aufschluss könnte eine Analyse der internen Rohdaten des Scans im PDF liefern, Screenshots reichen nicht.
... View more
‎Jan 02, 2025
05:53 AM
1 Upvote
You have a PDF with a hybrid form definition, it contains both an AcroForm form definition and a XFA form definition. This is meant to allow XFA aware viewers to display a form based on the (more flexible) XFA definition while XFA non-aware viewers can still display the (native PDF) AcroForm form. In your case the third party library appears to have filled in the AcroForm field but not the XFA field. As a consequence XFA aware viewers will not show the values but others will.
... View more
‎Dec 30, 2024
02:12 PM
Have you activated some option to include all the validation related information required for "LTV-enabling" the signature? In that case you may now suddenly include a full CRL instead of merely a small OCSP response. This can happen whenever the servers of your certificate authority have issues. Without more details, though, this essentially is plain guesswork.
... View more
‎Dec 27, 2024
01:46 PM
Well, as long as you don't forward your translation to arbitrary others, ISO likely won't care. In that case, just as @try67 mentioned: That PDF originally has been published without encryption. You may still find such a copy on the web. And another option: ISO 32000-1 actually is somewhat outdated. Since 2017 there has been ISO 32000-2 of which an update has been published in 2020. Also there are numerous errata for it. You can receive a version for free via the PDF association.
... View more
‎Dec 27, 2024
01:05 PM
Please remember that the PDF32000 file is derived from the ISO 32000-1 standard with different page headers. In the copyright notice you'll find: The technical material is identical between this version and the ISO Standard; the page and sections numbers are also preserved. Requests for permission to reproduce this document for any purpose should be arranged with ISO. Thus, this file has been published with specific objectives (identical technical material on the same pages and in the same sections). To motivate people to keep it this way, permissions have been limited. Also please consider the second sentence of the quote - I'd assume that translating the document into other languages is a way to reproduce the document, so before starting the translation you should contact ISO to ask for permission and for restrictions your translation will be subject to.
... View more
‎Dec 27, 2024
12:30 AM
I started analyzing the issue. There are some minor issues in the file, but I couldn't clearly reduce the issue to then. Merely, when removing the revision with the last signature and applying a new one with some signing software I have here, the issue does not occur anymore. Thus, the issue is clearly rooted in that final file revision. But it can be anything, some property of the signature itself or some structure element completely unrelated to the actual signature in that revision. I'll take another look next year.
... View more
‎Dec 25, 2024
03:37 AM
This may also indicate an issue of the PDF itself, making Acrobat to repair that issue in memory and so changing the signed data. I'm only on a smart phone now and, therefore, cannot analyze the file. I'll take a look later this week.
... View more
‎Dec 23, 2024
10:06 AM
The blue color can be in the PDF or can be generated by a viewer. Or both. As you neither share the PDF in question not name the other software, it is unclear which is the case. But most common is indeed that the PDF does not use the blue color but a viewer highlights the field using it.
... View more
‎Dec 16, 2024
01:31 AM
1 Upvote
Can you share the PDF for analysis?
... View more
‎Dec 16, 2024
01:26 AM
In short: Both icons imply that you have an approval signature with a positive identity check. In the former case permitted, signed changes exist, in the latter case the document is unchanged. Please take a look at the following cheat sheet for the symbols in general: (This cheat sheet is for Adobe Acrobat and Reader 9; meanwhile some icons have slightly changed in design.)
... View more
‎Dec 13, 2024
03:15 AM
1 Upvote
Well, there is the Acrobat uservoice forum. I don't know, though, how seriously Adobe takes the messages there.
... View more
‎Dec 13, 2024
03:07 AM
As far as I know that format cannot be changed. See also: When using certificates to digitally sign a document can I change the date format displayed on the signature from 2017.09.20 to 20 Sep 2017? Change date format in Certify signature
... View more
‎Dec 12, 2024
03:15 AM
Please explain more exactly which date displayed where shall be formatted differently?
... View more
‎Dec 11, 2024
09:19 AM
1 Upvote
There can be two sets of metadata in a PDF, the old info dictionary and the newer metadata streams. PDF processors are expected to keep those two sets in sync, but when they do differ, some PDF processors display the data from one source and some from the other.
... View more
‎Dec 10, 2024
10:00 AM
Highlighting is filling the selected area with the selected color in Blend Mode "Multiply". The definition of Multiply in the PDF spec in particular explains: When working with additive colours, multiplying any colour with black produces black while multiplying with white leaves the original colour unchanged. In other words, it is expected that highlighting with white doesn't change anything.
... View more
‎Dec 10, 2024
09:48 AM
Can you share the original PDF in question? There are some techniques to make content difficult to change with Acrobat, maybe such a technique has been used in your case.
... View more
‎Dec 04, 2024
10:26 PM
Please share the PDF (or a test PDF with the same issue) for analysis. It sounds like that website that generated your form did something peculiar, but there are lots of peculiar things that may have been done...
... View more
‎Nov 29, 2024
11:32 PM
1 Upvote
Without analyzing the PDF itself I see two possible reasons: The person you've emailed the PDF to has opened it in a viewer that does not support applying digital signatures. In that case the signature field may not be selectable at all, and the appearance of an empty signature field usually is blank. When creating the form you created it for filling in and signing via the Acrobat Sign service. Those forms are a bit different from those created for use on the local computer. In particular signature fields are different. You select this form type by having the check box "This form requires signatures" checked when starting to create the form.
... View more
‎Nov 27, 2024
10:33 AM
After signing with Acrobat Sign PDFs usually are locked and cannot be further manipulated without breaking the existing signature. So is the Acrobat Sign signing workflow already finished and you received the final result thereof? Then you can likely not add your signature anymore. Or is the Acrobat Sign workflow still in progress and add part thereof it's now your turn to sign? Then follow the instructions you got with the notification that it's your turn.
... View more
‎Nov 27, 2024
07:43 AM
I don't see the tag names from the right side of your screen shot (Cover, Chapter, ...) anywhere at top level in your file, only Part entries. Also you mention role mappings but the RoleMap dictionary of the structure tree of your PDF is empty. I might overlook something here, though, so someone who knows more about tagged files should take a look.
... View more
‎Nov 26, 2024
08:47 AM
Without the document (Word and PDF version) it's difficult to tell for sure. But you are aware that Word files are not in general meant to keep their exact layout? Depending on particular on the target output (specific printer, converter, ...) there can be small differences in character positioning which can result in different line breaks which can change the layout considerably.
... View more
‎Nov 26, 2024
07:53 AM
Can you share the PDF for analysis?
... View more
‎Nov 25, 2024
02:08 PM
Chances are that there indeed is an error in the file. Different viewers react in different ways to errors in PDFs. Many try to repair them but not in the same way. So for certain broken PDFs some PDF viewers are more successful repairing the issue than others. Nonetheless, the issue in such situations is not the viewer but the file. Can you share an example file illustrating the issue for analysis?
... View more