3.0.x rlm_sql mime encoding UTF8 characters

Arran Cudbard-Bell a.cudbardb at freeradius.org
Sun Nov 2 22:46:08 CET 2014


> On 2 Nov 2014, at 08:39, Alan DeKok <aland at deployingradius.com> wrote:
> 
> Isaac Boukris wrote:
>> I was faced with the same problem today (version 2.5.5).
>> 
>> I managed to get it working by replacing the function
>> 'sql_escape_func' in 'rlm_sql.c' with the function
>> 'sql_utf8_escape_func' from 'rlm_sql_log.c' file.
>> 
>> This seems to pass basic tests, but I am not sure what are the
>> implications of this change.
> 
>  Not much.  The best thing is probably to treat the "safe-characters"
> string as ASCII.  Then, allow any multi-byte UTF-89 character.
> 
>  I'll put a fix in before the next release.

I've pushed a fix to process UTF8 chars correctly for the %{escape:} and
%{unescape:} xlats.

I'm guessing the decision to pass through UTF8 chars here is more a matter
of convenience for the administrator than not wanting to write the code :)

-Arran

Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS development team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2



More information about the Freeradius-Users mailing list