[MDEV-8141] InnoDB: background encryption thread uses FIL_DEFAULT_ENCRYPTION_KEY - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.1.4
Fix Version/s: 10.1.5
Component/s: Encryption, Storage Engine - InnoDB, Storage Engine - XtraDB
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.

Attachments

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Sergei Golubchik

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2015-05-11 16:16

Updated:: 2015-05-13 16:16

Resolved:: 2015-05-13 16:16

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

Git Integration

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