[
https://issues.apache.org/jira/browse/PDFBOX-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098425#comment-17098425
]
Andreas Lehmkühler commented on PDFBOX-4784:
--------------------------------------------
[~pvandenbroucke] Can you elaborate on the main implementation details please?
The signing of the AES protected PDF from the
[commit|https://ec.europa.eu/cefdigital/code/projects/ESIG/repos/dss/commits/12160a133ac2f912595122dbe1ed029181eff902]
mentioned in DSS-1962 works using the CreateSignature example from the 2.0
branch of PDFBox. The only thing I've to change is the pass the password to the
load-method when opening the pdf. I'd really like to reproduce the issue to
understand it and maybe to find an alternative solution without necessarily
providing a custom SecureRandom instance in such cases.
> Possibility to provide the SecureRandom to SecurityHandler
> ----------------------------------------------------------
>
> Key: PDFBOX-4784
> URL: https://issues.apache.org/jira/browse/PDFBOX-4784
> Project: PDFBox
> Issue Type: Improvement
> Reporter: Pierrick Vandenbroucke
> Priority: Major
>
> In DSS, we build electronic signatures with two stateless operations
> (computation of the data to be signed and incorporation of the signature
> value). Currently, the signature creation fails with encrypted documents
> (AES) due to the Initialization Vector generations which produce different
> values at each call.
> We would need a way to "stabilize" this part. We discussed about that on our
> [issue tracker|https://ec.europa.eu/cefdigital/tracker/browse/DSS-1962] and
> the idea would be to provide a custom instance of the SecureRandom to the
> [SecurityHandler|https://github.com/apache/pdfbox/blob/2.0.19/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/SecurityHandler.java#L381].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
