Am 30.11.2019 um 23:28 schrieb Jason Pyeron:
From: Tilman Hausherr [mailto:[email protected]]
Sent: Friday, November 29, 2019 11:21 PM

Hi,
You can see it in PDFDebugger because indirect objects have something like
[19 0 R] in the tree, and direct objects don't.
Yes, got that.

The issue is which dictionary contains the non-indirect entry.

I have often used NOTEPAD++ to look into PDFs... If it is direct then it is on the left, i.e. without a new object with "19 0 obj".

19 0 obj
<<
/dic2key <</key2 value2 /key3 /value3>>
>>
endobj

"dic2key" here has a value which is a direct object which is a dictionary "<</key2 value2 /key3 /value3>>".

Can you share the PDF? I don't understand what you mean with "performing a validation fails".

Tilman



Re signatures, there are many things that can go wrong... changes between
direct / indirect in revisions are bad, not handling locked fields is bad (see
recent answer on stackoverflow)

Does the file validate with ShowSignature.java?
Yes, that is not the issue. It shows as unmodified in Acrobat, but performing a 
validation fails.

Tilman

Am 29.11.2019 um 22:16 schrieb Jason Pyeron:
I am trying to track down differences between Acrobat and PDFBox with
regards to digital signatures.
I have made much progress in eliminating differences, but I am still getting
the dreaded "Bad parameter" when validating the signature.
While I cannot find the reference to quote right now, I seem to remember
that certain entries must be direct and other certain entries must not be
direct in certain dictionaries.
I am inspecting the two PDFs signed by PDFBox and Acrobat, and I clearly
see that PDFBox is making Root/AcroForm/Fields/[0]/Kids/[0]/Kids/[16]/V
direct, whereas Acrobat is indirect. My question is what is the best way to
find which dictionary it is directly stored in? Started with hex editor, and it 
is
not fun :( .
v/r,

Jason Pyeron

--
Jason Pyeron  | Architect
PD Inc        |
10 w 24th St  |
Baltimore, MD |

.com: [email protected]
tel : 202-741-9397




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For
additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional
commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to