Hey... is it possible to tell RADIATOR to listen on 1645 _AND_ 1812 for
authentication? I think it can be done pretty simply by running two
instances of RADIATOR and pointing them to different config files but I
was wondering if there was a cleaner way...
-Steve
===
Archive at
Again... you can't decrypt the password. If you could (and do it quickly
enough
to be useful) I'd be pretty scared because that implies the encryption
is way too weak.
As Mike suggested you need to setup a hook to start logging the
passwords people use to a file... then you _WILL_ have their
RADIATOR doesn't decrypt the password. It, instead, encrypts the
password it receives from the NAS and compares the two encrypted
passwords.
-Steve
- Original Message -
From: "Felicetti, Stephen A." [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, April 11, 2000 2:09 PM
Subject:
Long winded response with many examples and captures of test sessions
coming up:
Well, you are seeing two problems - the first was a "bug" in 2.14.1 in
that
only a single attribute would be handled by AddToReplyIfNotExist.
Alrighty. This is fixed in 2.15?
However the
second problem with
Right now (to get this working today) I'm just using 'AddToReply'. That
lacks flexibiliy but gets the job done for today. Your explanation of
why this is failing for 'AddToReplyIfNotIncluded' makes sense. A new
directive is probably in order (I dislike making exceptions so modifying
I have a lot of old password databases that are encrypted passwords.
We'd like all of the databases to end up cleartext... so... some of the
records have both.
RADIATOR seems to give precedence to the encrypted version. What do I
tweak to get the precedence to go the other way?
Using Authby
On Fri, 29 Oct 1999, Steven E. Ames wrote:
Nope. I was shooting for inside a realm:
Realm xyz.com
Rewrite ..# a rewrite rule that will change
username
into
# [EMAIL PROTECTED]
/Realm
The purpose is to append the correct
Silly Novice (Perl) Question:
What's a good rewrite rule to append a realm on a string _only_ if it
doesn't already contain one?
-Steve
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
xx.xxx.xxx
Secret
DefaultRealm your.realm.here
/Client
Regards,
Darwin
"Steven E. Ames" wrote:
Silly Novice (Perl) Question:
What's a good rewrite rule to append a realm on a string _only_ if
it
doesn't already contain one?
-Steve
===
Archive at http:
Would it be possible to modify the way that AuthLDAP handles reply
attributes? Right now they are all listed in a singly replyattr
attribute. This is unwieldy for a lot of our tools and increases the
complexity of the parsing.
A better mechanism would be to handle them the same way as SQL is
Thanks for the quick reply Hugh. That works but (IMHO) it defeats the
purpose of having a database if you have to put the complete attribute
pair into it.
I actually just spent an hour or so migrating some code from AuthSQL.pm
to AuthLDAP.pm to do exactly what I want. Works great.
Is there some
Would it be possible to modify the way that AuthLDAP handles reply
attributes? Right now they are all listed in a singly replyattr
attribute. This is unwieldy for a lot of our tools and increases the
complexity of the parsing.
A better mechanism would be to handle them the same way as SQL
Excellent question! I was about to tackle a similar question with
regards to LDAP. All of the return info I want to send is in the LDAP
database, just not sure how to send it back to the NAS.
-Steve
Am I correct in understanding that I cannot authenticate my users
from my
Unix password file
Joel,
The changes to make it LDAP more like SQL were added to the base system.
I don't think there was a patch released? But they will be there in
future releases.
-Steve
- Original Message -
From: Joost Stegeman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 04, 1999
14 matches
Mail list logo
