Commit e6cb3596d1648f39df425c24d44f211017c90203
Merge error in README.md mixing sections
James Hogarth committed on 3/30/2016, 10:48:45 AMParent: 38447c815821ae8b6379d8005628ea3c9f94f1ee
Files changed
| README.md | changed |
| README.md | ||
|---|---|---|
| @@ -389,26 +389,8 @@ | ||
| 389 | 389 | To use the generator place it in /usr/lib/systemd/system-generators and then |
| 390 | 390 | call systemctl daemon-reload after any changes to /etc/sslh.cfg to generate |
| 391 | 391 | the new dynamic socket unit. |
| 392 | 392 | |
| 393 | -Transparent proxying means the target server sees the real | |
| 394 | -origin address, so it means if the client connects using | |
| 395 | -IPv6, the server must also support IPv6. It is easy to | |
| 396 | -support both IPv4 and IPv6 by configuring the server | |
| 397 | -accordingly, and setting `sslh` to connect to a name that | |
| 398 | -resolves to both IPv4 and IPv6, e.g.: | |
| 399 | - | |
| 400 | - sslh --transparent --listen <extaddr>:443 --ssh insideaddr:22 | |
| 401 | - | |
| 402 | - /etc/hosts: | |
| 403 | - 192.168.0.1 insideaddr | |
| 404 | - 201::::2 insideaddr | |
| 405 | - | |
| 406 | -Upon incoming IPv6 connection, `sslh` will first try to | |
| 407 | -connect to the IPv4 address (which will fail), then connect | |
| 408 | -to the IPv6 address. | |
| 409 | - | |
| 410 | - | |
| 411 | 393 | Fail2ban |
| 412 | 394 | -------- |
| 413 | 395 | |
| 414 | 396 | If using transparent proxying, just use the standard ssh |
Built with git-ssb-web