Hi, Can any one tell me that FREE RADIUS client is inernally doing UTF-8 conversion for the multilingual characters or It is replying on some other underlying module who is suppling credentials like username and password? Regards, Karnik Jain
On Mon, Feb 07, 2011 at 04:05:41PM +0530, karnik jain wrote:
Can any one tell me that
FREE RADIUS client is inernally doing UTF-8 conversion
for the multilingual characters or It is replying on some other underlying module
I think that's a meaningless question. RADIUS deals with bytes. It will send as User-Name whatever chunk of bytes you give it. It doesn't mangle values.
who is suppling credentials like username and password?
What exactly are you asking about - the program called "radclient"? In that case it is you, the person who invokes radclient, who supplies the username and password on stdin. If you're asking about something else, please be more specific.
Hello, I think that's a meaningless question.
RADIUS deals with bytes. It will send as User-Name whatever chunk of bytes you give it. It doesn't mangle values.
I am under the impression that RADIUS client (radclient) is itself is doing the UTF-8 conversion as per RFC 2865 while sending multilingual username attribute if it is not in UTF-8 form. So I think this is not at all a meaning less. correct me if i am wrong.
What exactly are you asking about - the program called "radclient"? In that case it is you, the person who invokes radclient, who supplies the username and password on stdin.
If you're asking about something else, please be more specific.
Yes, You have hit the correct nail. I am talking about radclient only. If supplied USER-NAme is not UTF-8 encoded by some means suppose the scenario where UTF-8 support is not there then at that time what radclient does. Does it send the same multilingual charcters to the RADIUS server or first of all convert that into UTF-8 as per RFC 2865 and send it to RADIUS server in ACCESS REQUEST packet as attribute or just send as it is to RADIUS server? Regards, Karnik jain
karnik jain wrote:
I am under the impression that RADIUS client (radclient) is itself is doing the UTF-8 conversion as per RFC 2865 while sending multilingual username attribute if it is not in UTF-8 form.
So I think this is not at all a meaning less. correct me if i am wrong.
Your question is meaningless and inappropriate for this forum. If you're writing your own RADIUS client, then pretending to ask questions about radclient is not nice. If you want to know how radclient handles UTF-8, go read the source code. It's publicly available.
Does it send the same multilingual charcters to the RADIUS server or first of all convert that into UTF-8 as per RFC 2865 and send it to RADIUS server in ACCESS REQUEST packet as attribute or just send as it is to RADIUS server?
This question was already answered on the list, in a message describing how a RADIUS client works. If you're not going to read the messages on this list, there's no point in asking questions here. Alan DeKok.
On Mon, Feb 07, 2011 at 05:07:03PM +0530, karnik jain wrote:
I am talking about radclient only. If supplied USER-NAme is not UTF-8 encoded by some means suppose the scenario where UTF-8 support is not there then at that time what radclient does.
Does it send the same multilingual charcters to the RADIUS server or first of all convert that into UTF-8 as per RFC 2865 and send it to RADIUS server in ACCESS REQUEST packet as attribute or just send as it is to RADIUS server?
It just sends the bytes as-is. If you have data in another encoding, which you want to convert to UTF-8 for sending, then you need to transcode it yourself first using something like 'iconv'. In any case, the data which you provide to radclient needs to use the standard ASCII characters for equals, double-quotes and so on, so that it can parse the lines. UTF-8 fulfils that requirement. HTH, Brian.
Hello B.Candler, Thank you so much sir for replying back. It is really helpful to my research on RADIUS client. Thanks, Karnik On Mon, Feb 7, 2011 at 7:50 PM, Brian Candler <B.Candler@pobox.com> wrote:
On Mon, Feb 07, 2011 at 05:07:03PM +0530, karnik jain wrote:
I am talking about radclient only. If supplied USER-NAme is not UTF-8 encoded by some means suppose the scenario where UTF-8 support is not there then at that time what radclient does.
Does it send the same multilingual charcters to the RADIUS server or first of all convert that into UTF-8 as per RFC 2865 and send it to RADIUS server in ACCESS REQUEST packet as attribute or just send as it is to RADIUS server?
It just sends the bytes as-is.
If you have data in another encoding, which you want to convert to UTF-8 for sending, then you need to transcode it yourself first using something like 'iconv'.
In any case, the data which you provide to radclient needs to use the standard ASCII characters for equals, double-quotes and so on, so that it can parse the lines. UTF-8 fulfils that requirement.
HTH,
Brian. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
Brian Candler -
karnik jain