Release Notes 4.5.0.37

Release Notes, Version 4.5.0.37
8
SOFTWARE FIXES
The following problems that were identified in previous releases of the ProCurve Secure Access
700wl Series system software have been fixed in software release 4.5.0.37:
• Upgraded the Apache web server to version 2.0.52_4 to address a web server restart
vulnerability,
which was only possible from an uplink client. The vulnerability was never open to
downlink/untrusted clients. (23394)
• Access Controller intermittent disconnects from Access Control Server. (20529, 20945)
• Access Controllers sometimes cannot display any clients after upgrade. As a workaround,
modifying a configuration item will usually fix this. (20669)
• Users authenticating with 802.1X Logons and associated with a Connection Profile that
specifies a VLAN ID will not get the correct rights row in the Rights Assignment table.
(19849)
• A client with a static IP and valid address on the uplink does not always get redirected.
(20832)
• An Access Controller IP address is not correctly displayed with CLI “show clients”
command. (20753)
• Access Controllers are not displayed in user interface when using Internet Explorer on
Windows 2003 Server. (20771)
• Retrieving client or session status may cause an Access Controller to reboot. (20730)
• The first time the 802.1X/WPA page is viewed, an error message is displayed stating that
WPA is not configured. To remove the error message, click the “Save” button. (19849)
• After performing a back-up on the Access Control Server, local host events are not logged.
Access Controller events are still logged after a back-up. (19801)
• Several minor error messages and minor information messages are added to the log when a
client attempts to access a restricted page. (19394)
• In order to perform a Trace Transaction when using Kerberos, the date and time settings must
match between the Access Control Server and the Key Distribution Center (KDC). (19908)
• A QoS Marking name may consist of 1 to 32 characters. If the name is one character long, it
cannot be the number zero (0). (19872)
• When creating or editing filters for Allowed or Redirected traffic and using a “!” or the word
“not” in front of the address, you must include a space between the “!” or the word “not” and
the address. For example: not @internal@. (19410)
• If you configure an IP address range for VPN tunneling (via the IP Address Assignment page
under the VPN icon) you must also set “Allow Static IP” in the relevant Access Policies
(including the Unauthenticated Access Policy) (18869)