User-Name return glitch in FR 3.0.17?
aland at deployingradius.com
Tue Sep 4 14:29:37 CEST 2018
On Sep 4, 2018, at 7:48 AM, Stefan Paetow <Stefan.Paetow at jisc.ac.uk> wrote:
> The existing behaviour (only one User-Name attribute) *was* changed by the code change (to always send a User-Name) that now causes this problem, so... just saying.
The issue was that the previous code sometimes *didn't* send User-Name when it was required to do so. That's wrong.
> Adding unlang may fix this for *new* installations, but all existing installations going to 3.0.18 will suddenly experience the same issue that I did originally. Those upgrading would have to do diffs (between .rpmnew and the original) to see what's changed, and that often does not happen. Either way, an upgrade *will* have an effect that is a departure from pre-3.0.17 behaviour.
Any bug fix is departure from previous behaviour.
I'll see if there's a fix. But it will have to be done carefully.
More information about the Freeradius-Users