diff options
author | Jay Berkenbilt <ejb@ql.org> | 2012-12-31 15:27:02 +0100 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2012-12-31 16:32:32 +0100 |
commit | 06c5bac96c9d18d8336a65e2ad6f8283530514c2 (patch) | |
tree | 86d686a0e42715e5a18983c5989c8361b0ac6ecc | |
parent | f8306913ba6eb751cd7f408d04f2d65d8cd3b341 (diff) | |
download | qpdf-06c5bac96c9d18d8336a65e2ad6f8283530514c2.tar.zst |
Clarify TODO note about crypt filters
-rw-r--r-- | TODO | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -79,13 +79,14 @@ Index: QPDFWriter.cc * The description of Crypt filters is unclear with respect to how to use them to override /StmF for specific streams. I'm not sure whether qpdf will do the right thing for any specific individual - streams that might have crypt filters. The specification seems to - imply that only embedded file streams and metadata streams can have - crypt filters, and there are already special cases in the code to - handle those. Most likely, it won't be a problem, but someday - someone may find a file that qpdf doesn't work on because of crypt - filters. There is an example in the spec of using a crypt filter - on a metadata stream. + streams that might have crypt filters, but I believe it does based + on my testing of a limited subset. The specification seems to imply + that only embedded file streams and metadata streams can have crypt + filters, and there are already special cases in the code to handle + those. Most likely, it won't be a problem, but someday someone may + find a file that qpdf doesn't work on because of crypt filters. + There is an example in the spec of using a crypt filter on a + metadata stream. For now, we notice /Crypt filters and decode parameters consistent with the example in the PDF specification, and the right thing |