Re: (RADIATOR) CHAP, HOWTO
Hello Camil - At 17:53 -0500 30/11/00, Camil Samaha wrote: >This is probably documented somewhere but I am drawing a blank. I >authenticate using an SQL database where all the passwords are stored in >plaintext. Is it possible to accept CHAP authentication? If so, how? > You don't have to do anything other than have the passwords in plaintext. Radiator looks for either User-Password or CHAP-Password and does the right thing automatically. regards Hugh -- 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.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) CHAP, HOWTO
AFAIK you configure your NAS to use CHAP, then Radiator will understand what to do when the CHAP-Password etc comes. /Ingvar -Original Message- From: Camil Samaha [mailto:[EMAIL PROTECTED]] Sent: den 30 november 2000 23:53 To: [EMAIL PROTECTED] Subject: (RADIATOR) CHAP, HOWTO This is probably documented somewhere but I am drawing a blank. I authenticate using an SQL database where all the passwords are stored in plaintext. Is it possible to accept CHAP authentication? If so, how? Thanks in advance, Camil Samaha === 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. === 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) CHAP HOWTO
Hi Richi, On Jun 6, 10:30pm, Richi Plana wrote: > Subject: Re: (RADIATOR) CHAP HOWTO > Hi, Mike, et al. > > On Sun, 6 Jun 1999, Mike McCauley wrote: > > |o| > Just wondering how to check the attributes CHAP-Password and > |o| > CHAP-Challenge. Are there methods in any of the Radiator objects that > |o| > would allow ones own written AuthBy method to check this attrib? > |o| > > |o| Radius::Radius::check_plaintext_password does most of the hard > |o| work of checking a password against whatever arrived in the radius > |o| request, be it CHAP, PAPA or whatever. > > It's a good function. Works like a charm. Is there some kind of > documentation on Radius::Radius or the whole Radius module (as implemented > in Radiator)? Seems there are a lot nifty functions just waiting to be > used. The only doc of the functions is in the file itself. > > BTW, although check_plaintext_password works as advertised, it won't work > for us because it just hit me: we've stored clients' password using DES > crypt(). If Radius::Radius::check_plaintext_password can work with that, > I'd like to know how! Then you lose. Its not possible to do CHAP authentication unless you have the plaintext password available. Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 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) CHAP HOWTO
Hi, Mike, et al. On Sun, 6 Jun 1999, Mike McCauley wrote: |o| > Just wondering how to check the attributes CHAP-Password and |o| > CHAP-Challenge. Are there methods in any of the Radiator objects that |o| > would allow ones own written AuthBy method to check this attrib? |o| > |o| Radius::Radius::check_plaintext_password does most of the hard |o| work of checking a password against whatever arrived in the radius |o| request, be it CHAP, PAPA or whatever. It's a good function. Works like a charm. Is there some kind of documentation on Radius::Radius or the whole Radius module (as implemented in Radiator)? Seems there are a lot nifty functions just waiting to be used. BTW, although check_plaintext_password works as advertised, it won't work for us because it just hit me: we've stored clients' password using DES crypt(). If Radius::Radius::check_plaintext_password can work with that, I'd like to know how! L L Richi Plana 8^) ,-,-. ,-,-. ,-,-. ,-,-. ,- LL LL Systems Administrator / / \ \ / / \ \ / / \ \ / / \ \ / / L Mosaic Communications, Inc. \ \ / / \ \ / / \ \ / / \ \ / / L mailto:[EMAIL PROTECTED] `-'-' `-'-' `-'-' `-'-' === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) CHAP HOWTO
Hi Richi, On Jun 5, 3:35pm, Richi Plana wrote: > Subject: (RADIATOR) CHAP HOWTO > Hi, > > Just wondering how to check the attributes CHAP-Password and > CHAP-Challenge. Are there methods in any of the Radiator objects that > would allow ones own written AuthBy method to check this attrib? > Radius::Radius::check_plaintext_password does most of the hard work of checking a password against whatever arrived in the radius request, be it CHAP, PAPA or whatever. Thats the only function that has specific knowledge of the CHAP attributes. Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 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.
