From 380b907aa703c3bbdb9a74255c4955afda028bb4 Mon Sep 17 00:00:00 2001 From: venaas Date: Tue, 5 Jun 2007 13:05:16 +0000 Subject: [PATCH] some minor updates git-svn-id: https://svn.testnett.uninett.no/radsecproxy/trunk@128 e88ac4ed-0b26-0410-9574-a7f39faa03bf --- Makefile.am | 1 - README | 26 +++++++++++++++----------- configure.ac | 2 +- radsecproxy.conf-example | 4 ++-- 4 files changed, 18 insertions(+), 15 deletions(-) diff --git a/Makefile.am b/Makefile.am index 119021b..702e089 100644 --- a/Makefile.am +++ b/Makefile.am @@ -10,5 +10,4 @@ radsecproxy_CFLAGS = -g -Wall -pedantic -pthread @SSL_CFLAGS@ radsecproxy_LDFLAGS = @SSL_LDFLAGS@ radsecproxy_LDADD = @SSL_LIBS@ -sysconfdir = ${prefix}/etc/radsecproxy dist_sysconf_DATA = $(srcdir)/radsecproxy.conf-example diff --git a/README b/README index 995055d..f0c876a 100644 --- a/README +++ b/README @@ -1,15 +1,18 @@ -This is a beta version of a generic RADIUS proxy that can support -various RADIUS clients over UDP or TLS (RadSec). +This is a revision from the radsecproxy 1.1 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 if you like. +"make". You may also try to use autoconf, but this is currently +unsupported. -To use it you need to create a config file called -"radsecproxy.conf" which must be in /etc/radsecproxy (unless -you alter it in the header file), the current directory, or -you can specify the location with the "-c" command line -option (see below). See the enclosed example file for further -instructions. +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 +http://software.uninett.no/radsecproxy/?page=documentation There are four options that may be specified on the command line. "-c configfile" to specify a non-default config file path; @@ -27,6 +30,7 @@ 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. contact . +For more information, feedback etc. please see the information +at http://software.uninett.no/radsecproxy/ -Stig Venaas, 2007.05.24 +Stig Venaas -- 2007.06.05 diff --git a/configure.ac b/configure.ac index c5ea60d..e64e6b5 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_INIT(radsecproxy, 0.1, venaas@uninett.no) +AC_INIT(radsecproxy, 1.1-devel, venaas@uninett.no) AM_INIT_AUTOMAKE AC_PROG_CC AM_PROG_CC_C_O diff --git a/radsecproxy.conf-example b/radsecproxy.conf-example index 029c7e1..854bb95 100644 --- a/radsecproxy.conf-example +++ b/radsecproxy.conf-example @@ -124,5 +124,5 @@ realm * { #If you don't have a default server you probably want to #reject all unknowns. Optionally you can also include a message #realm * { - replymessage "User unknown" -} +# replymessage "User unknown" +#} -- 2.1.4