[MDEV-8141] InnoDB: background encryption thread uses FIL_DEFAULT_ENCRYPTION_KEY Created: 2015-05-11 Updated: 2015-05-13 Resolved: 2015-05-13 |
|
| 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: | Major |
| Reporter: | Sergei Golubchik | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
In XtraDB/InnoDB the background encryption thread needs to check the latest key version for every tablespace to be able to re-encrypt tablespaces as necessary. Instead it asks for the latest key version for the key id 1. This is incorrect, because different tablespaces might be encrypted with different key ids and have different key rotation policies. |
| Comments |
| Comment by Sergei Golubchik [ 2015-05-11 ] |
|
jplindst, could you please review this fix? http://lists.askmonty.org/pipermail/commits/2015-May/007840.html |
| Comment by Jan Lindström (Inactive) [ 2015-05-12 ] |
|
ok to push. |