-
Notifications
You must be signed in to change notification settings - Fork 481
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
PS-8389 feature: Align PS Encryption UDFs functionality with new feat…
…ures from MySQL 8.0.30 Enterprise Encryption Component (openssl111 evp_pkey) https://jira.percona.com/browse/PS-8389 'evp_pkey' class reworked to support OpenSSL 1.1.1. We no longer use 'OSSL_PARAM's to operate on 'EVP_PKEY' as they become available only starting from OpenSSL 3.0.0. Fixed exception error message in 'decrypt_with_rsa_public_key()' / 'decrypt_with_rsa_private_key()' functions. Modified 'digest_table.inc' MTR include file. For OpenSSL 1.1.1 we use the following digests only for 'create_digest()' checks but not for 'asymmetric_sign()': - 'sha512-224' - 'sha512-256' - 'whirlpool' - 'sm3' - 'blake2b512' - 'blake2s256' - 'shake128' - 'shake256' For OpenSSL 3.x.y we use the following digests only for 'create_digest()' checks but not for 'asymmetric_sign()': - 'sha1' - 'md5-sha1' This change was necessary only for Oracle Linux 9 platform - for some reason its default OpenSSL 3.0.7 has additional restriction that these digests cannot be used in 'RSA' 'EVP_PKEY' signing operations. Checks for default padding scheme in 'asymmetric_encrypt()' / 'asymmetric_decrypt()' removed from the 'component_encryption_udf.xsa_sanity' MTR test case as they are covered in 'component_encryption_udf.legacy_padding_scheme'. 'component_encryption_udf.legacy_padding_scheme' MTR test case modified to take into account that decrypting messages with different padding scheme may either fail with an error or succeed but produce garbage (depending on random bytes inserted into the encrypted message).
- Loading branch information
1 parent
d39f32e
commit b64d618
Showing
9 changed files
with
138 additions
and
135 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.