[
https://issues.apache.org/jira/browse/PDFBOX-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207003#comment-14207003
]
Tilman Hausherr commented on PDFBOX-2456:
-----------------------------------------
I haven't done anything about the setAllSecurityToBeRemoved() problem myself
because I don't really understand how it should be used in a "bug free world".
What is the intended behaviour? Is it OK that I don't have to call it when I
use the old parser? Is it OK that I must call it when I use the new parser? And
if an encrypted PDF is opened, decrypted, changed and saved as encrypted, does
one have to call "protect" or not?
> create TestSymmetricKeyEncryption.java
> --------------------------------------
>
> Key: PDFBOX-2456
> URL: https://issues.apache.org/jira/browse/PDFBOX-2456
> Project: PDFBox
> Issue Type: Improvement
> Components: Utilities
> Affects Versions: 1.8.7, 1.8.8, 2.0.0
> Environment: java7 debian7
> Reporter: Ralf Hauser
> Labels: AES256
> Fix For: 1.8.8, 2.0.0
>
> Attachments: AES256.diff, TestSymmetricKeyEncryption.java,
> enc128bit_20141025_115145.pdf, enc256bit_20141025_105451.pdf,
> preEnc_20141025_105451.pdf, preEnc_20141025_115145.pdf
>
>
> similarly to org.apache.pdfbox.encryption.TestPublicKeyEncryption, also test
> password based encryption
> 1) 128bit
> 2) 256bit AES PDFBOX-1594
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
