Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2.2, 10.3.0, 10.4.0
-
None
Description
Although it is possible to CREATE TEMPORARY TABLE ... ENCRYPTED=yes temporary tablespace will contain data in plaintext (check file ibtmp1).
Attachments
Issue Links
- causes
-
MDEV-20142 encryption.innodb_encrypt_temporary_tables failed in buildbot with wrong result
-
- Closed
-
-
MDEV-20340 Encrypted temporary tables cannot be read with full_crc32
-
- Closed
-
I think that we must fix the code so that the InnoDB temporary tablespace file is encrypted if and only if innodb_encrypt_tables is set. All pages of the tablespace can and should be encrypted; there is no reason to disable encryption on page 0, because we do not care about the contents of the temporary tablespace after InnoDB has been killed or shut down.
Also, the table option ENCRYPTED should cause a warning to be issued if it contradicts with the encryption status of the tablespace.