You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tilman Hausherr (JIRA)" <ji...@apache.org> on 2018/03/27 17:44:01 UTC

[jira] [Commented] (PDFBOX-3631) Signature Interoperability Issue

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

Tilman Hausherr commented on PDFBOX-3631:
-----------------------------------------

Thanks to Gabriel Madeira Pessoa in the user mailing list

[https://mail-archives.apache.org/mod_mbox/pdfbox-users/201803.mbox/%3Cbc1eac6441555f3c6f39b5dd8c2f259a%40bry.com.br%3E]

the problem may be solved soon. The cause is that the object number of the XRef stream is reused by a different object in the incremental part.

We don't store the object number of the XRef stream. (COSParser.parseXrefObjStream()). This makes sense because this is recreated when doing a classic save. 
 
My first thought was to add 1 to the highest number, but this doesn't work because there is no guarantee that the object number of the XRef stream is the highest. (Seen in 007087-payment-due-p1_reduced_bc0.pdf) 
 
Analyzing the last trailer (/Index and /Size) doesn't help either, it is unclear which trailer is taken. 
 
So my current thought is to have COSParser.parseXrefObjStream() store the highest XRef object key number in the COSDocument object and check it later.

> Signature Interoperability Issue
> --------------------------------
>
>                 Key: PDFBOX-3631
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3631
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Signing
>    Affects Versions: 2.0.3
>         Environment: Java 1.8 Windows.
>            Reporter: Marco Monacelli
>            Priority: Minor
>         Attachments: Microsoft_Edge_on_Windows_10_rendering_correct.png, PDFBOX-3631.zip, PDFJS-4743-signature.pdf, Preview_rendering_not_correct.png, acrobat_rendering_correct.png, chrome_rendering_incorrect.png, firefox_incorrect_but_expected.png, libreoffice_rendering_correct.png, not_working_pdf_with_signatures.pdf, preview_of_Preview_rendering_correct.png, safari_using_preview_incorrect.png, test_out_pdf.pdf, working_pdf_with_signatures.pdf, working_pdf_with_signatures.pdf
>
>
> Some files if signed with PDFBox produce not visible signature in chrome, pdfium foxit. 
> If the same file is signed on some Actobat, Foxit or itext the signature is visible.
> The test fle are inserted in an encrypted zip. If possible I would like to communicate the password with a private message.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org