Ah, looking ~150 lines down in the changelog.Debian.gz I see a note about it being disabled in 3.0.12. Maybe the patch Debian added could have also added some diagnostic output when someone tries to enable it perhaps preventing a few days of wasted time. On Fri, Aug 30, 2019 at 12:14 PM Sven Hartge <sven@svenhartge.de> wrote:
On 29.08.19 19:01, Munroe Sollog wrote:
# freeradius -v
radiusd: FreeRADIUS Version 3.0.17, for host x86_64-pc-linux-gnu, built on Apr 22 2019 at 21:23:36
FreeRADIUS Version 3.0.17
Is this a packaged version from Debian or Ubuntu or a self-compiled one?
If the first, then the tlscache code has been completely disabled at the source level and will not work at all.
The latest 3.0.19 in Debian Unstable resolves this problem.
Grüße, Sven.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Munroe Sollog Senior Network Engineer munroe@lehigh.edu