Some more info: It seems that people using the command line client, or other Subversion clients are also running into this problem (minus the modal dialogs of course).
http://groups.google.com/group/google-code-hosting/browse_thread/thread/eef9caa43addd401 http://groups.google.com/group/google-code-hosting/browse_thread/thread/f2c77e5da0f6e555 Apparently Google Code is sending one of two SSL certificates back (at random) on every new connection to an https Google Code URL. One of these certs is signed by Thawte, one by Google themselves. Every time there's a mismatch between a previously accepted certificate for a particular URL and one that's being used on a new connection, SVN chokes and asks the user to accept the new certificate. Everything seems to point out that this is a problem with Google Code, not with Versions or Subversion in general. We're still looking for a workaround and ideally for a solution. Like Nick said, turning of working copy badges will help, because every time those are refreshed a new connection is made. It won't make the problem go away completely, but you'll see a lot fewer dialogs. Importing the *.googlecode.com certificate that Google signed themselves in your Keychain will not fix the problem, at least it doesn't for me; I still get the dialog asking me to accept the certificate, the difference is that the dialog claims the certificate is set to be trusted (which I just did in Keychain Access) instead of untrusted. If anyone here knows someone at or close to Google Code, please ask them to take a look at this thread. Any help we can get to clear this up would be appreciated. :) Cheers, - Dirk the Versions team On Nov 24, 6:54 pm, Nick <[email protected]> wrote: > I've been seeing this for the past few days. I tried importing the > certs into Keychain and now they show up as "trusted for this user" > when Versions displays them, but it hasn't stopped the popups. > > I had to turn off working copy badges to make it go away. So sad, > because I really depend on those! > > I'm using svn:external to bring in my google code repos. > > Nick > > On Nov 23, 5:08 pm, Paul Lefebvre <[email protected]> wrote: > > > > > I also have been seeing this problem the last couple days. I have > > about 4 or 5 Google Groups projects that I've bookmarked. Here's > > hoping to a fix soon; this is driving me crazy! > > > Thanks, > > > -- Paul > > > On Nov 20, 5:38 pm, Dirk Stoop <[email protected]> wrote: > > > > Hi Jared, > > > > Thanks for the info. > > > > There seems to be a problem with Subversion and wildcard SSL > > > certificates, which it seems Google has switched to for google code. > > > We're looking into a way around this problem. That's a lot of "it > > > seems"s in one sentence, but that's as much as we know right now. > > > I'll follow up here as soon as we know more. > > > > - Dirk > > > > On Nov 20, 9:45 pm, jared <[email protected]> wrote: > > > > > I'm having this problem as well, and my google code project is not set > > > > up as external in another repository. > > > > > Thanks for looking into this! > > > > > On Nov 20, 2:48 pm, Dirk Stoop <[email protected]> wrote: > > > > > > Thank you all for the feedback, > > > > > > I think this problem may only happen to people who have authenticated > > > > > google code projects set up as externals in other repositories that > > > > > they've bookmarked. We'll investigate more over here, if any of you > > > > > who are running into this problem don't have any google code externals > > > > > defined, please drop us a line here. > > > > > > Thanks again, > > > > > - Dirk > > > > > > the Versions team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" 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/versions?hl=en -~----------~----~----~----~------~----~------~--~---
