lp://staging/~gl-az/percona-xtrabackup/2.1-encrypted_stream
- Get this branch:
- bzr branch lp://staging/~gl-az/percona-xtrabackup/2.1-encrypted_stream
Branch merges
Branch information
- Owner:
- George Ormond Lorch III
- Status:
- Development
Recent revisions
- 488. By George Ormond Lorch III
-
Introducing xtrabackup with encryption.
Encryption will be done through the libgcrypt library which can be found documented here: http://
www.gnupg. org/documentati on/manuals/ gcrypt Addition of libgcrypt requires now that libgcrypt and libgpgerror packages be installed.
Many package repositories still contain older versions of libgcrypt. The current stable version of 1.5.0 is reccomended and will take advantage of the AES-NI instruction set if available.
Similar to compression, encryption is not supported on streamed tar backups.
New options:
--encrypt=<algorithm> : algorithm may be 'NONE', 'AES128', 'AES192' or 'AES256'. 'NONE' is used mainly for testing and is simply pass-through. Please refer to the libgcrypt manual for more information on these ciphers. --encrypt_
key=<key> : a proper length encryption key to use. It is not reccomended to use this option where there is uncontrolled access to the machine as the command line and thus the key can be viewed as part of the process info. See option --encrypt_key_file. --encrypt_
key_file= <keyfile> : the name of a file where the raw key of the appropriate length can be read from. The file must be a simple binary (or text) file that contains exactly the key to be used. --encrypt_
threads= <threadcount> : number of threads used to encrypt in parallel (default=1). --encrypt_
chunk_size= <size> : size (in bytes) of the working encryption buffer size for each encryption thread (default=64K). --compress_
chunk_size= <size> : size (in bytes) of the working compression buffer size for each encryption thread (default=64K). encrypt_key and encrypt_key_file are mutually exclusive. If --encrypt is specified, one of these MUST be specified else an error will occur.
encryption key lengths must be precise:
AES128=128 bits or 16 bytes
AES192=192 bits or 24 bytes
AES256=256 bits or 32 bytesWhen using the encrypt_key_file option, the file specified may have binary or textual content but must be _exactly_ the correct size for the algorithm being used. If using text, caution must be taken so that there are no extra spaces, tabs, carriage returns or line feeds within the file. These will cause the key to be read as an incorrect size and an error will be generated.
The coding task was fairly straight forward with some restructure/
refactoring approved by Alexey K:
- Update/set copyright notice in new and touched files to Copyright (c) 2009-2013 Percona Ireland Ltd.
- Implemented new ds_stdout data sink.
- Split the ds_stream data sink into two new, more specific data sinks, ds_archive and ds_xbstream.
- Implement write callback model for ds_xbstream similar to libarchive.
- Change ds_archive and ds_xbstream over to using callback write models.
- Add new option to compression --compress_chunk_size to allow user specified chunk size management.
- Implement xbcrypt format reader/writer. Format encapsulated as follows:
8 bytes - magic string "XBCRYP01"
8 bytes - reserved
8 bytes - original size
8 bytes - encrypted size
4 bytes - checksum
'encrypted size' bytes - encrypted data
- Implement a new ds_encrypt datasync modeled after the existing compression datasync which will use libgcrypt for actual encryption task and write callbacks.
- Add new options, options validations and pass through innobackupex.
- Implement new utility xbcrypt modeled after xbstream to perform encryption outside of xtrabackup for metadata and to offer a means of decrypting an encrypted backup.
- Implement new tests and refactor test script structure a little to make adding new, similar test cases a little easier.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/percona-xtrabackup/2.1