freeradius 3.0.15 memory corruption

[petr.linke at seznam.cz]

Only one info from aditional tests:

if in windows authentication dialog I fill correct name without domain and 
correct password, and username length is more than 5 characters - memory 
corruption.
if in windows authentication dialog I fill correct name (any length) without
domain and wrong password (auth fail) - no memory corruption.

Petr

"Ok, I understand. In attachment is the full debug (freeradius -Xxx) with 
winbind method in mschap.

Thank you for your help, Petr

---------- Original mail ----------
From: Alan DeKok <aland at deployingradius.com>
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
Date: 7. 9. 2017 17:11:19
Subjectt: Re: freeradius 3.0.15 memory corruption 
"On Sep 7, 2017, at 11:06 AM, <petr.linke at seznam.cz> <petr.linke at seznam.cz> 
wrote:
> 
> Only additional info. The same situation is with winbind method - username

> without domain with length more than 5 characters = memory corruption. 
> Username (length > 5 char) with domain = OK.

The additional information I need is:

> Please follow doc/bugs to get a useful backtrace.
> 
> Or. run it in debugging mode with "radiusd -Xxx". You'll get a LOT more 
> output, and the server will do additional memory sanity checking. That may

> show something useful.

If I don't get that, I can't help you.

Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.
html"
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.
html"