Hi everyone, This problem has been fixed by google. On thanksgiving nonetheless, so I know who I'm giving thanks to ;)
If anyone still gets those dialogs (which seems pretty unlikely to me, but you never know), please drop a line here or at google's support page linked in my previous post. Cheers and happy thxgiving, - Dirk the Versions team On Nov 24, 11:48 pm, Dirk Stoop <d...@madebysofa.com> wrote: > Yet more info: > > Please 'star' this issue at Google Code if you're experiencing the > problem in Versions:http://code.google.com/p/support/issues/detail?id=3312 > > The more votes, the more likely they'll be able to give it a higher > priority. > > Thank you all for your patience, > - Dirk > > the Versions team > > On Nov 24, 9:57 pm, Stratification <stratificat...@gmail.com> wrote: > > > > > That sounds very much like what I'm seeing and would really explain > > its intermittent nature. Thanks for the update, here's to hoping > > there's a reasonable fix on the horizon (or Google gets their act > > together). > > > Aaron > > > On Nov 24, 11:59 am, Dirk Stoop <d...@madebysofa.com> wrote: > > > > 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/thre...... > > > > 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 -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
