summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2019-01-18 03:51:30 +0100
committerJay Berkenbilt <ejb@ql.org>2019-01-19 16:14:07 +0100
commitc2030d1f333b9403cfb15460c4b9ca9fcb446021 (patch)
treeded1969d6ffd9d87fcbb38d80830805158471002 /ChangeLog
parent392f2ece51e66dd4c92df3be7f91b637cb54c059 (diff)
downloadqpdf-c2030d1f333b9403cfb15460c4b9ca9fcb446021.tar.zst
Implement password recovery suppression and password mode (fixes #215)
Allow fine control over how passwords are encoded for writing, and allow password for reading to be given as a hexademical encoded string. Allow suppression of password recovery as a means to ensure that the password you specify is actually the right one.
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog22
1 files changed, 22 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 4c1e62d8..684601aa 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,25 @@
+2019-01-19 Jay Berkenbilt <ejb@ql.org>
+
+ * NOTE: qpdf CLI: some non-compatible changes were made to how
+ qpdf interprets password arguments that contain Unicode characters
+ that fall outside of ASCII. On Windows, the non-compatibility was
+ unavoidable, as explained in the release notes. On all platforms,
+ it is possible to get the old behavior if desired, though the old
+ behavior would almost always result in files that other
+ applications were unable to open. As it stands, qpdf should now be
+ able to open passwords encrypted with a wide range of passwords
+ that some other viewers might not handle, though even now, qpdf's
+ Unicode password handling is not 100% complete.
+
+ * Add --password-mode option, which allows fine-grained control of
+ how password arguments are treated. This is discussed fully in the
+ manual. Fixes #215.
+
+ * Add option --suppress-password-recovery to disable the behavior
+ of searching for a correct password by re-encoding the provided
+ password. This option can be useful if you want to ensure you know
+ exactly what password is being used.
+
2019-01-17 Jay Berkenbilt <ejb@ql.org>
* When attempting to open an encrypted file with a password, if