-
Notifications
You must be signed in to change notification settings - Fork 81
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add tool compression and encryption support
Updated a number of tools to provide support for dealing with compressed and/or encrypted data (assuming that the compressed data is compressed with the GZIP algorithm, and that encrypted data is written with the PassphraseEncryptedOutputStream). This includes: * If ldapsearch output is to be written to one or more LDIF files, it is now possible to compress and/or encrypt that output. The --compressOutput argument can be used to indicate that the output should be compressed, and the --encryptOutput argument can be used to indicate that the output should be encrypted. If the --encryptionPassphraseFile argument is provided, the encryption passphrase will be read from that file; otherwise, it will be interactively requested from the user. * If ldapmodify is to read the changes to apply from one or more LDIF files, it can automatically detect whether the files are encrypted and/or compressed and will handle them accordingly. If the --encryptionPassphraseFile argument is provided, the encryption passphrase will be read from that file; otherwise, it will be interactively requested from the user. * The split-ldif and transform-ldif tools can now automatically detect whether the input LDIF files are compressed and/or encrypted, and they can now be directed to encrypt their output. The --sourceCompressed argument is still supported for the purpose of backward compatibility, but it is no longer required. The --encryptTarget argument can be used to indicate that the output should be encrypted. If the --encryptionPassphraseFile argument is provided, then the passphrase will be read from the specified file; otherwise, it will be interactively requested from the user. * The validate-ldif tool can now automatically detect whether the input LDIF file is compressed and/or encrypted. The --isCompressed argument is still supported for the purpose of backward compatibility, but it is no longer required. If the --encryptionPassphraseFile argument is provided, then the passphrase will read from the specified file; otherwise, it will be interactively requested from the user. * The summarize-access-log tool can now automatically detect whether the input log files are compressed and/or encrypted. The --isCompressed argument is still supported for the purpose of backward compatibility, but it is no longer required. If the --encryptionPassphraseFile argument is provided, then the passphrase will read from the specified file; otherwise, it will be interactively requested from the user.
- Loading branch information
Showing
22 changed files
with
4,240 additions
and
264 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.