NOT Donation Site, but STEI@home BETA! Same issue, but different certificate. It is issued to setibase.ssl.berkeley.edu. I guess it is the same issue, but I don't like to take the risk. Same with IE8. I don't know if Windows Update is updating the certificate list. Didn't find an option for that and didn't find it in the log. Using Win7 64.

NOT Donation Site, but STEI@home BETA! Same issue, but different certificate. It is issued to setibase.ssl.berkeley.edu. I guess it is the same issue, but I don't like to take the risk. Same with IE8. I don't know if Windows Update is updating the certificate list. Didn't find an option for that and didn't find it in the log. Using Win7 64.

This is going as PM to Eric too.

Christoph

Christoph, this isn't an issue and it is NOT related to the described Firefox-Comodo certificate problems!

If I explicitly request a SSL connection to the SETI@home website via: https://setiathome.ssl.berkeley.edu
then the Seti@home webserver offers me a (simple) self issued (self signed) root certificate which was issued by the Seti group itself... There is no certificate chain used in this case and thus no CA root certificate (e.g. Verisign, Comodo) is involved.
This simple configuration is typically applied if the SSL connection is not intended to be used by the general public (but only by the Seti@home developers, who trust their own site, of course). And by the way, a server certificate, issued by a globally accepted certificate authority (deployed in each OS and web browser) costs some money, which you don't spend if it is not really necessary.