mirror of
https://github.com/MariaDB/server.git
synced 2025-05-05 16:59:35 +03:00
6b6987154a
Problem was that checksum check resulted false positives that page is both not encrypted and encryted when checksum_algorithm was strict_none. Encrypton checksum will use only crc32 regardless of setting. buf_zip_decompress: If compression fails report a error message containing the space name if available (not available during import). And note if space could be encrypted. buf_page_get_gen: Do not assert if decompression fails, instead unfix the page and return NULL to upper layer. fil_crypt_calculate_checksum: Use only crc32 method. fil_space_verify_crypt_checksum: Here we need to check crc32, innodb and none method for old datafiles. fil_space_release_for_io: Allow null space. encryption.innodb-compressed-blob is now run with crc32 and none combinations. Note that with none and strict_none method there is not really a way to detect page corruptions and page corruptions after decrypting the page with incorrect key. New test innodb-checksum-algorithm to test different checksum algorithms with encrypted, row compressed and page compressed tables.
13 lines
338 B
Plaintext
13 lines
338 B
Plaintext
[crc32]
|
|
loose-innodb-tablespaces-encryption
|
|
loose-innodb-encrypt-tables=on
|
|
loose-innodb-encryption-threads=4
|
|
max_allowed_packet=64K
|
|
loose-innodb-checksum-algorithm=crc32
|
|
[none]
|
|
loose-innodb-tablespaces-encryption
|
|
loose-innodb-encrypt-tables=on
|
|
loose-innodb-encryption-threads=4
|
|
max_allowed_packet=64K
|
|
loose-innodb-checksum-algorithm=none
|