third-party-mirrors/sslh
1
0
Fork 0
mirror of https://github.com/yrutschle/sslh.git synced 2025-06-01 16:11:16 +03:00
Code Issues Packages Projects Releases Wiki Activity

add mention of sslh-ev

Browse Source
This commit is contained in:
Yves Rűtschlé 2022-07-21 18:24:36 +02:00
parent 7b923f793e
commit 5168fe081a
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/INSTALL.md
View File

@ -78,8 +78,8 @@ of the Makefile:
Binaries Binaries
-------- --------
The Makefile produces two different executables: `sslh-fork` The Makefile produces three different executables: `sslh-fork`,
and `sslh-select`: `sslh-select` and `sslh-ev`:
* `sslh-fork` forks a new process for each incoming connection. * `sslh-fork` forks a new process for each incoming connection.
It is well-tested and very reliable, but incurs the overhead It is well-tested and very reliable, but incurs the overhead
@ -88,18 +88,17 @@ If you are going to use `sslh` for a "small" setup (less than
a dozen ssh connections and a low-traffic https server) then a dozen ssh connections and a low-traffic https server) then
`sslh-fork` is probably more suited for you. `sslh-fork` is probably more suited for you.
* `sslh-select` uses only one thread, which monitors all connections * `sslh-select` uses only one thread, which monitors all
at once. It is more recent and less tested, but only incurs a 16 connections at once. It only incurs a 16 byte overhead per
byte overhead per connection. Also, if it stops, you'll lose all connection. Also, if it stops, you'll lose all connections,
connections, which means you can't upgrade it remotely. which means you can't upgrade it remotely. If you are going
If you are going to use `sslh` on a "medium" setup (a few thousand ssh to use `sslh` on a "medium" setup (a few hundreds of
connections, and another few thousand ssl connections), connections), or if you are on a system where forking is
`sslh-select` will be better. expensive (e.g. Windows), `sslh-select` will be better.
If you have a very large site (tens of thousands of connections),
you'll need a vapourware version that would use libevent or
something like that.
* `sslh-ev` is similar to `sslh-select`, but uses `libev` as
a backend. This allows using specific kernel APIs that
allow to manage thousands of connections concurrently.
Installation Installation
------------ ------------