client code for long extended attributes?
Can anybody comment on which client code should be used for long extended attributes? I see that the freeradius-client project predates RFC 6929. Is there any module in the server project that provides a good example of using these long values from requests?
Daniel Pocock wrote:
Can anybody comment on which client code should be used for long extended attributes?
I see that the freeradius-client project predates RFC 6929.
By a LONG ways. There's no client code for the extended attributes. The RFC was just published. So far as I know, FreeRADIUS is the only open source RADIUS system which supports it.
Is there any module in the server project that provides a good example of using these long values from requests?
src/lib/radius.c is the RADIUS encoder / decoder. Alan DeKok.
On 15/07/13 21:53, Alan DeKok wrote:
Daniel Pocock wrote:
Can anybody comment on which client code should be used for long extended attributes?
I see that the freeradius-client project predates RFC 6929.
By a LONG ways.
There's no client code for the extended attributes. The RFC was just published. So far as I know, FreeRADIUS is the only open source RADIUS system which supports it.
Is there any module in the server project that provides a good example of using these long values from requests?
src/lib/radius.c is the RADIUS encoder / decoder.
Should this code be shared with the client project freeradius-client? Or is it preferred to build a new client (or shared library) from the freeradius-server repository eventually?
Daniel Pocock wrote:
Should this code be shared with the client project freeradius-client?
No. The freeradius-client code is pretty bad.
Or is it preferred to build a new client (or shared library) from the freeradius-server repository eventually?
The client code is already LGPL'd. So it could be used as a client. Alan DeKok.
On 20/07/13 14:56, Alan DeKok wrote:
Daniel Pocock wrote:
Should this code be shared with the client project freeradius-client? No. The freeradius-client code is pretty bad.
Or is it preferred to build a new client (or shared library) from the freeradius-server repository eventually? The client code is already LGPL'd. So it could be used as a client.
Could you please clarify that - it is possible to build a client library from the server source tarball? In Debian, I see "libfreeradius2" built from the server source tarball but that appears to be server-side library code, or is it also for client applications?
Daniel Pocock wrote:
Could you please clarify that - it is possible to build a client library from the server source tarball?
Yes. RedHat already packages libfreeradius-radius as a separate RPM, IIRC.
In Debian, I see "libfreeradius2" built from the server source tarball but that appears to be server-side library code, or is it also for client applications?
Yes. It's a fully-featured LGPL'd RADIUS library. It handles everything related to RADIUS. Sockets, encoding, decoding, dictionaries, etc. Alan DeKok.
participants (2)
-
Alan DeKok -
Daniel Pocock