blob: 1db4328825263962476374e1f766faaf91e25f3d (plain
This is a revision from the radsecproxy 1.2 devel branch.
radsecproxy is a generic RADIUS proxy that can support various
RADIUS clients over UDP or TLS (RadSec).
It should build on most Linux and BSD platforms by simply typing
"make". You may also try to use autoconf, but this is currently
To use it you need to create a config file which normally is
called "/etc/radsecproxy.conf". If this is not found, the
proxy will look for radsecproxy.conf in the current directory.
You can also specify the location with the "-c" command line
option (see below). For further instructions, please see the
enclosed example file and the documentation at
There are five options that may be specified on the command line.
"-c configfile" to specify a non-default config file path;
"-d loglevel" to set a loglevel of 1, 2, 3 or 4 where 4 is the most
detailed; and "-f" to run the proxy in the foreground with logging
to stderr. Without "-f" the default is to detach as a daemon and
log to syslog. "-v" just prints version information and exits, while
"-p" (pretend) makes the proxy go through the configuration files as
normal, but stops before creating any sockets or doing any serious
work. This is useful for validating config files.
Thanks to Stefan Winter and Andreas Solberg for talking me into
doing this, and the funding from GEANT2. Stefan as well as Kolbj�rn
Barmen, Ralf Paffrath and Maja Wolniewicz have helped with early
testing of the code.
All of the above plus Milan Sova have provided good feedback on
several implementation choices. Finally thanks to Hans Zandbelt
for providing the autoconf stuff. I may have forgotten someone,
let me know if you feel left out.
For more information, feedback etc. please see the information
Stig Venaas <firstname.lastname@example.org> -- 2007.12.27