[MDEV-7803] Encryption metadata (crypt_data) is written to InnoDB file space page 0 even when encryption is not enabled - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.1.3
Fix Version/s: 10.1.4
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Labels:
None

Description

When innodb_encrypt_tablespace == FALSE and fil_space_page_encrypted(space) == FALSE make sure that no encryption data is written to file space page 0 and redo-logs.
If we have existing database that is not encrypted make sure that encryption can be enabled and all existing file spaces are encrypted (Google encryption).

Attachments

Activity

People

Assignee:: Jan Lindström (Inactive)

Reporter:: Jan Lindström (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2015-03-19 10:39

Updated:: 2015-03-19 14:13

Resolved:: 2015-03-19 14:13

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.