Contents

These files have been created by encrypting the minimal.pdf file.
The used encryption algorithm as well as the key length is encoded
in the files name.

The prefix shows which if any password was used:
* nopwd: No password was set.
* userpwd: An user password of 'uhexapdf' has been set.
* ownerpwd: An owner password of 'ohexapdf' has been set.
* bothpwd: Both the above user and owner passwords have been set.

Version data entries

96 entries across 96 versions & 1 rubygems

Version	Path
hexapdf-1.0.2	test/data/standard-security-handler/README
hexapdf-1.0.1	test/data/standard-security-handler/README
hexapdf-1.0.0	test/data/standard-security-handler/README
hexapdf-0.47.0	test/data/standard-security-handler/README
hexapdf-0.46.0	test/data/standard-security-handler/README
hexapdf-0.45.0	test/data/standard-security-handler/README
hexapdf-0.44.0	test/data/standard-security-handler/README
hexapdf-0.41.0	test/data/standard-security-handler/README
hexapdf-0.40.0	test/data/standard-security-handler/README
hexapdf-0.39.1	test/data/standard-security-handler/README
hexapdf-0.39.0	test/data/standard-security-handler/README
hexapdf-0.38.0	test/data/standard-security-handler/README
hexapdf-0.37.2	test/data/standard-security-handler/README
hexapdf-0.37.1	test/data/standard-security-handler/README
hexapdf-0.37.0	test/data/standard-security-handler/README
hexapdf-0.36.0	test/data/standard-security-handler/README
hexapdf-0.35.1	test/data/standard-security-handler/README
hexapdf-0.35.0	test/data/standard-security-handler/README
hexapdf-0.34.1	test/data/standard-security-handler/README
hexapdf-0.34.0	test/data/standard-security-handler/README