Comment 48 for bug 600779

Just to add some clarification to comment 42: Safari and Chrome only accept ipsCA certificates when running in Windows because they use the native certificate store in Windows that IE8 uses. Don't expect them to work on Safari or Chrome for Mac OS X or Linux because it won't! By way if you are teaching in higher ed and your school is somewhat typical like ours, your students will be overwhelmingly coming with Macs to the classroom this fall semester.

You truly get what you pay for (free in .edu's case): it is IMHO extremely unethical that ipsCA issued certificates that expire AFTER their root CA's expiration! Mind you they've had 11 YEARS to avoid this problem and instead waited until 9/7/2009 to just begin to solve it! We are now half a year into Mozilla's vetting process and they still have not responded to the INITIAL information gathering! Is it really worth keeping them as your SSL certificate issuer when you can get a wild card certificate for just over $200 and it will cover an *unlimited* number of websites and not student will have an issue?

For a more permanent solution, ask your school's IT department to seriously consider setting up a trusted root signed CA internally or use a 3rd party SSL managed service so you can issue your own certificates that are accepted everywhere. If you have large numbers of certificates it is a lot more cost effective and easier to manage in the long run.