-
Notifications
You must be signed in to change notification settings - Fork 328
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
Segmentation fault starting thread manager #10
Comments
No, this is definitely not issue #9. Could you post the output of |
Sure, here they are: ./sslsplit -V (gdb) run -D -l connections.log -j /tmp/sslsplit/ -S logdir/ -k ca.key -c ca.crt ssl 0.0.0.0 8443
Program received signal SIGSEGV, Segmentation fault. Thanks for your help |
Could I just replace proxy.c and pxythrmgr.c in sslsplit directory with the ones updated by you or should I tar the original archive again and use make with the replaced files? I tried the former but it still gives segmentation fault issue. Is there anything else I'd log to show you? Thanks for your time |
I suggest you do a git clone of master in order to test the latest code, that is safer than updating only those two files. Can you post the output of |
This should remove another potential source of segmentation faults when the thread manager fails to start. Issue: #10 Reported by: linuxton
Ok this is a -V of latest sslsplit git clone: ./sslsplit -V This is a try to run it:
And this is a gdb run of it:
Using a 'bt full' at this point gives a 'No stack.' message. Should I configure a ulimit number to successfully execute a bt full in gdb after running the program or is it normal since no segmentation fault error was in output? I ran the previous "standard" 0.4.7 version of sslsplit and did a bt full, thought it may have been useful to you since I forgot to add it last time: (gdb) run -D -l connections.log -j /tmp/sslsplit/ -S logdir/ -k ca.key -c ca.crt ssl 0.0.0.0 8443
Program received signal SIGSEGV, Segmentation fault. quit
Quit anyway? (y or n) Is it normal that executing two different 'run' in gdb gives different LWP numbers (see above 'run' of latest github clone, LWP 3970/3971/3972 while this log gives LWP 4071/4072/4073)? (gdb) run -D -l connections.log -j /tmp/sslsplit/ -S logdir/ -k ca.key -c ca.crt ssl 0.0.0.0 8443
Is there anything else I'd log? Thanks for your time |
Same error here, seems to be related to the -j option. If i try without -j it starts just fine.
|
[Comment moved to new separate issue #11 since it is possibly unrelated.] |
If I get FYI, This is on a RaspberryPi
|
There are actually two issues; one issue is that the thread manager fails to start (which I cannot reproduce so far), and the other is that sslsniff crashes after the thread manager fails to start (which I can reproduce by simulating a thread manager startup failure). The two commits referenced in this issue fixed many (all?) of potential sources of segmentation faults after thread manager startup failure, so you should not get any segmentation faults anymore if you use latest master. There is no fix for the failing thread manager yet. |
If you are using latest the latest git master version and still encounter a segmentation fault following If you are able to reproduce the |
I'm closing the issue since I believe the segmentation faults to be fixed. If you encounter any |
Hello,
when I try to run sslsplit (having libssl-dev and libevent-dev installed,generating self-signed certificates and using port forwarding before this) I get the following error:
I'm using:
on the command line.
Could this be a resurfacing of previously reported bug (issue #9)?
Thank you
The text was updated successfully, but these errors were encountered: