So I rolled on over to my blog reader and came across Mark Finkle’s post about the release of Prism for something other than windows.
Back when Prism was still called WebRunner, I gave it a try, since I’ve been looking for a way to have Zimbra have it’s own little icon in the doc. At the time, WebRunner was just a little bit too buggy for daily use. Hopeful that the major issues were resolved, I pulled down Prism, fired it up, and entered the address of my Zimbra install.
Does the Zimbra client work better in Prism? I can’t tell. They changed the way security settings work to completely disallow self-signed certs. Needless to say, I’m not buying a certificate so that the two people using my mail client can feel all warm and fuzzy because Thawte says it’s safe. Of course it’s safe, the two of us administer it.
Even more troubling is that there is a forum thread about this issue, but without any response on how to get around it.
I understand that users need to be protected from themselves at times and many blindly hit ‘okay’ to any dialog box they see. However, Prism is not an end user product yet. By it’s own admission, it’s a prototype. Therefore, it only follows that it should be easy to use for developers. Which means allowing non-fully trusted certificates.
Forum thread’s been updated, too ;)
All ranting aside, the way around the in-built limitation is to copy your firefox certificates over your prism ones. The file’s called cert8.db and you’ll find it in the directory of your firefox profile.
