[
https://issues.apache.org/jira/browse/PDFBOX-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr updated PDFBOX-3017:
------------------------------------
Description:
Improve signing code:
- incremental save only works for signatures and doesn't respect certificates
such as Adobe Extended Usage Rights
- -{{prepareNonVisualSignature}} clears the AcroForm DR
{{acroForm.setDefaultResources(null)}} which is not good if there are other
form fields-
- visual/nonVisualSignature should move into the {{interactive.forms}} package
and be handled within the signature field
- verify signature (to have tests that go full circle)
- document or refactor / rewrite visible labyrinthine signature code
- support rotated pages (see
https://stackoverflow.com/questions/34012293/pdfbox-sign-landscape-file-error/34359956#34359956
)
- make sure that signed PDF/A files are still PDF/A (see
http://www.pdfa.org/wp-content/uploads/2011/08/tn0006_digital_signatures_in_pdfa-1_2008-03-14.pdf
); /ID possibly not OK; /Annots is possibly required ([~tilman] removed this
for invisible signatures); test signed files with PDF-Tools and with preflight;
test whether "bad" signatures are detected by preflight
- PDFBOX-3363 - why is the stream cached in a file? Should it be done in memory?
- remove {{setVisualSignature(PDVisibleSigProperties visSignatureProperties)}}
from SignatureOptions.java, all it does is to call
{{visSignatureProperties.getVisibleSignature()}} which returns an
{{InputStream}}, and this is already available
- ... your ideas...
was:
Improve signing code:
- incremental save only works for signatures and doesn't respect certificates
such as Adobe Extended Usage Rights
- -{{prepareNonVisualSignature}} clears the AcroForm DR
{{acroForm.setDefaultResources(null)}} which is not good if there are other
form fields-
- visual/nonVisualSignature should move into the {{interactive.forms}} package
and be handled within the signature field
- verify signature (to have tests that go full circle)
- document or refactor / rewrite visible labyrinthine signature code
- support rotated pages (see
https://stackoverflow.com/questions/34012293/pdfbox-sign-landscape-file-error/34359956#34359956
)
- make sure that signed PDF/A files are still PDF/A (see
http://www.pdfa.org/wp-content/uploads/2011/08/tn0006_digital_signatures_in_pdfa-1_2008-03-14.pdf
); /ID possibly not OK; /Annots is possibly required ([~tilman] removed this
for invisible signatures); test signed files with PDF-Tools and with preflight;
test whether "bad" signatures are detected by preflight
- PDFBOX-3363 - why is the stream cached in a file? Should it be done in memory?
- ... your ideas...
> Improve document signing
> ------------------------
>
> Key: PDFBOX-3017
> URL: https://issues.apache.org/jira/browse/PDFBOX-3017
> Project: PDFBox
> Issue Type: Improvement
> Components: Signing
> Affects Versions: 2.0.0
> Reporter: Tilman Hausherr
> Attachments: pdfa_signed_insivible.pdf
>
>
> Improve signing code:
> - incremental save only works for signatures and doesn't respect certificates
> such as Adobe Extended Usage Rights
> - -{{prepareNonVisualSignature}} clears the AcroForm DR
> {{acroForm.setDefaultResources(null)}} which is not good if there are other
> form fields-
> - visual/nonVisualSignature should move into the {{interactive.forms}}
> package and be handled within the signature field
> - verify signature (to have tests that go full circle)
> - document or refactor / rewrite visible labyrinthine signature code
> - support rotated pages (see
> https://stackoverflow.com/questions/34012293/pdfbox-sign-landscape-file-error/34359956#34359956
> )
> - make sure that signed PDF/A files are still PDF/A (see
> http://www.pdfa.org/wp-content/uploads/2011/08/tn0006_digital_signatures_in_pdfa-1_2008-03-14.pdf
> ); /ID possibly not OK; /Annots is possibly required ([~tilman] removed this
> for invisible signatures); test signed files with PDF-Tools and with
> preflight; test whether "bad" signatures are detected by preflight
> - PDFBOX-3363 - why is the stream cached in a file? Should it be done in
> memory?
> - remove {{setVisualSignature(PDVisibleSigProperties
> visSignatureProperties)}} from SignatureOptions.java, all it does is to call
> {{visSignatureProperties.getVisibleSignature()}} which returns an
> {{InputStream}}, and this is already available
> - ... your ideas...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
