SetaPDF-Encryptor replaced by SetaPDF-Core2015-09-14
Finally we implemented the last puzzle from our version 1 branch of SetaPDF to version 2: All our SetaPDF components are shipped with support for public-key security by default now. Because the Core component was shipped with standard security as of its first release it covers now the full feature-set of the SetaPDF-Encryptor API which is obsolete as of now!
This implementation is not just writing encrypted PDF documents with the use of public-key cryptography but it is also possible to authenticate, read and modify (if this is allowed by the document author) these documents now. Read all details about the handling and usage of security handlers in SetaPDF here.
License owners of the SetaPDF-Encryptor API are welcome to send an email to firstname.lastname@example.org to initiate a license transfer to the Core component.
This release additionally includes the implementation of the latest security handler revision for AES 256 bit which comes with Acrobat X (defined in PDF 2.0 / 1.7 Adobe Extension Level 8). It replaces the previous revision because of a weakness in the password checking algorithm.
The deprecated factory class was renamed to SetaPDF_Core_SecHandler_Standard_Aes256R5 (to label revision 5) while the current revision is available by the old class name: SetaPDF_Core_SecHandler_Standard_Aes256
Release Notes and Downloads
Check the release notes of the components below.
Log in to download the latest version of the related packages!
Release date: 2015-09-14
Rev. 745 to 754
- Implemented public-key security handler for both reading and writing.
- Implemented revision 6 (AES256) in standard PDF security handler.
- Fixed behavior Text::getLines with glue characters like . or ,
- Forward a clean up call in SetaPDF_Core_Document::finish() to the PDF parser instance to close a possibly open reader file handle.
- Clean-up of security handler classes.