diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2012-11-20 19:15:14 +0100 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2012-11-20 19:57:37 +0100 |
| commit | f256670eba636a9b8344987108110e7b1b4c0a46 (patch) | |
| tree | da0cc0248dfc71cf2de5c76a60f99b9918d5c2d1 /TODO | |
| parent | 041397fdabde66574824db7582a26ef1e3fbfc65 (diff) | |
| download | qpdf-f256670eba636a9b8344987108110e7b1b4c0a46.tar.zst | |
Ignore objects with offset 0
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 31 |
1 files changed, 25 insertions, 6 deletions
@@ -1,12 +1,31 @@ General ======= - * See if I can support the encryption format used with /R 5 /V 5, - even though a qpdf-announce subscriber with an adobe.com email - address mentioned that this is deprecated. There is also a new - encryption format coming in a future release, which may be better - to support. As of the qpdf 3.0 release, the specification was not - publicly available yet. + * See if I can support the encryption format used with /R 5 /V 5 + (AESV3), even though a qpdf-announce subscriber with an adobe.com + email address mentioned that this is deprecated. There is also a + new encryption format coming in a future release (PDF 2.0), which + may be better to support. As of the qpdf 3.0 release, the + specification was not publicly available yet. + + AESV3 encryption is supported with PDF 1.7 extension level 3 and is + being deprecated, but there are plenty of files out there. The + encryption format is decribed in adobe_supplement_iso32000.pdf. + Such a file must specify that it uses these extensions in its + document catalog: + + << + /Type /Catalog + /Extensions << + /ADBE << + /BaseVersion /1.7 + /ExtensionLevel 3 + >> + >> + >> + + Possible sha256 implementations: http://sol-biotech.com/code/sha2/, + http://hashlib2plus.sourceforge.net/ * Consider the possibility of doing something locale-aware to support non-ASCII passwords. Update documentation if this is done. |