Re: [RADIATOR] Radiator Version 4.15 released - security fixes and enhancements
Hi Heikki,
that's a great release!
I couldn't find info about CEF and JSON logging in the reference manual,
should be included at least as keywords with a pointer to the
'logformat.cfg' goodies file although I'd prefer having it in the main docs.
Is there a way to log the used TLS version and cipher to find out which
ones are in use before restricting it with the new EAPTLS_Protocols and
EAPTLS_Ciphers config options?
Best regards, Alex
On 2015-07-15 14:40, Heikki Vatiainen wrote:
We are pleased to announce the release of Radiator version 4.15
This version contains fixes for an EAP-MSCHAP-V2 and EAP-pwd
vulnerability. Upgrade is recommended. Please review OSC security
advisory OSC-SEC-2015-01 for more information:
https://www.open.com.au/OSC-SEC-2015-01.html
As usual, the new version is available to current licensees from:
https://www.open.com.au/radiator/downloads/
and to current evaluators from:
https://www.open.com.au/radiator/demo-downloads
Licensees with expired access contracts can renew at:
https://www.open.com.au/renewal.html
An extract from the history file
https://www.open.com.au/radiator/history.html is below:
-
Revision 4.15 (2015-07-15)
Selected fixes, compatibility notes and enhancements
Fixes an EAP-MSCHAP-V2 and EAP-pwd vulnerability.
OSC recommends all users to review OSC security advisory
OSC-SEC-2015-01 to see if they are affected.
https://www.open.com.au/OSC-SEC-2015-01.html
perl-ldap-0.32 or better is required. Should be available in all current
systems.
EAP-pwd requires Crypt::OpenSSL::Bignum 0.06 or later from CPAN
Configurable TLS version and ciphersuite selection for TLS based EAP and
stream modules
CRL checks for the entire certificate chain can now be enabled
Included Gossip framework with Redis based implementation
Support for Gossip when communicating next hop proxy failures between
Radiator instances
Shared duplicate cache for a more simple server farm configuration
Windows Event log support
Custom format support for logs, authentication logs and accounting logs.
CEF and JSON included
Support for IEEE 802.1AE, also known as MACsec
All AuthBys now support PostAuthHooks
Various binary modules are now available from OSC and were removed from
the Radiator distribution
Detailed changes
Added VENDOR STI (Server Technology Inc.) 1718 and multiple STI VSAs to
dictionary. Contributed by Garry Shtern.
Added VENDOR PacketDesign 8083 and VSAs PacketDesign-UserClass and
PacketDesign-FTP to dictionary. Contributed by Garry Shtern.
Added SN-Software-Version to dictionary. Reported by Bruno Tiago Rodrigues.
Changed type of VENDORATTR 3076 Cisco-VPN-DHCP-Network-Scope in
dictionary.cisco-vpn from text to ipaddr. Reported by Kilian Krause.
Dictionary updates: Added H3C proprietary values H3C-SSH and H3C-Console
for Login-Service. Changed Lancom LCS-Mac-Address type from string to
hexadecimal. Added H3C-Priority. All reported by Philip Herbert.
Zero length writes are now skipped in Stream.pm write_pending() used by
RadSec, Diameter, SIGTRAN and other stream protocols. SCTP does not
support 0 length syswrites on all platforms and may close the socket if
zero length write is done.
Added VENDOR Airespace 14179 VSAs 7-11 and 13-16 to dictionary.
AuthBy GROUP now updates current AuthBy for %{AuthBy:parmname}. When
AuthBy GROUP is used, this special formatting now gets the parameter
value from the current AuthBy within the group instead of the AuthBy
GROUP itself.
Updated VENDOR 1991 Foundry VSAs in dictionary. foundry-privilege-level
is now a synonym for brocade-privilege-level. Added a number of foundry
VSAs.
LDAP Version now defaults to 3 instead of 2. Updated a number of LDAP
configuration example files in goodies to reflect this change.
Ldap.pm now uses the LDAP object's disconnect method, instead of closing
the socket directly.
AuthBy LDAP2 and AuthBy LDAPDIGIPASS now use escape_filter_value
provided by Net::LDAP::Util instead of escapeLdapLiteral in Ldap.pm
Ldap.pm escapeLdapLiteral is now deprecacted and perl-ldap-0.32 or
better is required.
RefreshPeriod in ClientListSQL and ClientListLDAP now support special %
formatting. Suggested by Bengi Sağlam.
Updated VENDOR 2011 Huawei VSAs in dictionary. Huawei-Input-Basic-Rate
is now an alias for Huawei-Input-Peak-Rate. Huawei-Output-Basic-Rate was
changed similarly. Some of the attribute numbers appear to have
different names and types between different devices. Huawei-User-Type,
Huawei-MIP-Agent-MN-Flag and Huawei-Requested-APN are now aliases but
aliasing may be handled with separate dictionary files in the future.
Huawei-HW-Portal-Mode was renamed to Huawei-Portal-Mode.
WiMAX dictionary updates: changed WiMAX-Session-Termination-Capability
type to integer and added one value: Dynamic-Authorization. Changed
WiMAX-PPAQ TLV Quota-Identifier type to binary. WiMAX subattributes
within
Re: [RADIATOR] Radiator Version 4.15 released - security fixes and enhancements
On 16.7.2015 13.42, Hartmaier Alexander wrote: I couldn't find info about CEF and JSON logging in the reference manual, should be included at least as keywords with a pointer to the 'logformat.cfg' goodies file although I'd prefer having it in the main docs. Good point. I'll see that CEF and JSON will be mentioned in ref.pdf The configuration sample file 'logformat.cfg' is mentioned where LogFormatHook for Log FILE and AuthLog FILE are described. It's also mentioned where AcctLogFileFormatHook for accounting messages is described. The configuration sample shows how to use the new module Radius/LogFormat.pm. This module includes CEF and JSON authentication log formatting and JSON accounting log formatting. There's also an example of how to use a custom module, possibly modified from Radius/LogFormat.pm, to change the formatting or add new formats. Is there a way to log the used TLS version and cipher to find out which ones are in use before restricting it with the new EAPTLS_Protocols and EAPTLS_Ciphers config options? I think the ciphers are the ones that can be listed with 'openssl ciphers -v' these depend on the SSL/TLS library. Older OpenSSL versions seem to have quite different set of ciphers than the most recent LibreSSL for example. In other words the ciphers could be listed by radiusd, but you can also see them from the command line. Also, new DEBUG level log message was added to show which Net::SSLeay version and SSL/TLS libary is used to make sure radiusd uses what you expect it to. The protocols also depend on what's compiled in the SSL/TLS library. I think the recent LibreSSLs do not have SSLv3 support anymore. Are you thinking about printing the available SSL/TLS versions before restricting them? Note that for TLS based EAPs, TLSv1 is the minimum so SSLv3 is not possible which means what you can use is TLSv1 or better. Thanks, Heikki -- Heikki Vatiainen h...@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. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Radiator Version 4.15 released - security fixes and enhancements
RC4 is particularly broken now: https://www.rc4nomore.com https://www.rc4nomore.com/vanhoef-usenix2015.pdf In conjunction with https://tools.ietf.org/html/rfc7465 , it is probably time for RADIUS servers to comply with this by default unless explicitly configured otherwise: o TLS servers MUST NOT select an RC4 cipher suite when a TLS client sends such a cipher suite in the ClientHello message. o If the TLS client only offers RC4 cipher suites, the TLS server MUST terminate the handshake. The TLS server MAY send the insufficient_security fatal alert in this case. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Radiator Version 4.15 released - security fixes and enhancements
On 2015-07-16 15:07, Heikki Vatiainen wrote: On 16.7.2015 13.42, Hartmaier Alexander wrote: I couldn't find info about CEF and JSON logging in the reference manual, should be included at least as keywords with a pointer to the 'logformat.cfg' goodies file although I'd prefer having it in the main docs. Good point. I'll see that CEF and JSON will be mentioned in ref.pdf The configuration sample file 'logformat.cfg' is mentioned where LogFormatHook for Log FILE and AuthLog FILE are described. It's also mentioned where AcctLogFileFormatHook for accounting messages is described. The configuration sample shows how to use the new module Radius/LogFormat.pm. This module includes CEF and JSON authentication log formatting and JSON accounting log formatting. There's also an example of how to use a custom module, possibly modified from Radius/LogFormat.pm, to change the formatting or add new formats. I know because I was the one who requested the feature and wrote the Log module before you added the hook ;) Is there a way to log the used TLS version and cipher to find out which ones are in use before restricting it with the new EAPTLS_Protocols and EAPTLS_Ciphers config options? I think the ciphers are the ones that can be listed with 'openssl ciphers -v' these depend on the SSL/TLS library. Older OpenSSL versions seem to have quite different set of ciphers than the most recent LibreSSL for example. In other words the ciphers could be listed by radiusd, but you can also see them from the command line. Also, new DEBUG level log message was added to show which Net::SSLeay version and SSL/TLS libary is used to make sure radiusd uses what you expect it to. The protocols also depend on what's compiled in the SSL/TLS library. I think the recent LibreSSLs do not have SSLv3 support anymore. Are you thinking about printing the available SSL/TLS versions before restricting them? Note that for TLS based EAPs, TLSv1 is the minimum so SSLv3 is not possible which means what you can use is TLSv1 or better. Yes I know. What I'd like to have is a way to *log* the actual chosen cipher per EAP-TLS connection, ideally in the AuthLog file. Thanks, Heikki Cheers, Alex *** T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien Handelsgericht Wien, FN 79340b *** Notice: This e-mail contains information that is confidential and may be privileged. If you are not the intended recipient, please notify the sender and then delete this e-mail immediately. *** ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
