[
https://issues.apache.org/jira/browse/PDFBOX-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111803#comment-17111803
]
Andreas Lehmkühler commented on PDFBOX-4784:
--------------------------------------------
[~mkl], [~bsanchezb] thanks for the explanation. I hoped that those single
steps might be somehow connected so that we might find a way to "cache" the
needed information during processing, but obviously those steps are separately
processed.
[~bsanchezb] Your proposal looks similar to the solution I've had in mind. I'm
going to merge it soon.
> Possibility to provide the SecureRandom to SecurityHandler
> ----------------------------------------------------------
>
> Key: PDFBOX-4784
> URL: https://issues.apache.org/jira/browse/PDFBOX-4784
> Project: PDFBox
> Issue Type: Improvement
> Components: Crypto
> Affects Versions: 2.0.19
> Reporter: Pierrick Vandenbroucke
> Assignee: Andreas Lehmkühler
> Priority: Major
> Fix For: 2.0.20, 3.0.0 PDFBox
>
>
> 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]
