-
Notifications
You must be signed in to change notification settings - Fork 0
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
Valgrind Error when using AEAD Encryption via CLI #40
Comments
@TJ-91 Thanks for spotting this! This could be the reason of this discussion: #35 (comment) Probably valgrind do stricter checks than other CI tools. I'll try to reproduce it and introduce the required fixes. |
The same (or a closely related) error can be seen when running the test case I also noticed that running the test case
|
I now also tried |
@TJ-91 Thanks for the information. File PR here: rnpgp/rnp#2119 |
to be verified still by MTG |
Could this have the same source as this one: randombit/botan#3926 ? Which is fixed via rnpgp/rnp@007ccdb |
It's possible. I can't reproduce the erorr with the current code so I assume it's fixed and I'm closing the issue. |
Reproduce (assumes no keys in key store, otherwise have to specify the key when encrypting):
$ ./src/rnpkeys/rnpkeys -g --expert
./src/rnp/rnp -e cleartextfile
Results in a valgrind error, probably related to AEAD as used in SEIPDv2:
When not using AEAD but forcing SEIPDv1 (via
--v3-pkesk-only
flag), there is no error.The text was updated successfully, but these errors were encountered: