octoleo/qpdf
2
1
Fork 0
mirror of https://github.com/qpdf/qpdf.git synced 2024-12-31 14:01:59 +00:00
Code Issues Releases Wiki Activity

Spell check

Browse Source
This commit is contained in:
Jay Berkenbilt 2022-05-01 11:48:41 -04:00
parent 04118ca44b
commit e34dbbfa18
5 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TODO
View File

@ -39,6 +39,8 @@ Soon: Break ground on "Document-level work"
Output JSON v2 Output JSON v2
============== ==============
Remember typo: search for "Typo" In QPDFJob::doJSONEncrypt.
Output JSON v2 will contain enough information to completely recreate Output JSON v2 will contain enough information to completely recreate
a PDF file. In other words, qpdf will have full, bidirectional, a PDF file. In other words, qpdf will have full, bidirectional,
lossless json serialization/deserialization of PDF. lossless json serialization/deserialization of PDF.

2
cSpell.json
View File

@ -267,7 +267,6 @@
"mkinstalldirs", "mkinstalldirs",
"mklink", "mklink",
"moddate", "moddate",
"moddifyannotations",
"monoseq", "monoseq",
"msvc", "msvc",
"msvcrt", "msvcrt",
@ -507,6 +506,7 @@
"unconflicting", "unconflicting",
"underlaying", "underlaying",
"unencrypted", "unencrypted",
"unexport",
"unfilterable", "unfilterable",
"unparse", "unparse",
"unpickling", "unpickling",

2
include/qpdf/DLL.h
View File

@ -63,7 +63,7 @@ for a more in-depth discussion.
* A class's runtime type information is need if the class is going to * A class's runtime type information is need if the class is going to
be used as an exception, inherited from, or tested with be used as an exception, inherited from, or tested with
dynamic_claass. To do these things across a shared object boundary, dynamic_class. To do these things across a shared object boundary,
runtime type information must be exported. runtime type information must be exported.
* On Windows: * On Windows:

2
libqpdf/QPDFJob.cc
View File

@ -1335,6 +1335,8 @@ QPDFJob::doJSONEncrypt(QPDF& pdf, JSON& j)
"modifyassembly", JSON::makeBool(pdf.allowModifyAssembly())); "modifyassembly", JSON::makeBool(pdf.allowModifyAssembly()));
j_capabilities.addDictionaryMember( j_capabilities.addDictionaryMember(
"modifyforms", JSON::makeBool(pdf.allowModifyForm())); "modifyforms", JSON::makeBool(pdf.allowModifyForm()));
// Typo will be fixed for json v2
/* cSpell:ignore moddifyannotations */
j_capabilities.addDictionaryMember( j_capabilities.addDictionaryMember(
"moddifyannotations", JSON::makeBool(pdf.allowModifyAnnotation())); "moddifyannotations", JSON::makeBool(pdf.allowModifyAnnotation()));
j_capabilities.addDictionaryMember( j_capabilities.addDictionaryMember(

6
manual/weak-crypto.rst
View File

@ -32,7 +32,7 @@ hash or two documents with the same hash.
When we say that an encryption algorithm is weak, we either mean that When we say that an encryption algorithm is weak, we either mean that
a mathematical flaw has been discovered that makes it inherently a mathematical flaw has been discovered that makes it inherently
crackable or that it is sufficiently simple that modern computer insecure or that it is sufficiently simple that modern computer
technology makes it possible to use "brute force" to crack. For technology makes it possible to use "brute force" to crack. For
example, when 40-bit keys were originally introduced, it wasn't example, when 40-bit keys were originally introduced, it wasn't
practical to consider trying all possible keys, but today such a thing practical to consider trying all possible keys, but today such a thing
@ -50,7 +50,7 @@ other words, you can't use a weak hash as a digital signature. There
is no harm, however, in using a weak hash as a way to sort or index is no harm, however, in using a weak hash as a way to sort or index
documents as long as hash collisions are tolerated. It is also common documents as long as hash collisions are tolerated. It is also common
to use weak hashes as checksums, which are often used a check that a to use weak hashes as checksums, which are often used a check that a
file wasn't damanged in transit or storage, though for true integrity, file wasn't damaged in transit or storage, though for true integrity,
a strong hash would be better. a strong hash would be better.
Note that qpdf must always retain support for weak cryptographic Note that qpdf must always retain support for weak cryptographic
@ -138,7 +138,7 @@ MD5 is used in the following non-security-sensitive ways:
It is therefore not possible completely avoid the use of MD5 with It is therefore not possible completely avoid the use of MD5 with
qpdf, but as long as you are using 256-bit encryption, it is not used qpdf, but as long as you are using 256-bit encryption, it is not used
in a securty-sensitive fashion. in a security-sensitive fashion.
.. _breaking-crypto-api: .. _breaking-crypto-api: