Re: [RADIATOR] Feature request - Different encryption methods in AuthBy UNIX
Hi, > On 04 Nov 2015, at 00:30, Johnson, Neil M wrote: > > Yes it does. > > Hmm. I must of mistyped a password somewhere. > Ack. > Sorry. > No problem, were you able to get it to work? BR -- Tuure Vartiainen Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Feature request - Different encryption methods in AuthBy UNIX
Yes it does.
Hmm. I must of mistyped a password somewhere.
Sorry.
-Neil
--
Neil Johnson
Network Engineer
The University of Iowa
Phone: 319 384-0938
Fax: 319 335-2951
E-Mail: neil-john...@uiowa.edu
> On Nov 2, 2015, at 2:08 PM, varti...@open.com.au wrote:
>
> Hi
>
> On Monday, 2 November, 2015 20:09, "Johnson, Neil M"
> said:
>
>> Radiator 4.16 on the test box and Radiator 4.13 in production.
>>
>> It appears the password is in SHA-512 format ($6$ prefix), but it didn’t
>> work on the test box until I ran a python script uses the following line to
>> encrypt the password:
>>
>> encrypted_password = crypt.crypt(raw_passwd1, salt=crypt.METHOD_SHA512)
>>
>> And then manually copied it into the /etc/shadow file.
>>
>> Here is the password entry for a dummy account I created on the test box:
>>
>> $6$rMzuK3lt$OTG.nVZjYW6E4jWjQJ3DVQgpEPoSSy6p6b34p1nx5w3b7NKfTAWKKF0xvUGPeiM9PLSc3z83uD8JcKzzjU6951
>>
>> password is “fredsmed"
>>
>
> I'm unable to reproduce the problem with Radiator 4.16 on Ubuntu 14.04 box
> using AuthBy UNIX or FILE
> with the SHA-512 hash above.
>
> Does the following Perl script print the same hash twice on the test box?
>
> use strict;
> use warnings;
>
> my $pw =
> '$6$rMzuK3lt$OTG.nVZjYW6E4jWjQJ3DVQgpEPoSSy6p6b34p1nx5w3b7NKfTAWKKF0xvUGPeiM9PLSc3z83uD8JcKzzjU6951';
> my $submitted_pw = "fredsmed";
>
> if ($pw =~ /^\$[56]\$.+\$/) {
>print $pw . "\n";
>print crypt($submitted_pw, $pw) . "\n";
> }
>
>
> BR
> --
> Tuure Vartiainen
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
> DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
> NetWare etc.
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Feature request - Different encryption methods in AuthBy UNIX
Hi
On Monday, 2 November, 2015 20:09, "Johnson, Neil M"
said:
> Radiator 4.16 on the test box and Radiator 4.13 in production.
>
> It appears the password is in SHA-512 format ($6$ prefix), but it didn’t
> work on the test box until I ran a python script uses the following line to
> encrypt the password:
>
> encrypted_password = crypt.crypt(raw_passwd1, salt=crypt.METHOD_SHA512)
>
> And then manually copied it into the /etc/shadow file.
>
> Here is the password entry for a dummy account I created on the test box:
>
> $6$rMzuK3lt$OTG.nVZjYW6E4jWjQJ3DVQgpEPoSSy6p6b34p1nx5w3b7NKfTAWKKF0xvUGPeiM9PLSc3z83uD8JcKzzjU6951
>
> password is “fredsmed"
>
I'm unable to reproduce the problem with Radiator 4.16 on Ubuntu 14.04 box
using AuthBy UNIX or FILE
with the SHA-512 hash above.
Does the following Perl script print the same hash twice on the test box?
use strict;
use warnings;
my $pw =
'$6$rMzuK3lt$OTG.nVZjYW6E4jWjQJ3DVQgpEPoSSy6p6b34p1nx5w3b7NKfTAWKKF0xvUGPeiM9PLSc3z83uD8JcKzzjU6951';
my $submitted_pw = "fredsmed";
if ($pw =~ /^\$[56]\$.+\$/) {
print $pw . "\n";
print crypt($submitted_pw, $pw) . "\n";
}
BR
--
Tuure Vartiainen
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Feature request - Different encryption methods in AuthBy UNIX
Radiator 4.16 on the test box and Radiator 4.13 in production. It appears the password is in SHA-512 format ($6$ prefix), but it didn’t work on the test box until I ran a python script uses the following line to encrypt the password: encrypted_password = crypt.crypt(raw_passwd1, salt=crypt.METHOD_SHA512) And then manually copied it into the /etc/shadow file. Here is the password entry for a dummy account I created on the test box: $6$rMzuK3lt$OTG.nVZjYW6E4jWjQJ3DVQgpEPoSSy6p6b34p1nx5w3b7NKfTAWKKF0xvUGPeiM9PLSc3z83uD8JcKzzjU6951 password is “fredsmed" -Neil -- Neil Johnson Network Engineer The University of Iowa Phone: 319 384-0938 Fax: 319 335-2951 E-Mail: neil-john...@uiowa.edu > On Nov 2, 2015, at 1:33 AM, Tuure Vartiainen wrote: > > Hi, > >> On 30 Oct 2015, at 20:32, Johnson, Neil M wrote: >> >> For instance I’m testing RADIATOR on an Ubuntu Server and >> doesn’t work because the Ubuntu uses a different hash/encryption method in >> their /etc/shadow file. >> >> If I manually encrypt the password with the same method as used by >> and put it in the /etc/shadow file it will then work, but that >> means that users can’t change their passwords from the command prompt. >> > > what version of Radiator are you running and which password encryption method > are you using? > > Since Radiator 4.13 there has been a support for e.g. SHA-512 passwords > (“$6$” prefix in shadow file). > > AuthBy UNIX supports all the same password formats which Radiator suppports. > > > BR > -- > Tuure Vartiainen > > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, > Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, > TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, > DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, > NetWare etc. > ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Feature request - Different encryption methods in AuthBy UNIX
Hi, > On 30 Oct 2015, at 20:32, Johnson, Neil M wrote: > > For instance I’m testing RADIATOR on an Ubuntu Server and > doesn’t work because the Ubuntu uses a different hash/encryption method in > their /etc/shadow file. > > If I manually encrypt the password with the same method as used by > and put it in the /etc/shadow file it will then work, but that > means that users can’t change their passwords from the command prompt. > what version of Radiator are you running and which password encryption method are you using? Since Radiator 4.13 there has been a support for e.g. SHA-512 passwords (“$6$” prefix in shadow file). AuthBy UNIX supports all the same password formats which Radiator suppports. BR -- Tuure Vartiainen Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
RE: (RADIATOR) Feature request: Multifunctional radpwtst
You can do this right now using the correct command line options. Here is what I use to send Accounting-Alives with radpwtst -> radpwtst -secret mysecret -noauth -noacct -trace -code Accounting-Request Acct-Status-Type=Alive Calling-Station-Id=5551212 Called-Station-Id=5551234 Acct-Session-Id=1234556 Class=someclass Acct-Session-Time=X Where X is the amount of time elapsed for the session so far. You will most likely need to use a different set of attributes depending on what you are trying to test. Frank Danielson [Infrastructure Architect] voice:407.515.8633 fax:407.515.9001 ClearSky Mobile Media, Inc. 56 E. Pine St. Suite 200 Orlando, FL 32801 USA -Original Message- From: Karel van der Velden [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 10:26 AM To: [EMAIL PROTECTED] Subject: (RADIATOR) Feature request: Multifunctional radpwtst Hello, The present radpwtst is focussed to sending radius requests for a dial environment (eg. it default sends called-station-id and calling-station-id). We would like to see the utility extended so it will be able to send radius accounting alive packets. Presently we are rebuilding it ourselves, but it would be convenient to have this within the product itself. With kind regards, Karel van der Velden Postbus 28129 3828 ZJ Amersfoort / Groningen Tel: 050-5881003 Bgg Tel: 030-6588500 Fax: 033-4513101 E-mail: [EMAIL PROTECTED] === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature request for AuthBy LDAP2
Hello Jeremy, Hello Dan - Thanks for pointing this out - an oversight on our part. Mike will add the relevant section to the manual for the next release. regards Hugh On Fri, 21 Jun 2002 02:00, Jeremy Hinton wrote: > Ask and ye shall recieve. Undocumented parameter i found in > AuthLDAP2.pm - NoBindBeforeOp. If i understand you right, adding that to > your clause should do what you are looking for. I dont know > if its available in LDAP or LDAPSDK. > > - jeremy > > On Thu, 20 Jun 2002, Dan Melomedman wrote: > > Also this is laterally related, but why does Radiator bind on every LDAP > > search while keeping the connection open? Not everyone's configuration > > needs to bind as a different user for each LDAP search. I wish there was > > an option to only bind once after connection open, so that LDAP server > > isn't hammered as much. Thanks. > > > > > > -- > > It takes a lot of hard work to make something easy. Then when > > you're done, people look at it and ask, "Oh, it's so simple; what was > > the big deal?" -Ralph Johnson > > // Jeremy HintonVisiNet > // [EMAIL PROTECTED] NOC Manager > // I've wrestled with reality for 35 years, doctor, > // and I'm happy to state I finally won out over it. -Elwood P Dowd > > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hello Bruno - The Trace parameter is a global parameter and PacketTrace is a per-module parameter. Here is an extract from the Radiator 3.0 history file: Client, Realm, Handler, and AuthBy clauses now all support a PacketTrace parameter that can turn up the trace level for packets passing 'through' that clause. regards Hugh On Tue, 19 Mar 2002 03:50, Bruno Tiago Rodrigues wrote: > Hugh, > > about the per-handler debug level... how exactly is this feature > accomplished? > and how does PacketTrace work on 3.0? are these related? > > -B > > > - Original Message - > From: "Hugh Irvine" <[EMAIL PROTECTED]> > To: "peter moody" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Friday, March 15, 2002 12:27 AM > Subject: Re: (RADIATOR) feature request > > > Hello Peter - > > > > This is already in Radiator 3.0. You should also have a look at our new > > (extra cost) product called Radar that will be released at the same time > > as > > > Radiator 3.0. > > > > > I was wondering if it was possible to have per-handler debug levels. > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Bruno Tiago Rodrigues wrote: > Hugh, > > about the per-handler debug level... how exactly is this feature > accomplished? just a guess, but it would make sense that you would have a "Trace" directive that you could put within . At least, that's sort of what I was expecting. -peter -- Peter Moody Systems Administrator [EMAIL PROTECTED] :wq === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hugh, about the per-handler debug level... how exactly is this feature accomplished? and how does PacketTrace work on 3.0? are these related? -B - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "peter moody" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, March 15, 2002 12:27 AM Subject: Re: (RADIATOR) feature request > > Hello Peter - > > This is already in Radiator 3.0. You should also have a look at our new > (extra cost) product called Radar that will be released at the same time as > Radiator 3.0. > > I was wondering if it was possible to have per-handler debug levels. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hello Leon - Thanks for your interest in Radar. I will send you a copy of Mike's beta-test announcement separately. regards Hugh On Sat, 16 Mar 2002 01:52, Leon Oosterwijk wrote: > Can you tell us what radar does? And why we should buy it? :) > > Sincerely, > > Leon Oosterwijk > ISDN-NET Inc. > www.isdn.net > +1 615-221-4200 > > > -Original Message- > > From: Hugh Irvine [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, March 14, 2002 8:41 PM > > To: peter moody; [EMAIL PROTECTED] > > Subject: Re: (RADIATOR) feature request > > > > > > > > Hello Peter - > > > > There are no upgrade costs for Radiator, you can download new > > versions from > > the web site with your existing username and password. > > > > Radar on the other hand is a new product and will be priced > > separately. > > > > regards > > > > Hugh > > > > On Fri, 15 Mar 2002 11:55, peter moody wrote: > > > Hugh Irvine wrote: > > > > This is already in Radiator 3.0. You should also have a > > > > look at our > > > > > > new > > > > > > just out of curiosity, what are the upgrade costs? > > > > > > -peter > > > > -- > > Radiator: the most portable, flexible and configurable RADIUS > > server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, > > NT, MacOS X. > > - > > Nets: internetwork inventory and management - graphical, > > extensible, flexible with hardware, software, platform and > > database independence. === Archive at > > http://www.open.com.au/archives/radiator/ > > Announcements on > > [EMAIL PROTECTED] > > To unsubscribe, email '[EMAIL PROTECTED]' with > > 'unsubscribe radiator' in the body of the message. > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) feature request
Can you tell us what radar does? And why we should buy it? :) Sincerely, Leon Oosterwijk ISDN-NET Inc. www.isdn.net +1 615-221-4200 > -Original Message- > From: Hugh Irvine [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 14, 2002 8:41 PM > To: peter moody; [EMAIL PROTECTED] > Subject: Re: (RADIATOR) feature request > > > > Hello Peter - > > There are no upgrade costs for Radiator, you can download new > versions from > the web site with your existing username and password. > > Radar on the other hand is a new product and will be priced > separately. > > regards > > Hugh > > > On Fri, 15 Mar 2002 11:55, peter moody wrote: > > Hugh Irvine wrote: > > > This is already in Radiator 3.0. You should also have a > look at our > > > new > > > > just out of curiosity, what are the upgrade costs? > > > > -peter > > -- > Radiator: the most portable, flexible and configurable RADIUS > server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, > NT, MacOS X. > - > Nets: internetwork inventory and management - graphical, > extensible, flexible with hardware, software, platform and > database independence. === Archive at > http://www.open.com.au/archives/radiator/ > Announcements on > [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hello Peter - There are no upgrade costs for Radiator, you can download new versions from the web site with your existing username and password. Radar on the other hand is a new product and will be priced separately. regards Hugh On Fri, 15 Mar 2002 11:55, peter moody wrote: > Hugh Irvine wrote: > > This is already in Radiator 3.0. You should also have a look at our new > > just out of curiosity, what are the upgrade costs? > > -peter -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hugh Irvine wrote: > This is already in Radiator 3.0. You should also have a look at our new just out of curiosity, what are the upgrade costs? -peter -- Peter Moody Systems Administrator [EMAIL PROTECTED] :wq === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request
Hello Peter - This is already in Radiator 3.0. You should also have a look at our new (extra cost) product called Radar that will be released at the same time as Radiator 3.0. regards Hugh On Fri, 15 Mar 2002 10:45, peter moody wrote: > Hugh, > I was wondering if it was possible to have per-handler debug levels. > I ask b/c I've currently got about 40 handlers (realms, > acct-status-type, etc), and log files tend to get really big when I'm > only interested in output for a certain handler or group of handlers. > included in 3.0 :) ? > > thanks. > > -peter -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request - Shutdown hook
Thanks for the patch, Hugh. It worked a treat. It's nice knowing that it will go into the official distribution aswell. Cheers, Rob. begin Hugh Irvine quotation: > Hello Rob - > > How are you going to initiate the shutdown? If it is by sending a signal, you > could use a different signal first, such as a SIGHUP or a SIGWINCH, and use > either a StartupHook (checking the parameter passed), or use a WINCHHook. > > In any case, it is easy enough to add a ShutdownHook, so I will do that in a > minute and I'll send you the patches (and I'll also send them to Mike so he > can add the code to the distribution for the next release). > > BTW - the reason there isn't such a thing already is simply because no-one > has asked for it before. > > cheers > > Hugh -- When one realizes that life is worthless, one either commits suicide or travels. Edward Dahlberg === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request - Shutdown hook
> In any case, it is easy enough to add a ShutdownHook, so I will do that > in a minute and I'll send you the patches (and I'll also send them to > Mike so he can add the code to the distribution for the next release). > This is *exactly* why you guys rule and why your software and support remains top knotch! Where else can you have a public forum with direct access to the developers who actually care enough to read and respond to EVERY SINGLE MESSAGE. It's unreal! Kudos to you guys -- keep up the excellent work. John === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request - Shutdown hook
Hello Rob - How are you going to initiate the shutdown? If it is by sending a signal, you could use a different signal first, such as a SIGHUP or a SIGWINCH, and use either a StartupHook (checking the parameter passed), or use a WINCHHook. In any case, it is easy enough to add a ShutdownHook, so I will do that in a minute and I'll send you the patches (and I'll also send them to Mike so he can add the code to the distribution for the next release). BTW - the reason there isn't such a thing already is simply because no-one has asked for it before. cheers Hugh On Tuesday 25 September 2001 13:12, Robert Thomson wrote: > I have an in-memory hash that I'm wanting to flush to disk on shutdown. > > Ideally, this would be in a shutdown hook. > > Or is there a recommended way to achieve such things, given the apparent > lack (perhaps just to me) of a shutdown hook? > > Cheers, > Rob. > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request
Hello Chris - Radiator is single-threaded, so it only ever handles a single request. regards Hugh At 8:37 AM -0600 6/22/01, Chris Given wrote: >Im not sure how radiator internally works, but I was wondering if it would >be possible to send a "batch" of all the current authentication requests >waiting up to a database server (Using XML) and return a "result set" of >there attributes. > >Something like this > >Auth Query : EXEC some_radius_authentication_procedure >@UsersXML='Username="user2 Password="pass2" />' > >Response from database server would be a result set with info for all users >it could find in @UsersXML, im not sure how many database servers support >sending XML into a query like this, but Microsoft SQL Server 2000 does. > >=== >Archive at http://www.open.com.au/archives/radiator/ >Announcements on [EMAIL PROTECTED] >To unsubscribe, email '[EMAIL PROTECTED]' with >'unsubscribe radiator' in the body of the message. -- NB: I am travelling this week, so there may be delays in our correspondence. Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature request : support StripFromReply in
Hello Christophe - There is similar functionality to this in one of the example hooks in the file "goodies/hooks.txt" in the Radiator distribution. It would be pretty simple to modify an example to do what you require. Have a look and if you have any questions just ask. cheers Hugh On Sat, 30 Sep 2000, Christophe Wolfhugel wrote: > Does it make sense to support this option (and this probably means > things like AddToReply) in client definitions ? > > Rationale : in a LAC/LNS environment, the L2TP parameters shall only > be sent to the LAC. With a current Radiator system, having different > replies requires to setup different handlers, ie : > > > stuff for the LNS > > > if not a LNS, then probably a LAC > > > I would find it easier to have : > > > Secret blah > SripFromReply Tunnel-Type, Tunnel-Server-Endpoint, ... > > > Side effect (or Cisco bug ?) : with IOS 12.1.3, the Cisco Radius > accounting packet from the LNS does not return NAS-Port-Type=Virtual > anymore, but send back the Port Type received from the LAC. > > -- > Christophe Wolfhugel -+- [EMAIL PROTECTED] -+- France Telecom Transpac > > === > Archive at http://www.starport.net/~radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request: AddToReply
Hello David - On Fri, 16 Jun 2000, David Lloyd wrote: > It would be really nice if I could use special formatting characters in my > AddToReply, for instance: > > AddToReply User-Name="%U" > > Any thoughts? > In looking at the code (AuthGeneric.pm), I see that AddToReplyIfNotExist calls the substitution routine "format_special", so you could try that. Otherwise, I think a Hook that calls "format_special" would be the way to go. regards Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Feature Request
>Yes. This is because the "Group = user" check item only has >relevance in your >AuthBy SYSTEM clause (or AuthBy UNIX). It doesn't have any >relevance in an >AuthBy FILE as you have it constructed above. (I think this is >my fault from >the example I sent you). Ok, that explains the behavior I was seeing. >What are you trying to have happen? I've lost track of what your exact >requirement is - so if you could refresh my memory I'd appreciate it. To answer your question: I am looking for a way to set default check-items for all users. You suggested I use nested Authby FILE statements and add a file to contain these(using a DEFAULT entry). I want to set a check-item of 'Group=user'. >From what you said I gather that this item needs to be in the file where the 'Authby=System' item is(my main USERS file). But this is what I am trying to avoid.() It's no big deal. The manual doesn't really state where the 'Group=xx' is valid, so I assumed everywhere. So I have the answer I was looking for. Thank you. Erik >Hello Erik - > >On Tue, 04 Jan 2000, Erik Meitner wrote: > >> >> Here is how I have my AuthBy's setup(minus extra junk): >> >> >> Identifier System >> >> >> #main users file >> >> NoDefaultIfFound >>Identifier MainUser >> Filename %D/users >> >> >> >> AcctLogFileName %L/detail >> >>Filename %D/users-def >> >> >> >> users-def file: >> DEFAULT Auth-Type=MainUsers, Group = user >> >> users file: >> DEFAULT Auth-Type = System >> User-Service = Framed-User, >> Ascend-Idle-Limit = 3600 >> >> >> emeitner Auth-Type = System, Time = "Al0600-1800" >> User-Service = Framed-User, >> Ascend-Idle-Limit = 3600 >> >> If users-def file is changed to: >> DEFAULT Auth-Type=System, Group = user >> >> it will work. >> > >Yes. This is because the "Group = user" check item only has >relevance in your >AuthBy SYSTEM clause (or AuthBy UNIX). It doesn't have any >relevance in an >AuthBy FILE as you have it constructed above. (I think this is >my fault from >the example I sent you). > >What are you trying to have happen? I've lost track of what your exact >requirement is - so if you could refresh my memory I'd appreciate it. > >thanks for your patience > >Hugh > === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Feature Request
Hello Erik - On Tue, 04 Jan 2000, Erik Meitner wrote: > > Here is how I have my AuthBy's setup(minus extra junk): > > > Identifier System > > > #main users file > > NoDefaultIfFound > Identifier MainUser > Filename %D/users > > > > AcctLogFileName %L/detail > >Filename %D/users-def > > > > users-def file: > DEFAULT Auth-Type=MainUsers, Group = user > > users file: > DEFAULT Auth-Type = System > User-Service = Framed-User, > Ascend-Idle-Limit = 3600 > > > emeitner Auth-Type = System, Time = "Al0600-1800" > User-Service = Framed-User, > Ascend-Idle-Limit = 3600 > > If users-def file is changed to: > DEFAULT Auth-Type=System, Group = user > > it will work. > Yes. This is because the "Group = user" check item only has relevance in your AuthBy SYSTEM clause (or AuthBy UNIX). It doesn't have any relevance in an AuthBy FILE as you have it constructed above. (I think this is my fault from the example I sent you). What are you trying to have happen? I've lost track of what your exact requirement is - so if you could refresh my memory I'd appreciate it. thanks for your patience Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Feature Request
Hugh said: > >The Identifier and the Auth-Type must agree. > Hi, That is just a typo in my message. Sorry. Erik >Hello Erik - > >On Tue, 04 Jan 2000, Erik Meitner wrote: > >> Here is how I have my AuthBy's setup(minus extra junk): >> >> >> Identifier System >> >> >> #main users file >> >> NoDefaultIfFound >>Identifier MainUser >> Filename %D/users >> >> >> >> AcctLogFileName %L/detail >> >>Filename %D/users-def >> >> >> >> users-def file: >> DEFAULT Auth-Type=MainUsers, Group = user >> >> users file: >> DEFAULT Auth-Type = System >> User-Service = Framed-User, >> Ascend-Idle-Limit = 3600 >> >> >> emeitner Auth-Type = System, Time = "Al0600-1800" >> User-Service = Framed-User, >> Ascend-Idle-Limit = 3600 >> >> If users-def file is changed to: >> DEFAULT Auth-Type=System, Group = user >> > >Note your spellings: > >> >> NoDefaultIfFound >>Identifier MainUser >> Filename %D/users >> > >> users-def file: >> DEFAULT Auth-Type=MainUsers, Group = user >> > >The Identifier and the Auth-Type must agree. > === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Feature Request
Hello Erik - On Tue, 04 Jan 2000, Erik Meitner wrote: > Here is how I have my AuthBy's setup(minus extra junk): > > > Identifier System > > > #main users file > > NoDefaultIfFound > Identifier MainUser > Filename %D/users > > > > AcctLogFileName %L/detail > >Filename %D/users-def > > > > users-def file: > DEFAULT Auth-Type=MainUsers, Group = user > > users file: > DEFAULT Auth-Type = System > User-Service = Framed-User, > Ascend-Idle-Limit = 3600 > > > emeitner Auth-Type = System, Time = "Al0600-1800" > User-Service = Framed-User, > Ascend-Idle-Limit = 3600 > > If users-def file is changed to: > DEFAULT Auth-Type=System, Group = user > Note your spellings: > > NoDefaultIfFound > Identifier MainUser > Filename %D/users > > users-def file: > DEFAULT Auth-Type=MainUsers, Group = user > The Identifier and the Auth-Type must agree. cheers Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Feature Request
Hugh: >Hello Erik - > >On Thu, 23 Dec 1999, Erik Meitner wrote: >> >> It would be nice to have an option that allows one to add >a check-item to >> every authentication request, much like how AddToReply works. ie: >> >> >> Filename %D/users >> AddToCheck Group=user >> >> > >You can already do this with cascaded AuthBy's, something like this: > ># create an AuthBy FILE with Identifier Users > > > Identifier Users > Filename %D/users > > ># your normal Handler > > > > Filename %D/groups > > > > >Then in your file %D/groups you would have the following: > ># check groups then refer to users file via the Identifier > >DEFAULTGroup = user, Auth-Type = Users > > >And of course your existing users file would remain the same. > >The advantage of this approach is that it is generalised and >AuthBy's can be >nested to any depth (and any AuthBy method can be used). > >hth > >Hugh Hmm. Something is not working. A 'Group' check item seems to only work in the file where 'Auth-Type=System' is used. The log for the following configuration: Wed Dec 29 14:50:03 1999: DEBUG: Reading users file /usr/local/etc/raddb/users Wed Dec 29 14:50:03 1999: DEBUG: Reading users file /usr/local/etc/raddb/users-def Wed Dec 29 14:50:03 1999: INFO: Server started Wed Dec 29 14:50:10 1999: DEBUG: Handling request with Handler 'Realm=DEFAULT' Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Deleting session for emeitner, 203.63.154.1, 1234 Wed Dec 29 14:50:10 1999: DEBUG: Handling with Radius::AuthFILE Wed Dec 29 14:50:10 1999: DEBUG: Radius::AuthFILE looks for match with emeitner Wed Dec 29 14:50:10 1999: DEBUG: Radius::AuthFILE looks for match with DEFAULT Wed Dec 29 14:50:10 1999: DEBUG: Handling with Radius::AuthFILE Wed Dec 29 14:50:10 1999: DEBUG: Radius::AuthFILE looks for match with emeitner Wed Dec 29 14:50:10 1999: WARNING: This AuthBy does not know how to check Group membership Wed Dec 29 14:50:10 1999: DEBUG: Radius::AuthFILE REJECT: User emeitner is not in Group user Wed Dec 29 14:50:10 1999: DEBUG: Radius::AuthFILE REJECT: User emeitner is not in Group user Wed Dec 29 14:50:10 1999: INFO: Access rejected for emeitner: User emeitner is not in Group user Wed Dec 29 14:50:10 1999: DEBUG: Handling request with Handler 'Realm=DEFAULT' Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Adding session for emeitner, 203.63.154.1, 1234 Wed Dec 29 14:50:10 1999: DEBUG: Handling with Radius::AuthFILE Wed Dec 29 14:50:10 1999: DEBUG: Accounting accepted Wed Dec 29 14:50:10 1999: DEBUG: Handling request with Handler 'Realm=DEFAULT' Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Rewrote user name to emeitner Wed Dec 29 14:50:10 1999: DEBUG: Deleting session for emeitner, 203.63.154.1, 1234 Wed Dec 29 14:50:10 1999: DEBUG: Handling with Radius::AuthFILE Wed Dec 29 14:50:10 1999: DEBUG: Accounting accepted Here is how I have my AuthBy's setup(minus extra junk): Identifier System #main users file NoDefaultIfFound Identifier MainUser Filename %D/users AcctLogFileName %L/detail Filename %D/users-def users-def file: DEFAULT Auth-Type=MainUsers, Group = user users file: DEFAULT Auth-Type = System User-Service = Framed-User, Ascend-Idle-Limit = 3600 emeitner Auth-Type = System, Time = "Al0600-1800" User-Service = Framed-User, Ascend-Idle-Limit = 3600 If users-def file is changed to: DEFAULT Auth-Type=System, Group = user it will work. Thanks. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request
At 09:55 23/12/99 +1100, Hugh Irvine wrote: ># create an AuthBy FILE with Identifier Users > > > Identifier Users > Filename %D/users > > ># your normal Handler > > > > Filename %D/groups > > Is there a way I can check if the group of "Perms" has been assigned in my "AuthTIC" module if I was to modify my radius.cfg as follows?? RewriteUsername s/^([^@]+).*/$1/ RewriteUsername s/^(.*)\/(.*)/$2\@$1/ RewriteUsername tr/A-Z/a-z/ RejectHasReason PasswordLogFileName %L/password.log AcctLogFileName %L/radacct/details AuthByPolicyContinueUntilReject NoDefaultIfFound *** add this line * Identifier Perms *** Filename%D/users DBSourcedbi:mysql:InterWeb DBUsername xxx DBAuth xxx AccountingTable ACCOUNTING ... columndefs removed ... AcctColumnDef CONNECTINFO,Connect-Info EncryptedPassword Simon Lindsay [EMAIL PROTECTED] Technical Manager Icq. 1485568 The Internet Company Pty. Ltd. http://www.iweb.net.au/~simon InterWeb Connections and Portal.net Ph. (08) 8221 5444 --- Speed with Service Fx. (08) 8221 5450 === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request
Hello Erik - On Thu, 23 Dec 1999, Erik Meitner wrote: > > It would be nice to have an option that allows one to add a check-item to > every authentication request, much like how AddToReply works. ie: > > > Filename %D/users > AddToCheck Group=user > > You can already do this with cascaded AuthBy's, something like this: # create an AuthBy FILE with Identifier Users Identifier Users Filename %D/users # your normal Handler Filename %D/groups Then in your file %D/groups you would have the following: # check groups then refer to users file via the Identifier DEFAULT Group = user, Auth-Type = Users And of course your existing users file would remain the same. The advantage of this approach is that it is generalised and AuthBy's can be nested to any depth (and any AuthBy method can be used). hth Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature request ?
Hi Joost, If you use %R in your log file name, it will be replaced by the users realm. Could that be useful? Cheers. --- Mike McCauley [EMAIL PROTECTED] Open System Consultants +61 3 9598 0985 Mike is travelling right now, and there may be delays in our correspondence. -Original Message- From: Joost Stegeman <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Monday, October 25, 1999 10:40 PM Subject: Re: (RADIATOR) Feature request ? >Me too! > >To be honest, I would really like to be able to log messages to a different >file for every realm/handler. We're reselling ports and this way I could show >the (relevant) errors to our customers on a webpage. They could do some more >"selfcare" and wouldn't bother our helpdesk as much. Of course the uid would be >very important too. I could probably build a filter on those in the meantime. > >- Joost. > >> In the radiator log file for trace level 3 it would be nice if on a >> failed connect the caller-id is also logged to the radiator.log file >> :-) >> >> Gary >> --- >> Ausmail >> Your virtual home on the net. >> Email, News & Home pages. >> --- >> Coming soon !! >> >> >> === >> Archive at http://www.thesite.com.au/~radiator/ >> To unsubscribe, email '[EMAIL PROTECTED]' with >> 'unsubscribe radiator' in the body of the message. > > >=== >Archive at http://www.thesite.com.au/~radiator/ >To unsubscribe, email '[EMAIL PROTECTED]' with >'unsubscribe radiator' in the body of the message. > === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature request ?
Me too! To be honest, I would really like to be able to log messages to a different file for every realm/handler. We're reselling ports and this way I could show the (relevant) errors to our customers on a webpage. They could do some more "selfcare" and wouldn't bother our helpdesk as much. Of course the uid would be very important too. I could probably build a filter on those in the meantime. - Joost. > In the radiator log file for trace level 3 it would be nice if on a > failed connect the caller-id is also logged to the radiator.log file > :-) > > Gary > --- > Ausmail > Your virtual home on the net. > Email, News & Home pages. > --- > Coming soon !! > > > === > Archive at http://www.thesite.com.au/~radiator/ > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Feature Request... Colour!
> How difficult would it be to add colour to the various Trace messages going > to the console in Radiator? You might like to look at some of the log colourizers already available, try your local freshmeat.net mirror and remember, it will probably want american spelling when you search. I'm sure you have things other than Radiator logs that would be useful to see in colour :-) === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request: AuthLogFileName and AuthLogFileFormat
Hi Bill - On Tue, 28 Sep 1999, Bill wrote: > It would be really nice to be able to format Auth request logfile > entries like we can Acct request logfile entries. This isn't on our list at the moment, but in our ample free time we'll see what we can do. BTW - the last time I asked for enhancement suggestions - the only request I got was for a cappuchino machine! (Please see http://www.gaggia.it if interested.) :~) Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request: allow include directive anywhere
Hello John - On Fri, 27 Aug 1999, John Coy wrote: > I'm looking at the docs for 2.13 and 2.14.1 side by side > and they don't look different -- 2.13 implies you can use > the "include" directive anywhere, but you cannot use it > inside of an clause (I get an error -- keyword > "include" not recognized or something like that). > > Has this behavior changed in 2.14.1 or am I doing something > wrong in my config file? > Neither one - we have fixed a bug that caused this problem. :-( There is a fixed version of AuthGeneric.pm in the patches area (2.14.1). You may want to upgrade to get the fix. thanks for pointing this problem out Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request: allow include directive anywhere
I'm looking at the docs for 2.13 and 2.14.1 side by side and they don't look different -- 2.13 implies you can use the "include" directive anywhere, but you cannot use it inside of an clause (I get an error -- keyword "include" not recognized or something like that). Has this behavior changed in 2.14.1 or am I doing something wrong in my config file? Sorry to ask all these goofy questions, but I just swung Radiator over as my primary RADIUS daemon (replacing Ascend's stock daemon) and all these things suddenly came up even though we tested this thing for about 3-4 months. John At 02:48 PM 8/27/99 +1000, you wrote: > >Hi John - > >On Fri, 27 Aug 1999, John Coy wrote: >> I'm currently using 2.13 and one feature I'd love to have >> is the use of the "include" directive anywhere within the >> configuration file (including inside an clause). >> > >Have a look at Section 6.1 in the Radiator 2.14.1 reference manual: > > >Each line in the configuration file can be one of: > > > Comment line with a `# ' as the first character. Anything including and >after the `# ' is ignored. Blank lines are also ignored. Example: > > ># This is a comment > > > An include directive. The word include followed by a filename. The named >file will be opened and read to the end as a configuration file before >processing of the current file continues. Special filename characters are >permitted (see Section 6.2 ). Files can be recursively included to any >depth. Example: > > >include %D/clients.cfg > > >> Is this a feature in 2.14.1 (I looked at the docs but >> they look the same as the 2.13 docs with respect to >> this directive). >> >> Anyhow, just some food for thought. Is there an "official" >> place to post feature requests? > >The mailing list is the best place - we very often implement what people >request - although we reserve the right to discussion. :-) > >And Mike always makes the final decision! > >hth > >Hugh > >-- >Radiator: the most portable, flexible and configurable RADIUS server >anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, >Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, >NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) feature request: allow include directive anywhere
Hi John - On Fri, 27 Aug 1999, John Coy wrote: > I'm currently using 2.13 and one feature I'd love to have > is the use of the "include" directive anywhere within the > configuration file (including inside an clause). > Have a look at Section 6.1 in the Radiator 2.14.1 reference manual: Each line in the configuration file can be one of: Comment line with a `# ' as the first character. Anything including and after the `# ' is ignored. Blank lines are also ignored. Example: # This is a comment An include directive. The word include followed by a filename. The named file will be opened and read to the end as a configuration file before processing of the current file continues. Special filename characters are permitted (see Section 6.2 ). Files can be recursively included to any depth. Example: include %D/clients.cfg > Is this a feature in 2.14.1 (I looked at the docs but > they look the same as the 2.13 docs with respect to > this directive). > > Anyhow, just some food for thought. Is there an "official" > place to post feature requests? The mailing list is the best place - we very often implement what people request - although we reserve the right to discussion. :-) And Mike always makes the final decision! hth Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
