* paffrath <paffrath(a)dfn.de>:
Two things
regarding this bug though.
Why didn't we hear from this until now?
Good question.
Maybe our setup is special? Is the number of RADIUS queries excessive?
We're using Enterasys/Extreme hardware for our access points.
Maybe other brands use (more/better) caching?
The offending
code is far from
new. Who else besides Ralf run radsecproxy in a static configuration (ie
no dynamicLookupCommand) on a multicore system and handle at least 10
requests/second?
In Germany most of the eduroam federation members using radsecproxy already.
So I’m very surprised that there is no information about so many crashes.
Mabye nobody noticed. I was running radsecproxy from systemd (since
that's what the distribution set up) and it was being restarted automatically.
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebrandt(a)charite.de Campus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155