GitLab/ocserv
1
0
Fork 0
mirror of https://gitlab.com/openconnect/ocserv.git synced 2026-02-10 08:46:58 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc update

Browse Source 
Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
This commit is contained in:
Nikos Mavrogiannopoulos
2017-04-14 11:36:34 +03:00
parent cf74746fb7
commit b2e199577d
2 changed files with 14 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/sample.config
View File

@@ -84,12 +84,15 @@ udp-port = 443
# Accept connections using a socket file. It accepts HTTP
# connections (i.e., without SSL/TLS unlike its TCP counterpart),
# and uses it as the primary channel. That option is experimental
# and it has the following known issues.
# * can only be combined with certificate authentication, by received
# information through the proxy protocol channel (see listen-proxy-proto)
# * It cannot derive any keys needed for the DTLS session (dtls-psk)
# and it has many known issues.
# * It can only be combined with certificate authentication, when receiving
# channel information through proxy protocol (see listen-proxy-proto)
# * It cannot derive any keys needed for the DTLS session (hence no support for dtls-psk)
# * It cannot enforce the framing of the SSL/TLS packets, and that
# breaks assumptions held by several openconnect clients.
# This option is not recommended for use, and may be removed
# in the future.
#
#listen-clear-file = /var/run/ocserv-conn.socket
# The user the worker processes will be run as. It should be

11
src/ocserv-args.def
View File

@@ -162,12 +162,15 @@ udp-port = 4443
# Accept connections using a socket file. It accepts HTTP
# connections (i.e., without SSL/TLS unlike its TCP counterpart),
# and uses it as the primary channel. That option is experimental
# and it has the following known issues.
# * can only be combined with certificate authentication, by received
# information through the proxy protocol channel (see listen-proxy-proto)
# * It cannot derive any keys needed for the DTLS session (dtls-psk)
# and it has many known issues.
# * It can only be combined with certificate authentication, when receiving
# channel information through proxy protocol (see listen-proxy-proto)
# * It cannot derive any keys needed for the DTLS session (hence no support for dtls-psk)
# * It cannot enforce the framing of the SSL/TLS packets, and that
# breaks assumptions held by several openconnect clients.
# This option is not recommended for use, and may be removed
# in the future.
#
#listen-clear-file = /var/run/ocserv-conn.socket
# The user the worker processes will be run as. It should be