[
https://issues.apache.org/jira/browse/PDFBOX-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770389#comment-16770389
]
Michael Klink commented on PDFBOX-4453:
---------------------------------------
I think that will relevantly improve the chances of positively recognizing a
signature value while the chance of a false positive increases only slightly.
Thus, as long as you don't intend to somehow keep the "undecrypted" string for
explicit retrieval by e.g. the signature validation code, your proposed
solution is as good as you can likely get it with a sensible effort. (You could
fine-tune by also looking at the *Filter* and *SubFilter* but the improvement
would be marginal.)
> Encrypted string not decrypted
> ------------------------------
>
> Key: PDFBOX-4453
> URL: https://issues.apache.org/jira/browse/PDFBOX-4453
> Project: PDFBox
> Issue Type: Bug
> Components: Crypto
> Affects Versions: 1.8.16, 2.0.13
> Reporter: Tilman Hausherr
> Assignee: Tilman Hausherr
> Priority: Critical
> Fix For: 1.8.17, 2.0.14, 3.0.0 PDFBox
>
> Attachments: 2AF-0088-NA-LMF35-40-01-2019-01-18-14-25-52(1).pdf
>
>
> In the attached file, an ancrypted string "0" should be decrypted to "3" but
> it is not.
> * It is RC4 40 bit encryption
> * The string is not decrypted because it is skipped because it is in the
> objects HashSet
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
