-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Keylog capture not working with OpenSSL 1.1.0 #533
Labels
Comments
The issue seems to be related to the incorrect assignment of the OpenSSL offset for OpenSSL 1.1.0 in the ecapture/user/module/probe_openssl_lib.go Line 107 in a8acece
After correcting the file assignment, the keylog capture starts working, but the captured data appears to be incorrect. |
AmazingPP
added a commit
to AmazingPP/ecapture
that referenced
this issue
Apr 28, 2024
the problem was the `client_random` member having different offsets within the `ssl3_state_st` structure across various OpenSSL versions Fixes gojue#533
Can |
Yes, the |
cfc4n
pushed a commit
that referenced
this issue
Apr 29, 2024
* user : fixed the incorrect assignment of the OpenSSL offset for OpenSSL 1.1.0 * kern: fix incorrect client_random capture for different OpenSSL versions the problem was the `client_random` member having different offsets within the `ssl3_state_st` structure across various OpenSSL versions Fixes #533
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the
ecapture
tool with OpenSSL 1.1.0 to capture keylog data with the-m keylog
option, no output is generated.
To Reproduce
Steps to reproduce the behavior:
ecapture
repository usinggit clone https://github.com/gojue/ecapture.git
/opt/openssl
curl
with the provided OpenSSL 1.1.0 libraryecapture
in text mode to capture TLS traffic usingsudo ./bin/ecapture tls --libssl=/opt/openssl/lib/libssl.so.1.1
curl
)ecapture
processsudo ./bin/ecapture tls -m keylog -k ecapture.txt --libssl=/opt/openssl/lib/libssl.so.1.1
ecapture.txt
file
Expected behavior
When using the
-m keylog
option with OpenSSL 1.1.0,ecapture
should capture and output keylog data to the specified file (ecapture.txt
in this case).
Screenshots
I cannot provide screenshots directly, but here is the relevant output from the terminal:
Linux Server:
Additional context
This issue seems to be specific to the OpenSSL 1.1.0 version. I have tried reproducing this issue on multiple Linux distributions and kernel versions, and the behavior is consistent with OpenSSL 1.1.0. It seems that the keylog capture functionality is not working as expected with this particular OpenSSL version, despite TLS decryption working correctly. I would appreciate if this issue could be investigated and resolved for OpenSSL 1.1.0 compatibility.
The text was updated successfully, but these errors were encountered: