From bde15e660005e50ff77c5832c9993275ac1d96c0 Mon Sep 17 00:00:00 2001 From: Linus Nordberg Date: Tue, 27 Sep 2011 19:48:12 +0200 Subject: Add F-Ticks documentation to radsecproxy.conf.5. --- radsecproxy.conf.5.xml | 37 +++++++++++++++++++++++++++++++------ 1 file changed, 31 insertions(+), 6 deletions(-) (limited to 'radsecproxy.conf.5.xml') diff --git a/radsecproxy.conf.5.xml b/radsecproxy.conf.5.xml index 16b0413..bfc701e 100644 --- a/radsecproxy.conf.5.xml +++ b/radsecproxy.conf.5.xml @@ -173,8 +173,15 @@ blocktype name { FTicksReporting - TODO! (See radsecproxy.conf-example - for now.) + The FTicksReporting option is used to enable F-Ticks + logging and can be set to None, + Basic or Full. Its + default value is None. + + See radsecproxy.conf-example for + details. Note that radsecproxy has to be configured with + support for F-Ticks (--enable-fticks) + for this option to have any effect. @@ -183,8 +190,20 @@ blocktype name { FTicksMAC - TODO! (See radsecproxy.conf-example - for now.) + The FTicksMAC option can be used to control if and how + Calling-Station-Id is being logged. It can be set to one + of Static, Original, + VendorHashed, + VendorKeyHashed, + FullyHashed or + FullyKeyHashed. + + Its default value is Static. + + See radsecproxy.conf-example for + details. Note that radsecproxy has to be configured with + support for F-Ticks (--enable-fticks) + for this option to have any effect. @@ -193,8 +212,14 @@ blocktype name { FTicksKey - TODO! (See radsecproxy.conf-example - for now.) + The FTicksKey option is used to specify the key to use + when producing HMAC's as an effect of specifying + VendorKeyHashed or FullyKeyHashed for the FTicksMAC + option. + + Note that radsecproxy has to be configured with support + for F-Ticks (--enable-fticks) for this + option to have any effect. -- cgit v1.1