third-party-mirrors/sslh
1
0
Fork 0
mirror of https://github.com/yrutschle/sslh.git synced 2025-04-13 07:37:15 +03:00
Code Issues Packages Projects Releases Wiki Activity

clarify the difficulty of transparent proxying

Browse Source
This commit is contained in:
Yves Rutschle 2024-03-12 22:07:17 +01:00
parent 3117c15fbd
commit 7ca567fcd9
2 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -36,6 +36,18 @@ Configuration
Please refer to the [configuration guide](doc/config.md).
Transparent proxying allows the target server to see the
original client IP address, i.e. `sslh` becomes invisible.
This makes it easier to use the server's logs, and potential
IP-based banning ability.
Configuration of transparent proxying is highly dependent on
your network environment and infrastructure setup. There is
no known generic approach, and if you do not find directions
for your exact setup, you will probably need an extensive
knowledge of network management and iptables setup".
It is described in its own [document](tproxy.md).
Docker image

8
doc/config.md
View File

@ -99,12 +99,8 @@ Then you can run sslh-select as an unprivileged user, e.g.:
Transparent proxy support
-------------------------
Transparent proxying allows the target server to see the
original client IP address, i.e. `sslh` becomes invisible.
This makes it easier to use the server's logs, and potential
IP-based banning ability.
Set up can get complicated, so it has its own [document](tproxy.md).
Transparent proxying is described in its own
[document](tproxy.md).
Systemd Socket Activation
-------------------------