pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryuukei (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PDFBOX-3853) Invisible signature's page catalog tree is not updated
Date Wed, 05 Jul 2017 11:25:01 GMT

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

ryuukei edited comment on PDFBOX-3853 at 7/5/17 11:24 AM:
----------------------------------------------------------

Thanks for your answer, at least we have one agreed point. :D Even there is an adverbial 'usually',
I don't get the point and benefit for treating visible and invisible signature differently
in updating catalog tree.
I have client (JS in general) process for detecting signatures and some operations there.
In older version pdfbox (1.8 actually), it works, after updating to 2.0.6 I found this issue.
As I mentioned in original report, I'm reporting this patch as improvement. Does it cause
any harmful result if we update the catalog tree for non visible signature?


was (Author: ryuukei):
Thanks for your answer, at least we have one agreed point. :D Even there is an adverbial 'usually',
I don't get the point and advantage for treating visible and invisible signature differently.
I have client (JS in general) process for detecting signatures and some operations there.
In older version pdfbox (1.8 actually), it works, after updating to 2.0.6 I found this issue.
As I mentioned in original report, I'm reporting this patch as improvement. Does it cause
any harmful result if we update the catalog tree for non visible signature?

> Invisible signature's page catalog tree is not updated
> ------------------------------------------------------
>
>                 Key: PDFBOX-3853
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3853
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Signing
>    Affects Versions: 2.0.6
>            Reporter: ryuukei
>            Priority: Minor
>              Labels: signature
>         Attachments: PDDocument.patch
>
>
> According latest Acrobat PDF 1.7 speficication:
> http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf
> Page 695, section [Signature Fields]:
> * quote 1:
> The field type ( FT ) is Sig , and the field value
> ( V ) is a signature dictionary containing the signature and specifying various at-
> tributes of the signature field.
> * quote 2:
> Like any other field, a signature field may actually be described by a widget anno-
> tation dictionary containing entries pertaining to an annotation as well as a field
> (see “Widget Annotations” on page 640). The annotation rectangle ( Rect ) in such
> a dictionary gives the position of the field on its page. Signature fields that are not
> intended to be visible should have an annotation rectangle that has zero height
> and width.
> All in all, invisible signature also should be as a Signature Field, which is one type
of Annotation, thus the page catalog tree should be updated as well. 
> For fixing this improvement issue, in the class PDDocument.java L351~L353, instead of
terminating the process after [prepareVisibleSignature] by return, continue with later on
annotation update process would be better.  
> Personally I'm using itext-rups to analyse the pdf catalog structure, after applying
the patch, the signature present in the catalog tree pages/page/annot/sig correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message