sniproxy
sniproxy copied to clipboard
Proxies incoming HTTP and TLS connections based on the hostname contained in the initial request of the TCP session.
Looks like something is amiss when building on RHEL. Any ideas? ``` [rhel8 sniproxy]# rpmbuild --define "_sourcedir `pwd`" -ba redhat/sniproxy.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.2B49Tw + umask 022 + cd /root/rpmbuild/BUILD...
The PCRE library is now abandoned and not maintained anymore. That library should not be used, especially when the input can come from an untrusted source. There is a newer...
I've been running sniproxy for about a year now, and haven't had any issues. Until recently one of my hosts going through sniproxy seems to be taking over. For some...
Add Dockerfile and update README.md (Please add hacktoberfest label to this PR, and if you want to merge it, please add hacktoberfest-accepted and hacktoberfest labels)
Usefull to perform arbitrary rewrite of the address
It's not possible to bind to the same address and port when the client is the same as the listener because it will already be in use by the incoming...
Proof-of-concept for #371: for review rather than actual merge. Usage: ``` listen 0.0.0.0 443 { proto tls embed fd46:1:: } ``` If the inbound connection is IPv4, and the outbound...
Hi, Currently, when the client is IPv4 and the destination is IPv4, transparent proxying works. When the client is IPv6 and the destination is IPv6, it does not, because the...
This makes it possible to get a list of active connections without the need to search trough temp files. I needed a way to remotely get a list of open...