[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freeradius-devel
Subject:    Re: Looking to pay for customization
From:       Alan DeKok <aland () deployingradius ! com>
Date:       2009-04-15 7:52:46
Message-ID: 49E5924E.2060805 () deployingradius ! com
[Download RAW message or body]

Eric Geier wrote:
> Thank you all for your comments.
> 
> What I don't understand is that it seems like it was very easy to do in a
> previous version:
> http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007870.html
> http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007871.html

  Yes.  Things change.

  The code in 2.x is a lot more capable than 1.x.  However, as a result,
it has some limitations that 1.x didn't.

  e.g. Shared secrets can now be any length, not just 32 characters.
However, this means that the shared secrets *cannot* be defined per
request packet.  They *must* be defined per client.

> Can something similar be done in version 2?

  See "dynamic clients".  That code could be updated to "peek" at the
entire packet, and create new clients based on more than just the IP
address.

  But it *is* more work than it would have been in 1.x.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
[prev in list] [next in list] [prev in thread] [next in thread]