freeradius -X crashes

[Mathieu Simon (Lists)]

Hi Henrik

The situation with Debian is not so easy, but for interim have a look
at the building packages page in the FR wiki.

You will find for both Debian and Ubuntu repositories maintained by
people using and building packages for Debian and Ubuntu.

In case of Debian for wheezy and jessie as for writing. Give them a try,
and otherwise I can only concur with Arran and Alan: It's not that
difficult to compile from source or build a debian package from source.

-- Mathieu

Am 28.06.2016 um 17:14 schrieb Henrik Kressner:
> On 28-06-2016 16:51, Arran Cudbard-Bell wrote:
>>> On Jun 28, 2016, at 10:41 AM, Henrik Kressner <kressner at synkro.dk>
>>> wrote:
>>>
>>>
>>>
>>> I am using:
>>>
>>> freeradius -v
>>> freeradius: FreeRADIUS Version 2.2.5, for host i586-pc-linux-gnu,
>>> built on Oct 24 2014 at 04:18:43
>> This version is unsupported.
>>
>> You should upgrade to the latest v3.0.x series release.
>>
>> -Arran
>>
>>
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
> 
> Thanks for fast reply.
> 
> 
> Now i suspect an error on: http://wiki.freeradius.org/building/Debian
> 
> 
> It claims:
> 
> " To install up-to-date FreeRADIUS 2.2.x packages on Debian stable
> systems, use the backports repository."
> 
> 
> When I follow that instruction, (on another mashine) I end op with the
> same version.
> 
> # freeradius -v
> freeradius: FreeRADIUS Version 2.2.5, for host x86_64-pc-linux-gnu,
> built on Oct 28 2014 at 16:27:11
> 
> When i try to start the server:
> 
> # freeradius -X
> 
> 
> It crashes with this troubeling message:
> 
> radiusd: #### Loading Clients ####
>  client localhost {
>      ipaddr = 127.0.0.1
>      require_message_authenticator = no
>      secret = "testing123"
>      nastype = "other"
>  }
> Refusing to start with libssl version OpenSSL 1.0.1e 11 Feb 2013 (in
> range 1.0.1 - 1.0.1f).  Security advisory CVE-2014-0160 (Heartbleed)
> For more information see http://heartbleed.com
> 
> 
> I believe my openssl should be updated.
> 
> 
> 
> 
> Anyway, I must look for a way to install v3.x.x.
> 
>