Commit 864b7badd2ddb767a0af545be19030e8e1dbc6dd
Merge pull request #115 from jimt/patch-1
Fix README typos.yrutschle authored on 12/19/2016, 8:39:09 PM
GitHub committed on 12/19/2016, 8:39:09 PM
Parent: f02ce3821c018719536971dbb1bc1ed1517530a2
Parent: 234c0883246ae63530622aff1e575d35b029db60
Files changed
README.md | changed |
README.md | ||
---|---|---|
@@ -134,9 +134,9 @@ | ||
134 | 134 | |
135 | 135 | Libwrap support |
136 | 136 | --------------- |
137 | 137 | |
138 | -Sslh can optionnaly perform `libwrap` checks for the sshd | |
138 | +Sslh can optionally perform `libwrap` checks for the sshd | |
139 | 139 | service: because the connection to `sshd` will be coming |
140 | 140 | locally from `sslh`, `sshd` cannot determine the IP of the |
141 | 141 | client. |
142 | 142 | |
@@ -144,12 +144,12 @@ | ||
144 | 144 | --------------- |
145 | 145 | |
146 | 146 | OpenVPN clients connecting to OpenVPN running with |
147 | 147 | `-port-share` reportedly take more than one second between |
148 | -the time the TCP connexion is established and the time they | |
148 | +the time the TCP connection is established and the time they | |
149 | 149 | send the first data packet. This results in `sslh` with |
150 | -default settings timing out and assuming an SSH connexion. | |
151 | -To support OpenVPN connexions reliably, it is necessary to | |
150 | +default settings timing out and assuming an SSH connection. | |
151 | +To support OpenVPN connections reliably, it is necessary to | |
152 | 152 | increase `sslh`'s timeout to 5 seconds. |
153 | 153 | |
154 | 154 | Instead of using OpenVPN's port sharing, it is more reliable |
155 | 155 | to use `sslh`'s `--openvpn` option to get `sslh` to do the |
@@ -395,10 +395,10 @@ | ||
395 | 395 | |
396 | 396 | If using transparent proxying, just use the standard ssh |
397 | 397 | rules. If you can't or don't want to use transparent |
398 | 398 | proxying, you can set `fail2ban` rules to block repeated ssh |
399 | -connections from a same IP address (obviously this depends | |
400 | -on the site, there might be legimite reasons you would get | |
399 | +connections from an IP address (obviously this depends | |
400 | +on the site, there might be legitimate reasons you would get | |
401 | 401 | many connections to ssh from the same IP address...) |
402 | 402 | |
403 | 403 | See example files in scripts/fail2ban. |
404 | 404 |
Built with git-ssb-web