From 21b0f4acfc0d6827f3d2d9a85873b7b649dc96f0 Mon Sep 17 00:00:00 2001 From: Jay Berkenbilt Date: Thu, 4 Feb 2021 15:55:41 -0500 Subject: Require --allow-insecure to create certain encrypted files (fixes #501) For now, --allow-insecure allows creation of files with the owner passwords empty or matching the user password. --- manual/qpdf-manual.xml | 48 ++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 46 insertions(+), 2 deletions(-) (limited to 'manual') diff --git a/manual/qpdf-manual.xml b/manual/qpdf-manual.xml index fda9c1fd..0d9fd489 100644 --- a/manual/qpdf-manual.xml +++ b/manual/qpdf-manual.xml @@ -1214,7 +1214,11 @@ make Either or both of the user password and the owner password may be - empty strings. + empty strings. Starting in qpdf 10.2, qpdf defaults to not + allowing creation of PDF files with an empty owner password or an + owner password that matches the user password. If you want to + create such files, specify the encryption option + , as described below. The value for @@ -1223,6 +1227,25 @@ make When no additional restrictions are given, the default is to be fully permissive. + + For all key lengths, the following options are available: + + + + + + From qpdf 10.2, qpdf defaults to not allowing creation of PDF + files where the owner password is blank or matches the user + password. Files created in this way are insecure and can't be + opened by some viewers. Users would ordinarily never want to + create such files. If you are using qpdf to intentionally + created strange files for testing (a definite valid use of + qpdf!), this option allows you to create such insecure files. + + + + + If is 40, the following restriction options are available: @@ -4824,7 +4847,28 @@ print "\n"; - Behavior Changes + CLI Behavior Changes + + + + + By default, qpdf no longer allows + creation of encrypted PDF files whose owner password is + empty or matches the user password. The + , specified inside the + options, allows creation of such + files. Behavior changes in the CLI are avoided when + possible, but an exception was made here because this is + security-related. qpdf must always allow creation of weird + files for testing purposes, but it should not default to + letting users unknowingly create insecure files. + + + + + + + Library Behavior Changes -- cgit v1.2.3-54-g00ecf