You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2025/01/28 15:06:00 UTC
[jira] [Created] (IMPALA-13705) Environment specific errors in test_encryption_exprs
Csaba Ringhofer created IMPALA-13705:
----------------------------------------
Summary: Environment specific errors in test_encryption_exprs
Key: IMPALA-13705
URL: https://issues.apache.org/jira/browse/IMPALA-13705
Project: IMPALA
Issue Type: Bug
Components: Backend, Infrastructure
Reporter: Csaba Ringhofer
This happened after running the recently introduced tests from
IMPALA-13039 in a different environment.
The tests failed on RHEL 8.8 + OpenSsl 1.1.1k + ARM cpu.
The passing tests I saw so far were with OpenSSL 1.0.2f/k and x86.
An example for failed test:
{code}
select base64encode(aes_encrypt('ABC', '1234567890123456','AES_128_GCM','1234567890123456'));
E assert Comparing QueryTestResults (expected vs actual):
E 'x+am+BIqtrEK9FpC/zrvpOycjQ==' != 'TrL7'
{code}
A theory for the cause is that AES_128_GCM falls back to another encryption on newer OpenSsl versions
{code}
impalad.WARNING:W0127 17:13:02.248562 553382 openssl-util.cc:382] 9343d005464c6a5d:e252059d00000000] AES_128_GCM is not supported, fall back to AES_256_CTR.
{code}
Generally it seems a bad idea to fall back to another mode, I think that we should return an error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)