Closed Lo0815 closed 3 years ago
I have never used docker. But the error says that the connection is not in the NAT table. As you probably know by now, sslproxy and sslsplit ask the NAT engine of the system the connection information, such as the source and destination addresses. If the NAT engine does not know such info, then sslproxy and sslsplit are clueless and should terminate the connection, as they do in your tests. As I said I am not familiar with docker, so I don't know why the NAT engine of the system running in a docker container does not have that info. (Perhaps it is not supposed to, because perhaps that's the purpose of containerization? I guess I should learn more about such environments, and try running sslproxy in them myself.)
I find a workaround using --net=host option to access the host network. Maybe this will help others with the same problem.
Thank you for your help
Hi when i try to run the SSLProxy (same with Sslplit) inside a Docker Container i always get the folllowing Error Can you tell what is going wrong here or is it a bug?
I expose the Port 8443 to the host system
sudo docker run -it -p 8443:8443 testssl
and redirect the traffic from 443 to the port 8443 (on the host)
Thanks in advance