Fwd: Upgraded freeradius to 2.1.12 with openssl 0.9.8n - Error: No SSL info available. Waiting for more SSL data.
winsonfernandes at gmail.com
Mon Apr 16 16:21:17 CEST 2012
We added more logs into openssl and found out why the
“state->info.initialized” did not get set and the callback had arg as NULL.
This was because the value SSL_CTRL_SET_MSG_CALLBACK_ARG passed by
freeradius SSL_set_msg_callback_arg -> Set_msg_callback_arg was 14 (due to
wrong header file). The value should have been 16 as per the upgraded
The radiusd was using the montavista build environment's openssl header
file which is 0.9.7 (which comes bundled with montavista tool chain).
Will either upgrade the openssl tool chain or make necessary changes in the
On Sun, Apr 8, 2012 at 3:43 PM, Alan DeKok <aland at deployingradius.com>wrote:
> Winson Fernandes wrote:
> > I upgraded freeradius version from 2.0.2 to 2.1.12 and also the openssl
> > version from 0.9.7 to 0.9.8n.
> > The issue I am facing now is with peap mschapv2 windows client not able
> > to authenticate with my radius server.
> Well... other people have it working. OpenSSL is weird.
> > The error is [peap] No SSL info available. Waiting for more SSL data.
> That means that the server expects the client to send more data, and
> the client expects the server to send more data. Since the client is in
> charge here, nothing more happens.
> > Not sure what the bug298 is all about and also what could be the
> > possible reason for the arg (state) to be NULL?
> No idea. OpenSSL is weird.
> Alan DeKok.
> List info/subscribe/unsubscribe? See
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freeradius-Devel