KMIP Binlog Data At Rest Encryption (MXS-2662)

[MXS-4129] Add encryption to binlogrouter Created: 2022-05-11  Updated: 2022-06-15  Resolved: 2022-06-15

Status: Closed
Project: MariaDB MaxScale
Component/s: pinloki
Affects Version/s: None
Fix Version/s: 22.08.0

Type: Sub-Task Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-157, MXS-SPRINT-158, MXS-SPRINT-159, MXS-SPRINT-160, MXS-SPRINT-161, MXS-SPRINT-162

 Description   

Add encryption of binlog events to the binlogrouter. A similar approach can be taken that was used with MaxScale 2.4 where the following steps were taken to encrypt an event:

  • Store the real event length in memory
  • Move the 4 byte timestamp into the 4 byte event length field
  • Encrypt the data, excluding the 4 bytes from the start of the file that contain the timestamp (now stored where the length is stored)
  • Move the 4 bytes of encrypted data stored at the event length field into the 4 bytes where the timestamp is stored
  • Store the encrypted event length in the 4 byte event length field

Generated at Thu Feb 08 04:26:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.