diff options
author | Jay Berkenbilt <ejb@ql.org> | 2009-10-17 05:14:47 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2009-10-17 05:14:47 +0200 |
commit | 846c9f6bcc9aa86067850088808ff8d724a0d18f (patch) | |
tree | 587f6ff5589ebaefad50ca9f1b1b7fa81736a119 /TODO | |
parent | ad19b03fd346e6779a029c43b6228e377919852f (diff) | |
download | qpdf-846c9f6bcc9aa86067850088808ff8d724a0d18f.tar.zst |
checkpoint -- started doing some R4 encryption support
git-svn-id: svn+q:///qpdf/trunk@807 71b93d88-0707-0410-a8cf-f5a4172ac649
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -56,6 +56,18 @@ dictionary. (V = 4 is Crypt Filters.) See ~/Q/pdf-collection/R4-encrypt-PDF_Inside_and_Out.pdf + Search for XXX in the code. Implementation has been started. + + Algorithms from PDF Spec in QPDF_encrypt.cc have been updated. We + can at least properly verify the user password with an R4 file. In + order to finish the job, we need an aes-128-cbc implementation. + Then we can fill in the gaps for the aes pipeline and actually run + the test suite. The pipeline may be able to hard-code the + initialization vector stuff by taking the first block of input and + by writing a random block for output. The padding is already in + the code, but the initialization vector is not since I accidentally + started using an aes256 implementation instead of aes128-cbc. + * Look at page splitting. |