[RADIATOR] Is StatusServer broken in 4.19 and latest patches?

[Heikki Vatiainen]

On 8.8.2017 12.36, Karl Gaissmaier wrote:

> nothing has changed at the upstream since I upgraded yesterday, here you 
> see it after I switched back to 4.17:
> 
> Tue Aug  8 09:07:43 2017 099341: DEBUG: Packet dump:
> *** Received from 193.174.XX.YY port 33333 ....
> Code:       Status-Server
> Identifier: 0
> Authentic: <230>)t<226><6><166><174><232><20>$<9>O<184>vfB
> Attributes:
>      Message-Authenticator = 
> b<165><188><140>C<231><209><15>\<160>c<205><174><242>=<6>
> Tue Aug  8 09:07:43 2017 099988: DEBUG: Packet dump:
> 
> 
> *** Sending reply to RadSec 193.174.75.134:33333 ....
> Code:       Access-Accept
> Identifier: 0
> Authentic: <230>)t<226><6><166><174><232><20>$<9>O<184>vfB
> Attributes:
>      Reply-Message = "Radiator Radius server version 4.17"
>      Reply-Message = "Running on mizar since Tue Aug  8 09:05:44 2017"

With 4.18 and later there will also be Message-Authenticator in the 
reply. This should be fine if the receiver respects RFC 5597 which 
allows Reply-Message and Message-Authenticator in Access-Accepts.

I'd say this is the main change between 4.17 and the latest version.

Please let us know about your findings.
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, 
NetWare etc.