[the following is a draft blog post announcing the release of OF3.7 beta]
The Ignite Realtime Community is pleased to announce the beta for the next release of Openfire. This release contains a number of important fixes and improvements to stability and XMPP protocol compliance. You can find a full list of fixed issues here. This beta is also the first to be released by Ignite Realtime under the Apache License v2.0.
Some important security related notes to this release:
- Openfire no longer ignores the system property to disallow password changes via XMPP. With previous releases, it was not possible to prevent users from changing their password via their XMPP connection. (CVE-2009-1596)
- Fixed a XSS attack on the admin console login form.
Protocol compliance improvements:
- Publish Subscribe (PubSub)
- BOSH (http-bind) xml namespace compliance fix.
Some highlights of this beta release:
- Improves how Openfire handles "idle" connections. Some of you may have the system property xmpp.client.idle set to -1 to work around previously broken behaviour. You may now let it default to 6 minutes or set it to your preference.
- Improved Openfire's caching to be less prone to memory exhaustion by correctly calculating cache size usage.
- Fixed a bug where admin console login into a newly installed Openfire server would fail until restarted.
- Fixed a bug with shared rosters within a LDAP environment.
- Openfire now is built and shipped with the latest JRE (1.6.0u18).
- A memory leak with the Personal Eventing Protocol (PEP) was fixed.
- Openfire's custom log interface has been replaced with SLF4J and a Log4J backend.
- Fix issues with self signed SSL certificates.
- A number of improvements and fixes were made to the Multi-User Chat (MUC) configuration pages on the admin console
- There were also some improvements made to the plugins.
- There are also French, Russian, and Lithuanian langauge translation fixes for Openfire and some of the plugins.