Commit 55b1d3ef16338cb16871365c4752b07ff8d75572
1 parent
b4d6cf68
TODO
Showing
1 changed file
with
9 additions
and
0 deletions
TODO
| 1 | Soon | 1 | Soon |
| 2 | ==== | 2 | ==== |
| 3 | 3 | ||
| 4 | + * libtests buffer test fails with address sanitizer. | ||
| 5 | + | ||
| 4 | * Figure out how to render Gajić correctly in the PDF version of the | 6 | * Figure out how to render Gajić correctly in the PDF version of the |
| 5 | qpdf manual. | 7 | qpdf manual. |
| 6 | 8 | ||
| @@ -62,6 +64,13 @@ directory or that are otherwise not publicly accessible. This includes | @@ -62,6 +64,13 @@ directory or that are otherwise not publicly accessible. This includes | ||
| 62 | things sent to me by email that are specifically not public. Even so, | 64 | things sent to me by email that are specifically not public. Even so, |
| 63 | I find it useful to make reference to them in this list | 65 | I find it useful to make reference to them in this list |
| 64 | 66 | ||
| 67 | + * Some test cases on bad fails fail because qpdf is unable to find | ||
| 68 | + the root dictionary when it fails to read the trailer. Recovery | ||
| 69 | + could find the root dictionary and even the info dictionary in | ||
| 70 | + other ways. In particular, issue-202.pdf can be opened by evince, | ||
| 71 | + and there's no real reason that qpdf couldn't be made to be able to | ||
| 72 | + recover that file as well. | ||
| 73 | + | ||
| 65 | * Audit every place where qpdf allocates memory to see whether there | 74 | * Audit every place where qpdf allocates memory to see whether there |
| 66 | are cases where malicious inputs could cause qpdf to attempt to | 75 | are cases where malicious inputs could cause qpdf to attempt to |
| 67 | grab very large amounts of memory. Certainly there are cases like | 76 | grab very large amounts of memory. Certainly there are cases like |