Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.4-1, 10.2.4-2
Description
WL#8845 introduced a redo log format identifier in MySQL 5.7.9.
The MariaDB extension innodb_encrypt_log should distinguish encrypted redo logs from cleartext ones by the redo log format tag. In this way, an attempt to start up MySQL 5.7 after a crash of MariaDB with innodb_encrypt_log=1 will result in a clear error message rather than some strange-looking crash.
Attachments
Issue Links
- blocks
-
MDEV-12041 Implement key rotation for innodb_encrypt_log
-
- Closed
-
- causes
-
MDEV-13061 innodb_encrypt_log recovery is spamming the error log
-
- Closed
-
-
MDEV-13834 10.2 wrongly recognizes 10.1.10 innodb_encrypt_log=ON data as after-crash and refuses to start
-
- Closed
-
- includes
-
MDEV-12061 Allow innodb_log_files_in_group=1
-
- Closed
-
- is part of
-
MDEV-11873 Unnecessary InnoDB warnings upon bootstrap
-
- Closed
-
- relates to
-
MDEV-12103 Reduce the time of looking for MLOG_CHECKPOINT during crash recovery
-
- Closed
-
-
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC
-
- Closed
-
-
MDEV-14874 innodb_encrypt_log corrupts the log when the LSN crosses 32-bit boundary
-
- Closed
-
-
MDEV-9011 Redo log encryption does not work
-
- Closed
-
-
MDEV-11432 Change the informational redo log format tag to say "MariaDB 10.2.3"
-
- Closed
-
-
MDEV-13253 After rebuilding redo logs, InnoDB can leak data from redo log buffer
-
- Closed
-
-
MDEV-13318 Crash recovery failure after the server is killed during innodb_encrypt_log startup
-
- Closed
-