On 3.8.2017 18.58, Karl Gaissmaier wrote:
is there a good reason why the NoReplyReject keyword from <AuthBy
RADIUS> is not supportetd in <AuthBy RADSEC> ???
I'd say there's no reason not to add it to AuthBy RADSEC. It will make
configuration shorter and easier to read when compared to a using a
hook. Meanwhile, if you take a look at how AuthBY RADIUS implements this
parameter, the NoReplyHook should be able to do this too.
Thanks for reminding about this!
Heikki
--
Heikki Vatiainen <[email protected]>
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.
_______________________________________________
radiator mailing list
[email protected]
http://lists.open.com.au/mailman/listinfo/radiator
