Hi All,
Ok, after reviewing all the information that was received, I've setup my
FreeRadius
as following:
1. The authorize and authenticate sections are setup to activate digest and
perl.
2. My rlm_perl script utilizes the following lines in order to return the
unencrypted
user password
Hi all,
Please disregard, I've solved the thing ;-) Silly typo in the return.
Z2L
- Original Message -
From: FreeRadius-ML [EMAIL PROTECTED]
To: freeradius-users freeradius-users@lists.freeradius.org
Sent: Thursday, July 26, 2007 6:41:21 PM (GMT+0200) Asia/Jerusalem
Subject: Fwd
, July 24, 2007 6:22:27 PM (GMT+0200) Asia/Jerusalem
Subject: Re: rml_perl question
FreeRadius-ML wrote:
Yes, that was the initial idea. However, $RAD_CHECK{User-Password}, at
least according to
my log file doesn't exist:
I don't understand. Did you update the Perl script to set
Ok,
What I'm trying to do is have FreeRadius perform its AAA functions again a
PERL based
backend, which reads the user information from a proprietary system - via a TCP
interface.
The authorization section and the authenticate section both have PERL enabled
in them.
(I removed the
it to FreeRADIUS
in the _authorize_ section as:
PaCleartext-ssword := yoursupersecretpassword
This is ALL you should have to do! Do not do anything else! Please. Just
dont!
Cheers
Peter
On Wed 25 Jul 2007, FreeRadius-ML wrote:
Ok,
What I'm trying to do is have FreeRadius perform its AAA
Subject: Re: rml_perl question
On Wed 25 Jul 2007, FreeRadius-ML wrote:
Hi Peter,
Thanks, that was the missing part for me - I think. Just let me verify
that I got you correctly:
1. My OpenSER will send a request to FreeRadius including the full
digest information.
2. Once the request
Hi All,
I've been tinkering with rlm_perl for a few days now, and found it to be
fairly simple
and straight forward. However, there is something that I'm a little unsure
about it's possibility,
so I would like to address the list about it.
My aim is to have my rlm_perl script connect to a
per thread.
2) perl without threads
In this case you should put your socket initialization code inside
the main body of your script.
Best Regards,
Boian Jordanov
SNE
Orbitel - Next Generation Telecom
tel. +359 2 4004 723
tel. +359 2 4004 002
On Jul 24, 2007, at 10:17 AM, FreeRadius-ML wrote
/Jerusalem
Subject: Re: rml_perl question
On Tue 24 Jul 2007, FreeRadius-ML wrote:
Thanks, that helps a bunch.
Another question, may be non related. Anyone has an idea how does OpenSER
and FreeRadius calculate the Digest response for rlm_digest?
According to the output of my rlm_perl RAD_REQUEST
unable to access
the nonce field
from rlm_perl, unless, I'm missing something.
Regards,
Z2L
- Original Message -
From: FreeRadius-ML [EMAIL PROTECTED]
To: freeradius-users freeradius-users@lists.freeradius.org
Sent: Tuesday, July 24, 2007 11:43:19 AM (GMT+0200) Asia/Jerusalem
Subject
@lists.freeradius.org
Sent: Tuesday, July 24, 2007 2:00:33 PM (GMT+0200) Asia/Jerusalem
Subject: Re: rml_perl question
On Tue, 2007-07-24 at 11:43 +0300, FreeRadius-ML wrote:
Hi Peter,
Well, according to the RFC, the string should be:
username:realm:password and then into the md5sum.
No, the digest response
:11 PM (GMT+0200) Asia/Jerusalem
Subject: Re: rml_perl question
On Tue, 2007-07-24 at 13:54 +0300, FreeRadius-ML wrote:
Ok,
It would appear that I'm a little silly, due to the way FreeRadius logs the
information
on the console. I've been debugging the information that I get, and I can see
PROTECTED], FreeRadius users mailing list
freeradius-users@lists.freeradius.org
Sent: Tuesday, July 24, 2007 5:47:36 PM (GMT+0200) Asia/Jerusalem
Subject: Re: rml_perl question
FreeRadius-ML wrote:
Now I understand you better, and I agree, that would constitute a much more
scalable method
FreeRadius-ML wrote:
I can understand now that authorize is working nicely, but the
Authentication section is wrong.
I know there's alot of shit in radiusd.conf, however, it shouldn't prevent
from the basics to work
correctly, no?
The default configuration works. The shit that's
FreeRadius-ML wrote:
I can understand now that authorize is working nicely, but the
Authentication section is wrong.
I know there's alot of shit in radiusd.conf, however, it shouldn't prevent
from the basics to work
correctly, no?
The default configuration works. The shit that's
Issue
FreeRadius-ML wrote:
Now, I'm basically re-learning everything, as the world of OpenSER +
FreeRadius is a little new to me,
and sometimes frustrates me. The amount of documentation in the configuration
files is great, but the lack
of updated examples is somewhat annoying. Even
on the OpenSER server, but i believe that is
caused by something else. Unless you have
some form of pointer tip here...
z2l
- Original Message -
From: FreeRadius-ML [EMAIL PROTECTED]
To: Alan DeKok [EMAIL PROTECTED]
Cc: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
Now, I'm basically re-learning everything, as the world of OpenSER +
FreeRadius is a little new to me,
and sometimes frustrates me. The amount of documentation in the configuration
files is great, but the lack
of updated
Hi All,
Ok, after battling with OpenSER + FreeRadius digest authentication, I managed
to make it work correctly.
Now, i've decided to try moving to rlm_perl, and I was wondering if any of you
guys may have examples or
code/configuration snips of rlm_perl integration.
I've managed to work
Ok, now we are getting somewhere, I'm getting the following output:
rad_recv: Access-Request packet from host 192.168.2.80:43835, id=102, length=234
User-Name = [EMAIL PROTECTED]
Digest-Attributes = 0x0a05313031
Digest-Attributes = 0x010e3139322e3136382e322e3830
Informatika ISP
Dana 17/7/2007, FreeRadius-ML [EMAIL PROTECTED] piše:
Ok, now we are getting somewhere, I'm getting the following output:
rad_recv: Access-Request packet from host 192.168.2.80:43835, id=102,
length=234
User-Name = [EMAIL PROTECTED]
Digest-Attributes = 0x0a05313031
:19 (GMT+0200) Asia/Jerusalem יום שלישי 17 יולי 2007
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
Well, right now I would like to start of with something really simple. I'd
like to have OpenSER authenticate
on FreeRadius, Digest is not a must - for all I care at this point, it can
יולי 2007
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
I've reached a few conclusions here, and according to the following
log I can deduce the
following:
...
auth: No authenticate method (Auth-Type) configuration found for the
request: Rejecting the user
That message would
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: [EMAIL PROTECTED], FreeRadius users mailing list
freeradius-users@lists.freeradius.org
Sent: 20:59:53 (GMT+0200) Asia/Jerusalem יום שלישי 17 יולי 2007
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
Well, the perl
users mailing list
freeradius-users@lists.freeradius.org
Sent: 21:52:47 (GMT+0200) Asia/Jerusalem יום שלישי 17 יולי 2007
Subject: Re: RLM_PERL Integration Issue
On Tue 17 Jul 2007, FreeRadius-ML wrote:
Ok,
i've modified the users file to say Cleartext-Password, and I've removed
the Auth-type
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: [EMAIL PROTECTED], FreeRadius users mailing list
freeradius-users@lists.freeradius.org
Sent: 21:31:08 (GMT+0200) Asia/Jerusalem יום שלישי 17 יולי 2007
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
1. I've removed
Hi All,
Ok, I'm a bit mixed up here, the documents are simply not cutting it.
I'm wondering if any of you have a working OpenSER + FreeRadius configuration
that I can look at and extrapulate my required settings?
I've gone over all the material I could find, but all of it reverts back
to the
27 matches
Mail list logo
