Null SQL user

Michael Griego mgriego at
Thu Sep 21 00:48:44 CEST 2006

There already is a DEFAULT profile that is checked for every user  
regardless of what groups they may or not may be in.  It would be  
easiest (and make the most sense, IMO) to just wrap everything before  
the profile check section (line 1018 in the CVS HEAD rlm_sql.c) in an  
"if (request->username != NULL)" block...  That way none of the  
radcheck/radreply and group checks for the normal username are done,  
it just skips straight to checking the default profile (or user  
profile if the attribute exists).


On Sep 20, 2006, at 5:05 PM, Peter Nixon wrote:

> Our patch needs a little work before its ready to be committed.  
> Currently to
> save auditing the rest of the code we are rewriting null values to  
> "X" which
> doesn't exist as a user in our database.
> We will spend some time tomorrow to write this patch correctly now  
> that I know
> alan doesn't have anything against it. (It was just a hack to get us
> operational)
> I also think that we should be able to have DEFAULT data in SQL  
> tables, but
> this will require a whole new class of query to impliment correctly. 
> (Or a
> second copy of the SQL module with the current code)
> Cheers
> On Wed 20 Sep 2006 19:26, Michael Griego wrote:
>> How does your patch work, Peter?  Is it similar to what I described?
>> --Mike
>> On Sep 20, 2006, at 9:45 AM, Alan DeKok wrote:
>>> Peter Nixon <listuser at> wrote:
>>>> We have had to locally patch rlm_sql to make it accept NULL
>>>> usernames. Is
>>>> there any particular reason why it does this check?
>>>> rlm_sql_postgresql works
>>>> fine with NULL usernames as does the rest of FreeRADIUS.
>>>   Go for it.
>>>   Alan DeKok.
>>> --
>>>       - The web site of the book
>>> - The blog
>>> -
>>> List info/subscribe/unsubscribe? See
>>> devel.html
>> -
>> List info/subscribe/unsubscribe? See
> -- 
> Peter Nixon
> PGP Key:
> -
> List info/subscribe/unsubscribe? See 
> devel.html

More information about the Freeradius-Devel mailing list