-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aes_authenticate valgrind warning "uninitialised value(s)" #566
Comments
|
this could be a bug in re and/or openssl @robert-scheck any advice for how to report this to Fedora ? |
Could you let me understand how this is specific to Fedora? |
I am on Ubuntu 22.04 LTS |
https://github.com/baresip/re/actions/runs/3213367854/jobs/5252982891
The bug is present on both Ubuntu 22.04 and Fedora 36. It might be related to OpenSSL version 3.0.x We have been running the same test with valgrind and OpenSSL 1.1.1 for a long time with zero warnings. sorry @robert-scheck it was not specific to Fedora :) |
Maybe something needs to be initialized different in OpenSSL v3, but nothing that jumps out at me. If we are sure this is a OpenSSL upstream bug, we can try to suppress the error with a |
The issue can be reproduced with Debian 11 and OpenSSL 3.0.5
OS: Debian 11 When openssl is compiled with default options, the warning is present. If openssl is compiled with debug mode "./config -d" then there are no warnings. openssl code: } else {
/* The tag must be set before actually decrypting data */
if (!ctx->enc && ctx->taglen == UNINITIALISED_SIZET)
goto err;
if (!hw->cipherfinal(ctx, ctx->buf))
goto err;
ctx->iv_state = IV_STATE_FINISHED; /* Don't reuse the IV */
goto finish;
} |
Looks like its fixed in openssl 3.0.7-dev. |
@cspiel1 could you please try again with openssl from git HEAD or 3.0.7-dev ? If the bug is in the OpenSSL code, we can close this Issue. |
It is still there with
|
The issue is most likely in openssl and not re. We should perhaps create a valgrind suppression file. Btw, baresip selftest has no warnings |
the warning has been reported to the OpenSSL project. the warning could be in ASM code or it could be a false positive. it is possible to change the retest aesgcm code slightly, to avoid the warning |
Do you have time to make this PR for retest to avoid this? |
the testcode in aesgcm can be fixed by splitting the encryption and decryption steps into two parts. our code is correct, and the warning is either a false positive or bug in valgrind/openssl |
fixed in baresip/retest#162 |
Maybe an openssl issue?
The text was updated successfully, but these errors were encountered: