[ 
https://issues.apache.org/jira/browse/PDFBOX-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538685#comment-16538685
 ] 

Claudio Tortorelli commented on PDFBOX-4261:
--------------------------------------------

Hi. I confirm the *problem is solved* using ** the NonSequentialParser . 
Can you fix the PDFParser too?

Then, I checked some of our regression test files to test any differences in 
signature using patched/standard versions:
 In one case there is a file that is not signed at all with 1.8.16-SNAPSHOT 
(using both parsers) without any errors, but the signature is done instead 
using old 1.8.12.
I'm evaluating it: I eventually create a separate ticket.

 

> Invalidated signature signing pdf twice 
> ----------------------------------------
>
>                 Key: PDFBOX-4261
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4261
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Signing
>    Affects Versions: 1.8.15
>            Reporter: Claudio Tortorelli
>            Assignee: Tilman Hausherr
>            Priority: Major
>             Fix For: 1.8.16
>
>         Attachments: issue_data.zip
>
>
> A customer sent us a pdf that has this problem: when it is signed twice by 
> *pdfbox 1.8.x* the second signature invalidates the first one.
> If we apply the same procedure using *pdfbox 2.0.x* the problem doesn't 
> occur, but the customer required java 1.5 so we can't switch to the new 
> version in this case.
> For +privacy purposes+ we had anonymized the original PDF file by editing 3 
> stream inside the pdf, without altering the original structure. So the file 
> "92752146_noSign_anonymous.pdf" you can find in attachement has not the 
> original text/image streams, but reproduces the problem as the original one.
> Thank you in advance
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to