[MDEV-8238] Tables with encryption=yes using file_key_management plugin are not encrypted Created: 2015-05-27  Updated: 2015-05-27  Resolved: 2015-05-27

Status: Closed
Project: MariaDB Server
Component/s: Encryption, Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.4
Fix Version/s: 10.1.5

Type: Bug Priority: Blocker
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Attachments: File innodb_page_encryption_key_change.test     Text File keys2.txt     Text File keys3.txt     Text File keys4.txt    

 Description   

Effect file_key_management_plugin where first tables with key_id 1-4 are created, then key_id is changed in all tables to 5. Restart server with different key file where keys 1-4 are deleted and new key_id 6-9 are introduced but naturally key 5 remains the same. Idea is to alter tables back to use changed keys for key_ids 6-9.

 Comments   
Comment by Jan Lindström (Inactive) [ 2015-05-27 ]

Actual keys can be changed as long the key_id does not change.

Comment by Jan Lindström (Inactive) [ 2015-05-27 ] 

150527 12:10:56 [ERROR] InnoDB: Tablespace id 9 encrypted but encryption service not available. Can't continue opening tablespace.
 
 
 
2015-05-27 12:10:56 7f69cdbbe780  InnoDB: Assertion failure in thread 140092399937408 in file ha_innodb.cc line 21135

Problem is that key_id 1 can't be removed.

Comment by Jan Lindström (Inactive) [ 2015-05-27 ]

Key_id 1 is needed but tables are not really encrypted.

Comment by Jan Lindström (Inactive) [ 2015-05-27 ]

commit a25ccd4f83912e02091abe1cba8515266483559b
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Wed May 27 15:37:13 2015 +0300

MDEV-8238: Tables with encryption=yes using file_key_management plugin are not encrypted

Analysis: Problem was that encryption was skipped.

Fixed by making sure that tables with ENCRYPTED=YES are encrypted.

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