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

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

The event payload is:

<uint8_t> binlog_crypto_scheme The Encryption scheme, always set to 1 for system files <uint32_t> binlog_key_version The Encryption key version */ <uint8_t> nonce[12] nonce (random bytes) of current binlog. These bytes + the binlog event current pos form the encrryption IV (16 bytes) for the event <uint32_t> crc32 crc32 of the event if binlog_checksum=CRC3 in my.cnf

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.