[MDEV-16997] Conflicting value definitions for innodb_encrypt_tables Created: 2018-08-16  Updated: 2018-08-16  Resolved: 2018-08-16

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Affects Version/s: 10.3.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Ceri Williams Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: encryption, innodb_encrypt_tables

Issue Links:
Relates
relates to MDEV-16998 Allow logging of plaintext InnoDB tab... Open

 Description   

When reading Encrypting Data for InnoDB / XtraDB you may be lead to believe that if you are using innodb_encrypt_tables=FORCE then you would be unable to access any InnoDB tables that are storing data in plaintext.

Option Description
OFF Disables table encryption
ON Enables table encryption, but allows unencrypted tables
FORCE Enables table encryption, but doesn't allow unencrypted tables

The variable documentation states it differently:

Description: Encrypt all tables in the storage engine. See Table and Tablespace Encryption. The FORCE option (from 10.1.4) means that XtraDB/InnoDB will refuse to create unencrypted tables (CREATE TABLE ... ENCRYPTED=NO will fail).

This could lead to someone having the wrong impression about using FORCE



 Comments   
Comment by Ian Gilfillan [ 2018-08-16 ]

Clarified documentation

Generated at Thu Feb 08 08:33:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.