Prepare 11.6.3 release

This commit is contained in:
Jay Berkenbilt 2023-10-14 19:49:29 -04:00
parent 9055723af3
commit 81823f4032
2 changed files with 25 additions and 5 deletions

View File

@ -1,13 +1,19 @@
2023-10-15 Jay Berkenbilt <ejb@ql.org>
* 11.6.3: release
2023-10-14 Jay Berkenbilt <ejb@ql.org> 2023-10-14 Jay Berkenbilt <ejb@ql.org>
* Tweak linearization code to better handle files between 2 GB and * Tweak linearization code to better handle files between 2 GB and
4 GB in size. Fixes #1023. 4 GB in size. Fixes #1023.
* Fix serious bug: qpdf could discard a the character after an * Fix data loss bug: qpdf could discard a the character after an
escaped octal string. For content, this would only happen with QDF escaped octal string consisting of less than three digits. For
or when normalizing content, but it could have happened in a content, this would only happen with QDF or when normalizing
binary string. This bug was introduced between 10.6.3 and 11.0.0. content. Outside of content, it could have happened in any binary
Fixes #1050. string, such as /ID, if the encoding software used octal escape
strings with less than three digits. This bug was introduced
between 10.6.3 and 11.0.0. Fixes #1050.
2023-10-07 Jay Berkenbilt <ejb@ql.org> 2023-10-07 Jay Berkenbilt <ejb@ql.org>

View File

@ -38,6 +38,20 @@ Planned changes for future 12.x (subject to change):
.. x.y.z: not yet released .. x.y.z: not yet released
11.6.3: October 15, 2023
- Bug fixes:
- Fix a bug in which qpdf could potentially discard a character in
a binary string if that character was preceded by an octal
escaped string with fewer than three digits. This bug was
introduced in the 11.0.0 release. The bug would not apply to
content streams with default settings.
- The linearization specification precludes linearized files that
require offets past the 4 GB mark. A bug in qpdf was preventing
it from working when offsets had to pass the 2 GB mark. This has
been corrected.
11.6.2: October 7, 2023 11.6.2: October 7, 2023
- Bug fixes: - Bug fixes: