Commit e34dbbfa18ab4753f9637920719e683ba3037fcf

Authored by Jay Berkenbilt
1 parent 04118ca4

Spell check

@@ -39,6 +39,8 @@ Soon: Break ground on "Document-level work" @@ -39,6 +39,8 @@ Soon: Break ground on "Document-level work"
39 Output JSON v2 39 Output JSON v2
40 ============== 40 ==============
41 41
  42 +Remember typo: search for "Typo" In QPDFJob::doJSONEncrypt.
  43 +
42 Output JSON v2 will contain enough information to completely recreate 44 Output JSON v2 will contain enough information to completely recreate
43 a PDF file. In other words, qpdf will have full, bidirectional, 45 a PDF file. In other words, qpdf will have full, bidirectional,
44 lossless json serialization/deserialization of PDF. 46 lossless json serialization/deserialization of PDF.
cSpell.json
@@ -267,7 +267,6 @@ @@ -267,7 +267,6 @@
267 "mkinstalldirs", 267 "mkinstalldirs",
268 "mklink", 268 "mklink",
269 "moddate", 269 "moddate",
270 - "moddifyannotations",  
271 "monoseq", 270 "monoseq",
272 "msvc", 271 "msvc",
273 "msvcrt", 272 "msvcrt",
@@ -507,6 +506,7 @@ @@ -507,6 +506,7 @@
507 "unconflicting", 506 "unconflicting",
508 "underlaying", 507 "underlaying",
509 "unencrypted", 508 "unencrypted",
  509 + "unexport",
510 "unfilterable", 510 "unfilterable",
511 "unparse", 511 "unparse",
512 "unpickling", 512 "unpickling",
include/qpdf/DLL.h
@@ -63,7 +63,7 @@ for a more in-depth discussion. @@ -63,7 +63,7 @@ for a more in-depth discussion.
63 63
64 * A class's runtime type information is need if the class is going to 64 * A class's runtime type information is need if the class is going to
65 be used as an exception, inherited from, or tested with 65 be used as an exception, inherited from, or tested with
66 - dynamic_claass. To do these things across a shared object boundary, 66 + dynamic_class. To do these things across a shared object boundary,
67 runtime type information must be exported. 67 runtime type information must be exported.
68 68
69 * On Windows: 69 * On Windows:
libqpdf/QPDFJob.cc
@@ -1335,6 +1335,8 @@ QPDFJob::doJSONEncrypt(QPDF& pdf, JSON& j) @@ -1335,6 +1335,8 @@ QPDFJob::doJSONEncrypt(QPDF& pdf, JSON& j)
1335 "modifyassembly", JSON::makeBool(pdf.allowModifyAssembly())); 1335 "modifyassembly", JSON::makeBool(pdf.allowModifyAssembly()));
1336 j_capabilities.addDictionaryMember( 1336 j_capabilities.addDictionaryMember(
1337 "modifyforms", JSON::makeBool(pdf.allowModifyForm())); 1337 "modifyforms", JSON::makeBool(pdf.allowModifyForm()));
  1338 + // Typo will be fixed for json v2
  1339 + /* cSpell:ignore moddifyannotations */
1338 j_capabilities.addDictionaryMember( 1340 j_capabilities.addDictionaryMember(
1339 "moddifyannotations", JSON::makeBool(pdf.allowModifyAnnotation())); 1341 "moddifyannotations", JSON::makeBool(pdf.allowModifyAnnotation()));
1340 j_capabilities.addDictionaryMember( 1342 j_capabilities.addDictionaryMember(
manual/weak-crypto.rst
@@ -32,7 +32,7 @@ hash or two documents with the same hash. @@ -32,7 +32,7 @@ hash or two documents with the same hash.
32 32
33 When we say that an encryption algorithm is weak, we either mean that 33 When we say that an encryption algorithm is weak, we either mean that
34 a mathematical flaw has been discovered that makes it inherently 34 a mathematical flaw has been discovered that makes it inherently
35 -crackable or that it is sufficiently simple that modern computer 35 +insecure or that it is sufficiently simple that modern computer
36 technology makes it possible to use "brute force" to crack. For 36 technology makes it possible to use "brute force" to crack. For
37 example, when 40-bit keys were originally introduced, it wasn't 37 example, when 40-bit keys were originally introduced, it wasn't
38 practical to consider trying all possible keys, but today such a thing 38 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 @@ -50,7 +50,7 @@ other words, you can't use a weak hash as a digital signature. There
50 is no harm, however, in using a weak hash as a way to sort or index 50 is no harm, however, in using a weak hash as a way to sort or index
51 documents as long as hash collisions are tolerated. It is also common 51 documents as long as hash collisions are tolerated. It is also common
52 to use weak hashes as checksums, which are often used a check that a 52 to use weak hashes as checksums, which are often used a check that a
53 -file wasn't damanged in transit or storage, though for true integrity, 53 +file wasn't damaged in transit or storage, though for true integrity,
54 a strong hash would be better. 54 a strong hash would be better.
55 55
56 Note that qpdf must always retain support for weak cryptographic 56 Note that qpdf must always retain support for weak cryptographic
@@ -138,7 +138,7 @@ MD5 is used in the following non-security-sensitive ways: @@ -138,7 +138,7 @@ MD5 is used in the following non-security-sensitive ways:
138 138
139 It is therefore not possible completely avoid the use of MD5 with 139 It is therefore not possible completely avoid the use of MD5 with
140 qpdf, but as long as you are using 256-bit encryption, it is not used 140 qpdf, but as long as you are using 256-bit encryption, it is not used
141 -in a securty-sensitive fashion. 141 +in a security-sensitive fashion.
142 142
143 .. _breaking-crypto-api: 143 .. _breaking-crypto-api:
144 144