[
https://issues.apache.org/jira/browse/PDFBOX-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964842#action_12964842
]
Adam Nichols commented on PDFBOX-907:
-------------------------------------
I think AES encryption support was added by PDFBOX-872. If the IV is random,
then it also has to be included in plaintext or it wouldn't be possible to
decrypt the first block. I think you might mean the salt (See 7.6.2, page 58,
PDF 32000-1:2008). If there's anything further which needs added for AES,
please let me know.
> Encrypted Key not correctly calculated when the meta data is not encrypted
> --------------------------------------------------------------------------
>
> Key: PDFBOX-907
> URL: https://issues.apache.org/jira/browse/PDFBOX-907
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 1.3.1
> Reporter: Martijn Brinkers
> Attachments: MBTA_Review_2009.pdf, PDFBOX-907.patch
>
>
> Since rev 4, meta data can be unencrypted while the data is encrypted. If the
> metadata is not encrypted 0xFFFFFFFF should be added to the hash:
> "Security handlers of revision 4 or greater) If document metadata is not
> being encrypted, pass 4 bytes with
> the value 0xFFFFFFFF to the MD5 hash function."
> (see see 7.6.3.3 Algorithm 2 Step f of PDF 32000-1:2008)
> Whether or not the metadata is encrypted is store in the encryption
> dictionary. The default value is to encrypt the meta data.
> I will attach a patch to detect whether the meta data is encrypted, and if
> not 0xFFFFFFFF will be added.
> The document that I have tested with can be downloaded from
> http://www.mbtareview.com/MBTA_Review_2009.pdf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
