As you have probably noticed, I’ve just gone through a major software migration for my web site. I was using typo. It was OK, but had a few problems. While its web site describes it as “lean”, that isn’t really the reality. It also relied on a combination of Apache, LigHTTPd and FastCGI that tended to break down without explanation. The biggest reason for change, though, was that typo’s authors’ idea of what was important functionality was diverging from mine.
Lotus Domino 7 has an unfortunate bug which means that you can’t cross-certify with another organization via phone or e-mail, by using the Domino Administrator, choosing Cross Certify Key… and entering their key ID. The bug is documented in the readme.pdf, and is still unfixed as of 7.0.2. It results in server errors saying “The subject’s public key found in the cross certificate does not match the one found in the certificate table.”
[Update 2006-05-17: I’m pleased to say that I heard today they’ve managed to squeeze a fix for the problem into 7.0.2. This is not an official statement of support from IBM, etc etc.]
This is a problem in situations where you want to cross-certify your server with someone else’s, but for whatever reasons they can’t or won’t give you access to CERT.ID, and can’t engage the cooperation of the owners of their CERT.ID.