tag:blogger.com,1999:blog-11300808.post4867927674007754328..comments2024-03-27T04:19:57.377-07:00Comments on The official Google Code blog: SSL Certificate Renewal for Project Hosting on Google CodeMike Marchakhttp://www.blogger.com/profile/08067736591419106914noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11300808.post-67546855135609527322010-08-11T06:42:22.571-07:002010-08-11T06:42:22.571-07:00I from experience have always just bought a new SS...I from experience have always just bought a new SSL certificate as opposed to renewing them, as this seems to bring about less conflicts (and a more familiar process to me). I've installed my latest new SSL certs from <a href="http://www.ssl247.com/" rel="nofollow">SSL247.com</a>, although this is an interesting bit of code for Subversion.Unknownhttps://www.blogger.com/profile/10918315827644862300noreply@blogger.comtag:blogger.com,1999:blog-11300808.post-2920008979202132192008-06-06T15:00:00.000-07:002008-06-06T15:00:00.000-07:00On OSX, the [global] ssl-trust-default-ca = true o...On OSX, the [global] ssl-trust-default-ca = true option has no effect, because the openssl installation has no default trusted root certs; they're all stashed away in the Keychain app. The expedient thing to do is simply to check the fingerprint and accept the cert.Guido van Rossumhttps://www.blogger.com/profile/12821714508588242516noreply@blogger.com