Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.5
-
None
Description
Found by reading the code. https://github.com/MariaDB/server/blob/17080cbcf04ab295806db8aaaeead2696988fab4/storage/innobase/log/log0crypt.cc#L158
So, all key rotation logic depends on log_t::FORMAT_ENC_10_4 while in 10.5 it should also work for log_t::FORMAT_ENC_10_5
Attachments
Issue Links
- is caused by
-
MDEV-12353 Efficient InnoDB redo log record format
-
- Closed
-
- relates to
-
MDEV-12041 Implement key rotation for innodb_encrypt_log
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Eugene Kosov [ kevg ] |
Link |
This issue is caused by |
Link |
This issue relates to |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Fix Version/s | 10.5.2 [ 24030 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 104875 ] | MariaDB v4 [ 157439 ] |
The fix will change the format of the redo log record blocks when using innodb_encrypt_log.
Because the log format was changed (and this bug introduced) in MariaDB 10.5.2 by
MDEV-12353and related changes, it would be best if also this fix were included in MariaDB 10.5.2. If we fail to include this fix in 10.5.2, then we would have to implement another redo log format tag for the 10.5.3+ encrypted redo log and maybe also implement upgrade logic from 10.5.2 to later 10.5 versions.