Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-01-26 | Bug fix: handle ColorSpace lookup for inline images (fixes #392) | Jay Berkenbilt | |
If the value of /CS in the inline image dictionary was is key in the page's /Resource -> /ColorSpace dictionary, properly resolve it by referencing the proper colorspace, and not just the name, in the external image dictionary. | |||
2020-01-15 | Fix for Windows unable to acquire crypt context with new keyset (fixes #387) | Cloudmersive | |
Fix is based on guidance https://support.microsoft.com/en-us/help/238187/cryptacquirecontext-use-and-troubleshooting and is the proper fix for #285/#286 | |||
2020-01-14 | Pull wmain -> main code from qpdf.cc into QUtil.cc | Jay Berkenbilt | |
2020-01-14 | Add error detection for read_lines_from_file(FILE*) | Jay Berkenbilt | |
2020-01-13 | QUtil::read_lines_from_file: optional EOL preservation | Jay Berkenbilt | |
2020-01-13 | Refactor QUtil::read_lines_from_file | Jay Berkenbilt | |
This commit adds the preserve_eol flags but doesn't implement EOL preservation yet. | |||
2019-11-17 | Prepare 9.1.0 releaserelease-qpdf-9.1.0 | Jay Berkenbilt | |
2019-11-10 | Prepare 9.1.rc1 release | Jay Berkenbilt | |
2019-11-09 | Allow odd/even modifiers in numeric range (fixes #364) | Jay Berkenbilt | |
2019-11-09 | Allow /P in encryption dictionary to be positive (fixes #382) | Jay Berkenbilt | |
Even though this is disallowed by the spec, files like this have been encountered in the wild. | |||
2019-11-09 | Allow runtime inspection/override of crypto provider | Jay Berkenbilt | |
2019-11-09 | Implement gnutls crypto provider (fixes #218) | Jay Berkenbilt | |
Thanks to Zdenek Dohnal <zdohnal@redhat.com> for contributing the code used for the gnutls crypto provider. | |||
2019-11-09 | Update autoconf to support crypto selection | Jay Berkenbilt | |
2019-11-09 | Fix typos in configure.ac | Jay Berkenbilt | |
2019-11-09 | Isolate source files used for native crypto | Jay Berkenbilt | |
2019-11-09 | AES_PDF: move CBC logic from pipeline to AES_PDF implementation | Jay Berkenbilt | |
2019-11-09 | AES_PDF: switch to pluggable crypto | Jay Berkenbilt | |
2019-11-09 | SHA2: switch to pluggable crypto | Jay Berkenbilt | |
2019-11-09 | Rename SHA2 implementation (non-bisectable) | Jay Berkenbilt | |
2019-11-09 | RC4: switch to pluggable crypto | Jay Berkenbilt | |
2019-11-09 | Rename RC4 implementation (non-bisectable) | Jay Berkenbilt | |
2019-11-09 | MD5: switch to pluggable crypto | Jay Berkenbilt | |
2019-11-09 | Rename MD5 implementation (non-bisectable) | Jay Berkenbilt | |
Just rename MD5 -> MD5_native in place so that git annotate will show the lines as having originated there. | |||
2019-11-09 | QPDFCryptoProvider: initial implementation | Jay Berkenbilt | |
2019-11-09 | Remove int type checks -- subsumed by C++-11 | Jay Berkenbilt | |
2019-11-09 | Require C++-11 | Jay Berkenbilt | |
Includes updates to m4/ax_cxx_compile_stdcxx.m4 to make it work with msvc, which supports C++-11 with no flags but doesn't set __cplusplus to a recent value. | |||
2019-11-04 | Fix two additional fuzz test cases | Jay Berkenbilt | |
2019-10-22 | Parse Contents in signature dictionary without encryption | Masamichi 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-22 | Add QPDFObject::getParsedOffset() | Masamichi Hosoda | |
2019-10-22 | Add QPDFWriter::getWrittenXRefTable() | Masamichi Hosoda | |
2019-10-22 | Add QPDFWriter::getRenumberedObjGen() | Masamichi Hosoda | |
2019-10-22 | Add QPDF::getXRefTable() | Masamichi Hosoda | |
2019-10-22 | Exclude signature dictionary from compressible objects | Masamichi 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-22 | Fix /Contents value representation in a signature dictionary | Masamichi 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-13 | Prepare 9.0.2 releaserelease-qpdf-9.0.2 | Jay Berkenbilt | |
2019-09-20 | Prepare 9.0.1 release | Jay Berkenbilt | |
2019-09-20 | Correct reversed Rectangle coordinates (fixes #363) | Jay Berkenbilt | |
2019-09-20 | Fix typo in comment | Jay Berkenbilt | |
2019-09-20 | Warn for duplicated dictionary keys (fixes #345) | Jay Berkenbilt | |
2019-09-18 | Fix fuzz issue 16953 (overflow checking in xref stream index) | Jay Berkenbilt | |
2019-09-18 | Fix integer type warnings for big-endian systems | Jay Berkenbilt | |
2019-09-01 | Prepare 9.0.0 releaserelease-qpdf-9.0.0 | Jay Berkenbilt | |
2019-08-31 | Add methods QPDF::anyWarnings and QPDF::closeInputSource | Jay Berkenbilt | |
2019-08-31 | Add remove_file and rename_file to QUtil | Jay Berkenbilt | |
2019-08-29 | Don't encrypt trailer, fixes fuzz issue 15983 | Jay 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-28 | Detect stream in object stream, fixing fuzz 16214 | Jay 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-28 | Make popping pipeline stack safer | Jay Berkenbilt | |
Use destructors to pop the pipeline stack, and ensure that code that pops the stack is actually popping the intended thing. | |||
2019-08-28 | Fix fuzz issues 15316 and 15390 | Jay Berkenbilt | |
2019-08-27 | Fix fuzz issue 16172 (overflow checking in OffsetInputSource) | Jay Berkenbilt | |
2019-08-27 | Fix fuzz issue 15442 (overflow checking in BufferInputSource) | Jay Berkenbilt | |