A bunch of people using Versions are running into the exact same problem, More information from those Versions users is over in this thread:
http://groups.google.com/group/versions/browse_thread/thread/8275849edd0c94ab It seems that we're randomly getting one of two different certificates from google code on every fresh connection to the repository. Some insight from anyone at Google Code who's familiar with the – seemingly – recent changes to the SSL certificate setup would be strongly appreciated by me, and everyone else who uses Versions (or afaik. any other SVN client) to access https Google Code repositories. Thanks, - Dirk On Nov 22, 5:47 pm, Naomi Novik <[email protected]> wrote: > Hi all, > > We're getting the following error: > > Error validating servercertificatefor 'https://otwarchive.googlecode.com:443' > : > - Thecertificateis not issued by a trusted authority. Use the > fingerprint to validate thecertificatemanually!Certificateinformation: > - Hostname: *.googlecode.com > - Valid: from Nov 12 20:35:36 2009 GMT until Nov 12 20:45:36 2010 GMT > - Issuer: Google Inc, US > - Fingerprint: 0a:21:29:6e:13:40:12:15:48:fd:00:b7:10:a9:2d:8c:34:2d: > 1e:40 > (R)eject, accept (t)emporarily or accept (p)ermanently? p > > As you can see, the fingerprint we're getting: > > 0a:21:29:6e:13:40:12:15:48:fd:00:b7:10:a9:2d:8c:34:2d:1e:40 > > doesn't match what the FAQ says it should be here: > > http://code.google.com/p/support/wiki/SubversionFAQ#What_does_%22use_... > > so as instructed, I'm emailing you to discuss. Aside from the > mismatch, accepting thiscertificatepermanently isn't working. It > would be a real help if you can tell us how to fix this. > > -- Naomi -- You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
