pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tilman Hausherr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PDFBOX-2471) AES encryption failing to write Acroform field names and values
Date Sat, 01 Nov 2014 06:35:33 GMT

    [ https://issues.apache.org/jira/browse/PDFBOX-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192989#comment-14192989

Tilman Hausherr commented on PDFBOX-2471:

Yes we have a problem with AES256, which is apparently JDK related. This was discovered while
working on PDFBOX-2456. So you help is most welcome, if successful. Your patch doesn't help
on my local system, sadly. Please do this whether it works for you:
- open the file org.apache.pdfbox.encryption.TestSymmetricKeyEncryption.java in the tests
- in the source code replace "test.pdf" with "Acroform-PDFBOX-2333.pdf"
- in the source code, look for testProtection() and activate this segment that is commented
        document = PDDocument.load(new ByteArrayInputStream(inputFileAsByteArray));
        testSymmEncrForKeySize(256, sizePriorToEncryption, document, PASSWORD, permission1);
- run the test with your patch (and if this is my lucky day, improve your patch :-) so that
it passes the test)

> AES encryption failing to write Acroform field names and values
> ---------------------------------------------------------------
>                 Key: PDFBOX-2471
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2471
>             Project: PDFBox
>          Issue Type: Bug
>          Components: AcroForm, Writing
>    Affects Versions: 2.0.0
>            Reporter: Stephen Hendrix
>         Attachments: PDFBOX-2471_Fix__AES_256_bit_encryption_of_COSString.diff
> When writing a PDF using AES 256 bit encryption, the field names / values from the Acroform
are not being persisted correctly. If I encrypt using RC4 128 bit, they are persisted correctly.
I am using snapshot pdfbox:2.0.0-20141023.180319-636.
> I dug into this, and it looks to me the problem is with COSWriter.visitFromString, which
invokes  SecurityHandler.decryptString (there is no SecurityHandler.encryptString).

This message was sent by Atlassian JIRA

View raw message