Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-11-09 | Allow runtime inspection/override of crypto provider | Jay Berkenbilt | |
2019-11-09 | Increase coverage for RC4 testing | Jay Berkenbilt | |
2019-11-09 | Explicitly use only native crypto for oss-fuzz | Jay Berkenbilt | |
I don't need qpdf's fuzz to find leaks and invalid memory in gnutls. | |||
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 | Local dev: use --std=c++11 explicitly | Jay Berkenbilt | |
Since g++ (as of this writing) uses c++14 by default, this prevents me from accidentally using c++14 features. | |||
2019-11-09 | Remove int type checks -- subsumed by C++-11 | Jay Berkenbilt | |
2019-11-09 | See if C++11 features work | 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 | Add stock ax_cxx_compile_stdcxx.m4 from autoconf-archive | Jay Berkenbilt | |
2019-11-04 | Fix two additional fuzz test cases | Jay Berkenbilt | |
2019-11-04 | Update list of ignored fuzzer tests | Jay Berkenbilt | |
Removed ones that were fixed upstream, and added a new one, all from the jpeg library. | |||
2019-10-22 | Add ChangeLog and documentation for signature dict enhancements | 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-10-13 | Update fuzz errors in TODO | Jay Berkenbilt | |
2019-10-13 | Make --replace-input work with / in path (fixes #365) | Jay Berkenbilt | |
2019-09-20 | Fix 9.0.1 version numberrelease-qpdf-9.0.1 | Jay Berkenbilt | |
2019-09-20 | Prepare 9.0.1 release | Jay Berkenbilt | |
2019-09-20 | Update release notes for upcoming 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 | Remove reference to automatically closed fuzz issue | 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-17 | Don't assume char is signed in int conversion tests (fixes #361) | Jay Berkenbilt | |
2019-09-01 | Fix duplicated release notes entries | Jay Berkenbilt | |
2019-09-01 | Prepare 9.0.0 releaserelease-qpdf-9.0.0 | Jay Berkenbilt | |
2019-08-31 | spell check | Jay Berkenbilt | |
2019-08-31 | Add --replace-input option (fixes #321) | Jay Berkenbilt | |
2019-08-31 | Add methods QPDF::anyWarnings and QPDF::closeInputSource | Jay Berkenbilt | |
2019-08-31 | refactor: split write_outfile and do_split_pages | Jay Berkenbilt | |