[
https://issues.apache.org/jira/browse/PDFBOX-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751025#comment-15751025
]
Tilman Hausherr edited comment on PDFBOX-3631 at 12/15/16 11:10 AM:
--------------------------------------------------------------------
I can reproduce the effect by signing and viewing them on my android mobile
phone with google drive pdf viewer. The OK file has the signature, the KO file
hasn't. Very weird.
Things I tried
- set bbox in correct order - no
- sign uncompressed file - no
- sign uncompressed file with xref table instead of XRef stream - yes!
So it's something related to the XRef stream.
Coincidentally, a competing java product has the same problem.
was (Author: tilman):
I can reproduce the effect by signing and viewing them on my android mobile
phone with google drive pdf viewer. The OK file has the signature, the KO file
hasn't. Very weird.
> 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: PDFBOX-3631.zip, PDFJS-4743-signature.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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
