Specifications

Steel-Belted Radius v6.1.1 Release Notes
8 Resolved Issues
No stored procedures with MySQL—As of MYSQL 5.0 and 5.1, stored
procedures are supported by MYSQL and can be used with Steel-Belted Radius
when using a SQL backend for authentication and accounting. Note that there
are known issues with MYSQL when using CALL statements such as "SQL=
{call rsp_getpword (%username!i, %password!o)}". However, execute
statements, such as "SQL= Execute rsp_getpword %username, %password"
work fine. See MYSQL for further details. (8130)
Resolved Issues
The following issues from previous releases have been resolved in the Steel-Belted
Radius release 6.1 software. The identifier in brackets is the tracking number in our
bug database.
Problems Resolved in Release 6.1.1
SNMP get requests fail when a TcpControlAddress is configured in radius.ini.
(255899)
LDAP authentication fails when simultaneous authentications are attempted.
(258354)
LDAP authentication fails due to login limit exceeded when using routed proxy.
(260680)
Proxy target statistics are incorrect in the SBR administrator. (261108)
Server crashes when stripping usernames. (262371)
LDAP authentication does not work against Microsoft when searching the top
base. (269036)
The “block=1” setting does not work for static accounting realms. (271743)
Machine authentication fails when username contains a DNS subdomain.
(273069)
Native user passwords can not contain international characters. (276427)
Server crashes when LDAP authentication is configured on Linux. (278229)
EAP-Id is incremented in accept packet for LEAP authentication. (281842)
RSA SecurID authentication fails because of socket leak. (282087)
Client shared secrets are not propagated to replica servers. (282975)
Server crashes when a native user record is accessed in the SBR Administrator.
(284066)
The stringnz attribute type is not working for response attributes configured
with HiddenEAPIdentity in
radius.ini. (286845)