aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2018-04-16 00:45:11 +0200
committerJay Berkenbilt <ejb@ql.org>2018-04-16 00:45:11 +0200
commit55b1d3ef16338cb16871365c4752b07ff8d75572 (patch)
treeaf6ce055843941d343451e8bc7adbab555c61226 /TODO
parentb4d6cf6836ce025ba1811b7bbec52680c7204223 (diff)
downloadqpdf-55b1d3ef16338cb16871365c4752b07ff8d75572.tar.zst
TODO
Diffstat (limited to 'TODO')
-rw-r--r--TODO9
1 files changed, 9 insertions, 0 deletions
diff --git a/TODO b/TODO
index 03c784a8..8404ea35 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,8 @@
Soon
====
+ * libtests buffer test fails with address sanitizer.
+
* Figure out how to render Gajić correctly in the PDF version of the
qpdf manual.
@@ -62,6 +64,13 @@ directory or that are otherwise not publicly accessible. This includes
things sent to me by email that are specifically not public. Even so,
I find it useful to make reference to them in this list
+ * Some test cases on bad fails fail because qpdf is unable to find
+ the root dictionary when it fails to read the trailer. Recovery
+ could find the root dictionary and even the info dictionary in
+ other ways. In particular, issue-202.pdf can be opened by evince,
+ and there's no real reason that qpdf couldn't be made to be able to
+ recover that file as well.
+
* Audit every place where qpdf allocates memory to see whether there
are cases where malicious inputs could cause qpdf to attempt to
grab very large amounts of memory. Certainly there are cases like