view doc/acl_wl.conf.sample @ 1521:996823ef481c

Rename 3GPP MBMS-Flag (931) to MBMS-Flags Note: 3GPP TS 29.061 table 20.5a.1 row MBMS-Flag (931) has incorrect name and should be "MBMS-Flags" per clause 20.5a.9. Fix: MBMS-Flag (931) renamed to MBMS-Flags (931).
author Luke Mewburn <luke@mewburn.net>
date Fri, 17 Apr 2020 14:21:19 +1000
parents 0dff6a604b0a
children
line wrap: on
line source

# Configuration file for the peer whitelist extension.
#
# This extension is meant to allow connection from remote peers, without actively
# maintaining this connection ourselves (as it would be the case by declaring the 
# peer in a ConnectPeer directive).
#
# This extension supports configuration reload at runtime. Send
# signal SIGUSR1 to the process to cause the process to reload its
# config.
#
# The format of this file is very simple. It contains a list of peer names
# separated by spaces or newlines. 
#
# The peer name must be a fqdn. We allow also a special "*" character as the
# first label of the fqdn, to allow all fqdn with the same domain name.
# Example: *.example.net will allow host1.example.net and host2.example.net
#
# At the beginning of a line, the following flags are allowed (case sensitive) -- either or both can appear:
# ALLOW_OLD_TLS : we accept unprotected CER/CEA exchange with Inband-Security-Id = TLS
# ALLOW_IPSEC   : we accept implicitly protected connection with with peer (Inband-Security-Id = IPSec)
# It is specified for example as:
# ALLOW_IPSEC vpn.example.net vpn2.example.net *.vpn.example.net
# These flag take effect from their position, until the end of the line.

"Welcome to our mercurial repository"