-
Notifications
You must be signed in to change notification settings - Fork 327
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
Child pid killed by signal 11 #278
Comments
Can you disable (comment out) the call to the function bufferevent_openssl_set_allow_dirty_shutdown() in pxy_conn_autossl_peek_and_upgrade() in the file pxyconn.c, and then recompile and try if it is going to crash still? That seems to be one of the main differences in autossl between 0.5.4 and 0.5.5. Btw, I guess the command line you have provided is not the actual command line you have used, because it is missing the -c option. Otherwise, sslsplit would quit with an error like "no CA cert specified (-c)". And I am surprised that the version of OpenSSL on osx is so old. |
Same problem here. I commented out the line and the problem persists! |
I tried with "ssl" and it stops also:
|
Can you try the underlying-bevs-issue#303 branch and report back please? It has a couple of fixes for autossl at least. Otherwise, enabling the DEBUG_PROXY switch in GNUmakefile can probably give us more info. |
Already tested the branch underlying-bevs-issue#303 and the failure continues. This is with "ssl":
And this with "autossl":
|
This is with DEBUG_PROXY switch in GNUmakefile enabled. Let me know if you require more info:
|
Unfortunately, those debug logs do not help either (I guess you have started sslsplit with the -D option, right?). The debug logs in sslsplit are not verbose. So the other option are:
|
Btw, I don't know your xnu version, but another possibility is that this may be about the header files under xnu. Please see the xnu folder in the sources. |
If this issue is on macOS Mojave 10.14.6 (which is the system the OP was using), can you please try the xnu-4903.270.47 branch? Since I don't have a macOS machine, this is a stab in the dark. |
Hi, 1.) I have reproduced this issue on Kali Linux VM. When I use Ubuntu 20.04 VM and the exact same software and setup, sslsplit does not crash. Scenario: Command: I have attached output of sslsplit -V and neofetch for both VMs in Kali_System.txt and Ubuntu_System.txt 2.) I have tried to use ssl-proxy but it doesn't work for my scenario, and I also need to dump decrypted traffic to pcap file which ssl-proxy I think is not capable of I have attached output of ssl-proxy and log of application used to connect to it in ssl-proxy.txt. 3.) I've used gdb but when I issued bt - there was no backtrace. Although I was able to find a coredump and have used coredumpctl to dump it. Attached coredump sslsplit_coredump and also gdb output and coredumpctl output in gdb_coredump.txt You will find all attachments in the .zip file Please tell me if any additional info is needed. P.S. - I have updated and upgraded both VMs and rebooted before repeating test |
Update:
Output for the non-working one:
Seems like I was using a pretty old version and wasn't aware of it. But on Ubuntu VM I am also using old build and it's surprisingly working:
|
Upgrading sslsplit inside Debookee from 0.5.4 to 0.5.5, sslsplit stops with signal 11 as soon as it sees first traffic.
Debug says :
Configuration:
On macOS 10.14.6, non-root Email traffic is redirected to interface lo0 and then port 6971 through redirections and NAT rules:
For bug reports, please supply:
sslsplit -V
uname -a
Darwin Pep 18.7.0 Darwin Kernel Version 18.7.0: Mon Feb 10 21:08:45 PST 2020; root:xnu-4903.278.28~1/RELEASE_X86_64 x86_64
Exact command line arguments used to run
sslsplit
sudo ./sslsplit -k ~/mitmproxy-ca.pem -L ~/logAllData.log -l ~/logConnections.log autossl 127.0.0.1 6971
List of failing unit tests in
make test
outputThe text was updated successfully, but these errors were encountered: