warning/error about ignored --encrypt-key or --encrypt-key-file if the --encrypt option is missing
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Confirmed
|
Medium
|
Unassigned | |||
2.4 |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hi,
If you specify --encrypt=AES256 but not --encrypt-key or --encrypt-key-file the result will be:
* xtrabackup --defaults-file= --user=root --password='' --backup --socket=
InnoDB: Number of pools: 1
encryption: no encryption key or key file specified.
encryption: unable to set libgcrypt cipher key - User defined source 1 : Invalid key length
encrypt: failed to create worker threads.
Error: failed to initialize datasink.
If you did not specify --encrypt but --encrypt-key or --encrypt-key-file, they will be ignored silently.
* xtrabackup --defaults-file= --user=root --password='' --backup --socket=
InnoDB: Number of pools: 1
171222 12:27:40 >> log scanned up to (696446812)
xtrabackup: Generating a list of tablespaces
InnoDB: Allocated tablespace ID 21 for sys/sys_config, old maximum was 0
171222 12:27:41 >> log scanned up to (696446812)
171222 12:27:42 >> log scanned up to (696451913)
171222 12:27:43 >> log scanned up to (696451913)
171222 12:27:44 >> log scanned up to (696451913)
The best is to force to use --encrypt if (--encrypt-key or --encrypt-key-file) specified or print warning/error on this.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-798