-
Notifications
You must be signed in to change notification settings - Fork 103
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
This same setup works with sslsplit but not with sslproxy #60
Comments
Can you make sure your test machine SSLproxy is running on has Internet connection, that SSLproxy can resolve names during tests, and report back please? |
Yes, ping is working
From the debug output above, I think SSLproxy can resolve names
I am not entirely sure if it can resolve them during tests. But if it couldn't, the tests would have failed, right? |
My current theory is that your machine does not have IPv6, for some reason. Can you check if it has an IPv6 address please? (I have never run those tests without IPv6, I can try, but it will take some time.) Otherwise, I have run the unit tests, make unittest, with the same git version as you have, and all tests pass successfully. Btw, looking at the number of checks, 212, you seem to run the tests as sudo or root. Also, I think the errors in the debug output you have posted are usually caused if you don't install on your browser (or whatever program you use) the CA cert you pass to SSLproxy. |
I pass these same certificates to sslsplit, and it runs fine.
No, there is no ipv6 address. Is that necessary? Should I assign to the interface any local ipv6 address? |
OK, I think those errors are due to cert verification, not CA cert. SSLproxy verifies certificates by default, but sslsplit does not. That explains the difference. You can disable cert verification by the VerifyPeer option, for example by passing
I think that's why the unit tests fail. Can you enable IPv6 and try again please? (I don't think there is any issue on your setup, you can skip those tests if you want, but please report back if IPv6 fixes the failing tests.)
That's fine, two extra tests are enabled if run as root user. |
I am getting PR_CONNECT_RESET_ERROR in firefox while using sslproxy. With sslsplit, firefox gives no such error |
Yes, I assigned an IPv6 address, and no failures now. Although running
|
I need debug logs for PR_CONNECT_RESET_ERROR, -D4 would be better, but you should rebuild with DEBUG_PROXY for that, and perhaps with other switches, see main.mk. You need testproxy for e2e tests. If you don't want the e2e tests, just run |
DEBUG_PROXY feature enabled. Running with -D4 gave:
|
You did not provide the command line you start sslproxy with, but looking at the debug logs I think you did not pass the |
sslproxy -V
uname -a
sslproxy
make test
outputThe text was updated successfully, but these errors were encountered: