aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2019-11-09Allow /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-09Start list of ABI changes for qpdf 10Jay Berkenbilt
2019-11-09Update release notes for crypto providersJay Berkenbilt
2019-11-09Update docs for crypto providersJay Berkenbilt
2019-11-09Run all crypto providers in CI for Linux and sanitizer buildsJay Berkenbilt
2019-11-09Run libtests for crypto with all available providersJay Berkenbilt
If QPDF_CRYPTO_PROVIDER is set, just run the tests for the given provider. This is to support cases of running the entire test suite for each provider. If QPDF_CRYPTO_PROVIDER is not set, run the tests that exercise the cyrpto provider for each available provider.
2019-11-09Allow runtime inspection/override of crypto providerJay Berkenbilt
2019-11-09Increase coverage for RC4 testingJay Berkenbilt
2019-11-09Explicitly use only native crypto for oss-fuzzJay Berkenbilt
I don't need qpdf's fuzz to find leaks and invalid memory in gnutls.
2019-11-09Implement 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-09Update autoconf to support crypto selectionJay Berkenbilt
2019-11-09Fix typos in configure.acJay Berkenbilt
2019-11-09Isolate source files used for native cryptoJay Berkenbilt
2019-11-09AES_PDF: move CBC logic from pipeline to AES_PDF implementationJay Berkenbilt
2019-11-09AES_PDF: switch to pluggable cryptoJay Berkenbilt
2019-11-09SHA2: switch to pluggable cryptoJay Berkenbilt
2019-11-09Rename SHA2 implementation (non-bisectable)Jay Berkenbilt
2019-11-09RC4: switch to pluggable cryptoJay Berkenbilt
2019-11-09Rename RC4 implementation (non-bisectable)Jay Berkenbilt
2019-11-09MD5: switch to pluggable cryptoJay Berkenbilt
2019-11-09Rename 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-09QPDFCryptoProvider: initial implementationJay Berkenbilt
2019-11-09Local dev: use --std=c++11 explicitlyJay Berkenbilt
Since g++ (as of this writing) uses c++14 by default, this prevents me from accidentally using c++14 features.
2019-11-09Remove int type checks -- subsumed by C++-11Jay Berkenbilt
2019-11-09See if C++11 features workJay Berkenbilt
2019-11-09Require C++-11Jay 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-04Add stock ax_cxx_compile_stdcxx.m4 from autoconf-archiveJay Berkenbilt
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