APCrypt Readme, Version 4.0
© 2009 Appligent, Inc.
| Product Version: | 4.0 |
| Release Date: | 10/29/09 |
| User Guide Version: | 4.0 |
| Publication Date: | 10/29/09 |
Introduction
APCrypt is a command-line driven server-based application that applies standard Acrobat security features to PDF documents. APCrypt is designed to run in tandem with other processes in an unattended environment and to handle high-volume and on-demand production needs. These release notes contain last-minute product information and updates. Please refer to the APCrypt User Guide for additional information.
Installation
For all UNIX platforms — setting environmental variables
In this release, there are two additional environmental variables (home directory and library path) that need to be set for APCrypt on all UNIX platforms. If you run APCrypt from the apcrypt script created during installation, these environmental variables will be set by the script. If you run apcryptapp directly, you will need to set these environmental variables to run APCrypt. Once APCrypt is installed, you can view the variables needed by looking at the apcryptapp script created by the installer.
For all UNIX platforms — setting the Appligent home directory
The environmental variable that stores the location of the Appligent home directory is APPLIGENT_HOME. The default location for the Appligent home directory is /usr/local/appligent. The Appligent home directory contains the library files and resources needed to run APCrypt. It also contains license information for APCrypt.
Example: export APPLIGENT_HOME=/usr/local/appligent
For UNIX platforms only (not including AIX) — setting the APDFL library path
The APDFL library path must be added to the LD_LIBRARY_PATH variable. The APDFL library path is located in a subdirectory of the APPLIGENT_HOME directory. The path should be set to ${APPLIGENT_HOME}/APDFL9.0.1/Libs
Example: export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${APPLIGENT_HOME}/APDFL9.0.1/Libs
For AIX only — setting the APDFL library path
The APDFL library path for AIX must be added to the LIBPATH variable. The APDFL library path is located in a subdirectory of the APPLIGENT_HOME directory. The path should be set to ${APPLIGENT_HOME}/APDFL9.0.1/Libs.
Example: export LIBPATH=${LIBPATH}:${APPLIGENT_HOME}/APDFL9.0.1/Libs
Registration Numbers for APCrypt 4.0
In previous versions of APCrypt, the APCrypt registration number was required as a command line option with the -r flag each time apcryptapp was run. An apcrypt script was provided that automatically added -r and the registration number to the apcryptapp command line when the script was run.
In the current release, in addition to getting the registration number from the command line, APCrypt can get the registration number from a license file in the appligent home directory. On UNIX systems, license files are created by the installation script and stored in the ${APPLIGENT_HOME}/license directory. For Windows, the license file is created by the installer and stored in the All Users\Application Data\Appligent\License directory. With a valid license file, the -r is no longer required on the command line. The -r option can still be used as in previous versions, and will override the value in the license file.
To Upgrade a Demo Version of APCrypt 4.0
As mentioned in the previous paragraph, registration numbers are now stored in the license directory. The license file for APCrypt 4.0 is called APCT_40.arn. To upgrade a demo version of APCrypt, change the demo number stored in the license file to your new registration number.
If you call the apcryptapp executable with the -r option directly from a script or program that you wrote, update the number in that file.
Type apcrypt -v on the command line and press Enter. The new registration number, and a message that it is valid, should be displayed.
Supported Platforms
See the [[apcrypt product page]].
New Security Features
- Apply 128-bit or 256-bit AES encryption to PDF documents; the latest and most secure Adobe Acrobat standard encryption mechanism.
- Utilize PDFs as secure envelopes; apply 256-bit AES security to PDF and non-PDF file attachments while leaving the PDF itself unencrypted.
New options
-rc4: Encrypt using the RC4 cryptography algorithm
-aes: Encrypt using the AES cryptography algorithm
-keylength <int>: Key Length. Valid options are 40, 128 & 256. Default is 128.
Note: If a file has been encrypted with AES 256 bit encryption, the file can only be opened under software that supports this compression. In the case of Adobe Acrobat or Reader, version 9 or above is required or you will receive the message "There was an error opening this document. Acrobat cannot decrypt the document.” When viewing the Document Information on a file that is set with AES 256 encryption, the PDF Version will be set as 1.7, Adobe Extension Level 3.
-onlyattach: Encrypt attachments only using AES. -onlyattach also requires the following flags on the command line: -userpass <Password>, -ownerpass <Password>, -aes -keylength 128 or 256
New Features
-nomod: Retain current file modification date
-optimize: Combine -flate, -rascii, -nolzw, -optxobj, -optcontent and -optfonts
Please Note: PDF files support the use of multiple types of compression simultaneously. Object level compression is a technique developed by Adobe to reduce the size of PDF files. Object level compression is used in addition to the other compression mechanisms used within the PDF file. Object level compression will reduce the file size typically by 2%. The limitation of Object level compression is that this compression mechanism is not always understood by older versions of Acrobat or third party PDF viewers or procession tools.
To use object level compression, use -comp. This flag will apply object level compression, typically reducing file size by 2%.
To not use object level compression, use -nocomp. This flag will not add object level compression and will remove object level compression, if found, resulting in a document that is compatible with all versions of Acrobat.
To create a document that is ISO 32000 compliant, use -iso32000. This flag sets the output file for ISO 32000 compliance, resulting in a document that is PDF version 1.7.
Known Issues
If an input file has a user password set
The user password is copied over into the new output file even if -userpass <Password> is not supplied on the command line.
-d option must have Owner password
All encrypted documents that you decrypt with -d ownerpass must have an Owner password. You cannot use the -d option without an Owner password. If you have a legacy PDF document that was encrypted without an Owner password, you must create an Owner password for the document before using the -d option to decrypt it.
Corrupt output file created when required -d option omitted
If -d ownerpass is not specified when decrypting an input file secured with an Owner password, APCrypt processes the file anyway and creates a corrupt output file. Always use the -d ownerpass option for decryption.
Form fields
APCrypt cannot decrypt files with form fields. If you need to apply encryption to a document with form fields, delete them, remove encryption manually beforehand, or flatten them with FDFMerge.
Linearization
Linearization (-w) should not be used with files that contain articles.
To Get Help:
Documentation for APCrypt can be found here.
Contact technical support by:
emailing support@appligent.com, or calling 610-284-4006
Please provide the following:
Product name and version number
Operating system
Your name, company name, email address, and phone number
Description of your question or problem
Responses are typically emailed within one business day.