From db5e302519ef3f63cd90548526ae2f652f74fe7a Mon Sep 17 00:00:00 2001 From: Linus Nordberg Date: Fri, 6 Oct 2017 08:58:49 +0200 Subject: Regenerate doc, for the double backslash fix in realm regexps. --- doc/1.6/radsecproxy-hash.html | 14 ++++----- doc/1.6/radsecproxy.conf.html | 70 ++++++++++++++++++++----------------------- doc/1.6/radsecproxy.html | 21 +++++++------ 3 files changed, 50 insertions(+), 55 deletions(-) (limited to 'doc/1.6') diff --git a/doc/1.6/radsecproxy-hash.html b/doc/1.6/radsecproxy-hash.html index c734e78..a59dbc7 100644 --- a/doc/1.6/radsecproxy-hash.html +++ b/doc/1.6/radsecproxy-hash.html @@ -1,5 +1,5 @@ - - + + @@ -50,8 +50,8 @@ -

radsecproxy-hash [−h] -[−k key] [−t type]

+

radsecproxy-hash [-h] [-k key] +[-t type]

@@ -77,7 +77,7 @@ input.

-

−h

+

-h

@@ -90,7 +90,7 @@ input.

-

−k key

+

-k key

@@ -100,7 +100,7 @@ input.

-

−t type

+

-t type

print digest of type TYPE [hash|hmac]

diff --git a/doc/1.6/radsecproxy.conf.html b/doc/1.6/radsecproxy.conf.html index 519c54c..beec50b 100644 --- a/doc/1.6/radsecproxy.conf.html +++ b/doc/1.6/radsecproxy.conf.html @@ -1,5 +1,5 @@ - - + + @@ -42,7 +42,7 @@

radsecproxy.conf -− Radsec proxy configuration file

+- Radsec proxy configuration file

DESCRIPTION @@ -54,8 +54,8 @@ server starts, it will first check the command line arguments, and then read the configuration file. Normally radsecproxy will read the configuration file /usr/local/etc/radsecproxy.conf. The command line -−c option can be used to instead read an -alternate file (see radsecproxy(1) for details).

+-c option can be used to instead read an alternate +file (see radsecproxy(1) for details).

If the configuration file can not be found, the proxy will exit @@ -157,8 +157,8 @@ PidFile

The PidFile option specifies the name of a file to which the process id (PID) will be -written. This is overridden by the −i command -line option. There is no default value for the PidFile +written. This is overridden by the -i command line +option. There is no default value for the PidFile option.

LogLevel

@@ -167,7 +167,7 @@ option.

level. It must be set to 1, 2, 3, 4 or 5, where 1 logs only serious errors, and 5 logs everything. The default is 2 which logs errors, warnings and a few informational -messages. Note that the command line option −d +messages. Note that the command line option -d overrides this.

LogDestination

@@ -179,15 +179,14 @@ another syslog facility, or you may specify that logging should be to a particular file, not using syslog. The value must be either a file or syslog URL. The file URL is the standard one, specifying a local file that should be used. -For syslog, you must use the syntax: -x−syslog:///FACILITY where FACILITY must be one of -LOG_DAEMON, LOG_MAIL, LOG_USER, LOG_LOCAL0, LOG_LOCAL1, -LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6 -or LOG_LOCAL7. You may omit the facility from the URL to -specify logging to the default facility, but this is not -very useful since this is the default log destination. Note -that this option is ignored if −f is specified -on the command line.

+For syslog, you must use the syntax: x-syslog:///FACILITY +where FACILITY must be one of LOG_DAEMON, LOG_MAIL, +LOG_USER, LOG_LOCAL0, LOG_LOCAL1, LOG_LOCAL2, LOG_LOCAL3, +LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6 or LOG_LOCAL7. You may +omit the facility from the URL to specify logging to the +default facility, but this is not very useful since this is +the default log destination. Note that this option is +ignored if -f is specified on the command line.

FTicksReporting

@@ -199,10 +198,9 @@ for FTicksMAC is VendorKeyHashed which needs FTicksKey to be set.

See -radsecproxy.conf−example for details. Note that -radsecproxy has to be configured with F-Ticks support -(−−enable−fticks) for this option to have -any effect.

+radsecproxy.conf-example for details. Note that radsecproxy +has to be configured with F-Ticks support (--enable-fticks) +for this option to have any effect.

FTicksMAC

@@ -223,10 +221,9 @@ collected. How will the logs be stored, transferred and accessed?

See -radsecproxy.conf−example for details. Note that -radsecproxy has to be configured with F-Ticks support -(−−enable−fticks) for this option to have -any effect.

+radsecproxy.conf-example for details. Note that radsecproxy +has to be configured with F-Ticks support (--enable-fticks) +for this option to have any effect.

FTicksKey

@@ -237,8 +234,7 @@ the FTicksMAC option.

Note that radsecproxy has to be configured with F-Ticks support -(−−enable−fticks) for this option to have -any effect.

+(--enable-fticks) for this option to have any effect.

FTicksSyslogFacility

@@ -637,7 +633,7 @@ with a non-zero exit code. An example of a shell script resolving the DNS NAPTR records for the realm and then the SRV records for each NAPTR matching ’x-eduroam:radius.tls’ is provided in -tools/naptr−eduroam.sh. This option was added in +tools/naptr-eduroam.sh. This option was added in radsecproxy-1.3 but tends to crash radsecproxy versions earlier than 1.6.

@@ -690,14 +686,14 @@ done using this regexp on the value of the entire Username attribute. Optionally you may also have a trailing / after the regexp. So as an example, if you want to use regexp matching the domain example.com you could have a realm block -named /@example\\.com$. Optionally this can also be written -/@example\\.com$/. If you want to match all domains under -the .com top domain, you could do /@.*\\.com$. Note that -since the matching is done on the entire attribute value, -you can also use rules like /^[a−k].*@example\\.com$/ -to get some of the users in this domain to use one server, -while other users could be matched by another realm block -and use another server.

+named /@example\.com$. Optionally this can also be written +/@example\.com$/. If you want to match all domains under the +.com top domain, you could do /@.*\.com$. Note that since +the matching is done on the entire attribute value, you can +also use rules like /^[a-k].*@example\.com$/ to get some of +the users in this domain to use one server, while other +users could be matched by another realm block and use +another server.

REALM BLOCK OPTIONS
@@ -735,7 +731,7 @@ exists, while for other domains under .bv you want to send a reject. At the same time you might want to send all other requests to some default server. After the realms for the subdomains, you would then have two realm definitions. One -with the name /@.*\\.bv$ with no servers, followed by one +with the name /@.*\.bv$ with no servers, followed by one with the name * with the default server defined. This may also be useful for blocking particular usernames.

diff --git a/doc/1.6/radsecproxy.html b/doc/1.6/radsecproxy.html index 33b7468..92ff78f 100644 --- a/doc/1.6/radsecproxy.html +++ b/doc/1.6/radsecproxy.html @@ -1,5 +1,5 @@ - - + + @@ -52,9 +52,8 @@ TCP/TLS (RadSec) transport.

-

radsecproxy [−c -configfile] [−d debuglevel] [−f] [−i -pidfile] [−p] [−v]

+

radsecproxy [-c configfile] [-d +debuglevel] [-f] [-i pidfile] [-p] [-v]

DESCRIPTION @@ -103,7 +102,7 @@ use only IPv4 and some only IPv6.

-

−f

+

-f

@@ -118,7 +117,7 @@ this option, the proxy will run in foreground mode. That is, it won’t detach. Also all logging will be done to stderr.

-

−d <debug +

-d <debug level>

Debug @@ -137,7 +136,7 @@ messages.

-

−p

+

-p

@@ -162,7 +161,7 @@ running.

-

−v

+

-v

@@ -176,7 +175,7 @@ running.

option is specified, the proxy will simply print version information and exit.

-

−c <config file +

-c <config file path>

Config file @@ -187,7 +186,7 @@ allows you to specify which config file to use. This is useful if you want to use a config file that is not in any of the default locations.

-

−i <pid file +

-i <pid file path>

PID file -- cgit v1.1