Encrypt with MK pages 1-4 of system tablespace

Description

Keyring encryption based on MariaDB implementation does not encrypt  FSP_TRX_SYS_PAGE_NO as it contains double write buffer header. Ours MK system tablespace encryption on the other hand also does not encrypt pages 1-4. Seems it should be safe to encrypt those pages. There should not be backward incompatibility if we start to encrypt those pages now as encryption information can be set for not encrypted page. The page's decryption function looks at the page's header and if it sees that the page is not encrypted it returns and leaves the page intact.

Environment

None

Smart Checklist

Activity

Show:

Julia Vural March 4, 2025 at 9:04 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Won't Do

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created April 9, 2019 at 7:55 AM
Updated March 4, 2025 at 9:04 PM
Resolved March 4, 2025 at 9:04 PM