The Ultimate Guide to High Availability with MariaDB

START_ENCRYPTION event

You are viewing an old version of this article. View the current version here.

The START_ENCRYPTION event is written in every binary log file if 'encrypt_binlog' is set to ON in my.cnf.

This event is written just once and after The Format Description event, which is the first event of a binlog file.

The event has the 19 bytes event header with EventType set to value 164 (0xa4) + 17 bytes

The event payload is:

  • uint<1> The Encryption scheme, always set to 1 for system files
  • uint<4> The Encryption key version
  • byte<12> Nonce (12 random bytes) of current binlog file.

Note: the Nonce 12 bytes + the binlog event current pos uint<4> form the encrryption IV (16 bytes) for the event.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.