aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2019-11-04Fix two additional fuzz test casesJay Berkenbilt
2019-11-04Update list of ignored fuzzer testsJay Berkenbilt
Removed ones that were fixed upstream, and added a new one, all from the jpeg library.
2019-10-22Add ChangeLog and documentation for signature dict enhancementsJay Berkenbilt
2019-10-22Parse Contents in signature dictionary without encryptionMasamichi Hosoda
Various PDF digital signing tools do not encrypt /Contents value in signature dictionary. Adobe Acrobat Reader DC can handle a PDF with the /Contents value not encrypted. Write Contents in signature dictionary without encryption Tests ensure that string /Contents are not handled specially when not found in sig dicts.
2019-10-22Add QPDFObject::getParsedOffset()Masamichi Hosoda
2019-10-22Add QPDFWriter::getWrittenXRefTable()Masamichi Hosoda
2019-10-22Add QPDFWriter::getRenumberedObjGen()Masamichi Hosoda
2019-10-22Add QPDF::getXRefTable()Masamichi Hosoda
2019-10-22Exclude signature dictionary from compressible objectsMasamichi Hosoda
It seems better not to compress signature dictionaries. Various PDF digital signing tools, including Adobe Acrobat Reader DC, do not compress signature dictionaries. Table 8.93 "Entries in a signature dictionary" in PDF 1.5 reference describes that /ByteRange in the signature dictionary shall be used to describe a digest that does not include the signature value (/Contents) itself. The byte ranges cannot be determined if the dictionary is compressed.
2019-10-22Fix /Contents value representation in a signature dictionaryMasamichi Hosoda
Table 8.93 "Entries in a signature dictionary" in PDF 1.5 reference describes that the value of Contents entry is a hexadecimal string representation when ByteRange is specified. This commit makes QPDF always uses hexadecimal strings representation instead of literal strings for it.
2019-10-13Prepare 9.0.2 releaserelease-qpdf-9.0.2Jay Berkenbilt
2019-10-13Update fuzz errors in TODOJay Berkenbilt
2019-10-13Make --replace-input work with / in path (fixes #365)Jay Berkenbilt
2019-09-20Fix 9.0.1 version numberrelease-qpdf-9.0.1Jay Berkenbilt
2019-09-20Prepare 9.0.1 releaseJay Berkenbilt
2019-09-20Update release notes for upcoming 9.0.1 releaseJay Berkenbilt
2019-09-20Correct reversed Rectangle coordinates (fixes #363)Jay Berkenbilt
2019-09-20Fix typo in commentJay Berkenbilt
2019-09-20Warn for duplicated dictionary keys (fixes #345)Jay Berkenbilt
2019-09-18Remove reference to automatically closed fuzz issueJay Berkenbilt
2019-09-18Fix fuzz issue 16953 (overflow checking in xref stream index)Jay Berkenbilt
2019-09-18Fix integer type warnings for big-endian systemsJay Berkenbilt
2019-09-17Don't assume char is signed in int conversion tests (fixes #361)Jay Berkenbilt
2019-09-01Fix duplicated release notes entriesJay Berkenbilt
2019-09-01Prepare 9.0.0 releaserelease-qpdf-9.0.0Jay Berkenbilt
2019-08-31spell checkJay Berkenbilt
2019-08-31Add --replace-input option (fixes #321)Jay Berkenbilt
2019-08-31Add methods QPDF::anyWarnings and QPDF::closeInputSourceJay Berkenbilt
2019-08-31refactor: split write_outfile and do_split_pagesJay Berkenbilt
2019-08-31Change release notes orderJay Berkenbilt
2019-08-31Add remove_file and rename_file to QUtilJay Berkenbilt
2019-08-31Update release preparation instructionsJay Berkenbilt
2019-08-31Remove stray TODO commentJay Berkenbilt
2019-08-31spell checkJay Berkenbilt
2019-08-31Update C++-11 notesJay Berkenbilt
2019-08-30Notes about C++-11 for qpdf 10Jay Berkenbilt
2019-08-30Add getRefcount to PointerHolder testJay Berkenbilt
2019-08-30Update Windows image and compilerJay Berkenbilt
2019-08-30Exclude emacs backups in autogen.shJay Berkenbilt
2019-08-29TODO: update notes on ignored fuzz casesJay Berkenbilt
2019-08-29Don't encrypt trailer, fixes fuzz issue 15983Jay Berkenbilt
Ordinarily the trailer doesn't contain any strings, so this is usually a non-issue, but if the trailer contains strings, linearizing and encrypting with object streams would include encrypted strings in the trailer, which would blow out the padding because encrypted strings are longer than their cleartext counterparts.
2019-08-29More fuzzer notesJay Berkenbilt
2019-08-28Detect stream in object stream, fixing fuzz 16214Jay Berkenbilt
It's detected in QPDFWriter instead of at parse time because I can't figure out how to construct a test case in a reasonable time. This commit moves the fuzz file into the regular test suite for a QTC coverage case.
2019-08-28Safe pipeline pop fixed fuzz issue 15445Jay Berkenbilt
2019-08-28Make popping pipeline stack saferJay Berkenbilt
Use destructors to pop the pipeline stack, and ensure that code that pops the stack is actually popping the intended thing.
2019-08-28Fix fuzz issues 15316 and 15390Jay Berkenbilt
2019-08-27Fix fuzz issue 16172 (overflow checking in OffsetInputSource)Jay Berkenbilt
2019-08-27Fix fuzz issue 15442 (overflow checking in BufferInputSource)Jay Berkenbilt
2019-08-27Seek in two stages to avoid overflowJay Berkenbilt
When seeing to a position based on a value read from the input, we are prone to integer overflow (fuzz issue 15442). Seek in two stages to move the overflow check into the input source code.
2019-08-27Fix fuzz issue 15387 (overflow checking xref size)Jay Berkenbilt