EZproxy version 5.6 released today

Good news for EZproxy admins! A new version was released today with lots of bug fixes and a few new features to boot. Here's the recap from the official announcement that went out:

New features:
• Beta EZproxy implementations now no longer require a license—the betas will simply “expire,” which makes it easier for libraries to try things out
• A new way to detect and resolve crashes, down to identifying the actual machine instruction that caused it
• In the Administration Screen, Server Status, the display now shows detailed information about the “Option Cookie” directives that are in place for each database definition on the “Extended Information” display.

General bug fixes:
• Removed extraneous repeating lines in messages.txt for Shibboleth and UUAcquireMutex/UUReleaseMutex
• Changed timers for the Guardian process and for Athens sites, eliminating a potential restart
• When a Shibboleth V2.x attribute was received without a XML attribute FriendlyName specified, EZproxy would crash; EZproxy no longer requires the XML attribute FriendlyName to be present
• Resolved a potential problem in the SSL certificate import process: In some cases, a failed SSL certificate import would leave an incomplete .cnf file
• Resolved a problem where, in rare cases, EZproxy would have problems running from a symlinked directory
• Resolved an issue with referring URL authentication where some users were being sent the suspend.htm file instead of being transparently authenticated
• Resolved a problem that, in rare cases, EZproxy used case sensitive comparisons for starting point URL comparisons
• In some cases, EZProxy would crash when querying a Shibboleth Identity Provider for attributes; this problem has been resolved
• EZproxy once again ignores SIGHUP signals, so the Guardian process will keep running when a SIGHUP signal is received
• Resolved an invalid pointer in the UTF-16 parser, preventing unauthorized access to the Siku Quanshu content, one of the largest collections of books in Chinese history
• A number of additional security issues were also addressed in this release.

A note about future supported operating platforms:
Release V5.6 of EZproxy is the last release to support Solaris SPARC hardware and Operating System platforms. Support for Solaris on Intel platforms continues unchanged. The next release (V6.0, expected late 2012) will not include a SPARC build.

In addition, EZproxy V6.0 will be the first release to use a revamped compile and build process, which will reduce maintenance and provide support for IP V6. The new compile and build process supports consuming newer system libraries such as those needed for IP V6 that the previous one did not.

As part of this process transition, we are looking for beta testers of EZproxy V6.0 for each supported platform. Please e-mail  by 1 August 2012 to participate.

We encourage you to upgrade to EZproxy 5.6 or move to the hosted version to stay current with the latest features. Please review the enhancements page and upgrade at your earliest convenience. The EZproxy hosted version is currently available in the US, with plans for a European pilot and release later this calendar year.

  • See more details and a full list of changes
  • Upgrade to EZproxy 5.6
  • OCLC EZproxy Virtual Users Group meeting happens on May 30 from 10:00–11:00 am, ET. We’ll discuss the latest EZproxy release, and discuss IPv6, what it is, what it means and how to be ready for it. Register now.

There are no Profiles matching the configured list.