All, I have built a fourth release candidate of SASL 2.1.27 which can be downloaded from here: HTTP: http://www.cyrusimap.org/releases/cyrus-sasl-2.1.27-rc5.tar.gz [MD5: 0e4ab034e93933ae7e4891b6ff58694f] http://www.cyrusimap.org/releases/cyrus-sasl-2.1.27-rc5.tar.gz.sig [MD5: 5ebb22737aa11810f6c9e5d12b167f16] FTP: ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-2.1.27-rc5.tar.gz [MD5: 0e4ab034e93933ae7e4891b6ff58694f] ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-2.1.27-rc5.tar.gz.sig [MD5: 5ebb22737aa11810f6c9e5d12b167f16]Note that the distro has been signed by my colleague Partha Susarla at FastMail. The only major change since RC4 has to do with detection of PAM support. Those using PAM with saslauthd are encouraged to make sure that this release compiles and runs as expected.
The (mostly) complete list of changes from 2.1.26 are these:
At this point any major changes (e.g. API, wire protocol) will be pushed out to 2.1.28 or 2.2.0. I believe that this is close to being a final release which I would like to get out by the end of September. The biggest outstanding issues are those around recent GSSAPI changes. I'm inclined to defer to Alexey's judgement on these unless someone can convince us that the SASL code is wrong per the specs. The fact that it broke a particular piece of code doesn't necessarily mean that the application code is correct and the SASL change was wrong. If there are any other last minute show stoppers, please open an issue on GitHub (preferably with a patch), or better yet create a pull request. -- Kenneth Murchison Cyrus Development Team FastMail Pty Ltd |