Re: Problem: Google Code SSL certificates - Reopened
Hello folks - So, a definitive fix to this problem has been posted [1]. I contacted the Versions Team, and they confirmed that this is the necessary fix, and gave me the steps to execute the fix. With their permission, I'm posting their email below. It fixed the issue for me, and I hope it fixes it for you guys! Sincerely, Elli [1] http://code.google.com/p/support/issues/detail?id=3312#c42 ~~ Hi Eliezer, You're right, since OS X 10.6, it's possible for SVN to use the OS X keychain when verifying repositories. Versions uses the same configuration files as normal SVN, so you'd have to edit the same files. However, Versions currently isn't able to use this feature because it also has to run os OS X 10.4 and 10.5. In the next big release we have added support for the keychain ourselves, so you shouldn't get those errors anymore. There is also a way to explicitly add support for google yourself, so you can get rid of those errors right now. However, it involves a bit of Terminal magic. Here are the steps: 1) Start Terminal 2) curl -o ~/.subversion/google.pem http://www.geotrust.com/resources/extended-validation-ssl/certs/Equifax%20Secure%20Certificate%20Authority.crt This downloads the certificate that is used to sign the Google certificates. 3) open -e ~/.subversion/servers This opens the 'servers' configuration file where you can specify server-by-server configurations. 4) In this file, add something like the following at the bottom: [global] ssl-authority-files = /Users/pieter/.subversion/google.pem NOTE: Replace 'pieter' with your short username you use to login to OS X. 5) Save the file You should now be able to use Versions without getting annoying googlecode certificate warnings. If you try this, let me know if it works! - Pieter The Versions Team On Wed, Sep 15, 2010 at 8:08 PM, Eliezer Kanal wrote: > Hey folks - > > So, the problem described on your forums [1] about google > code certificates may be resolved. The bug referencing this > problem in google's bug database has two new comments [2] > which suggests that the only problem is a missing option in > the server config file. I tried to search for the config file used > by Versions, but I wasn't able to find it. Where is it located? I > don't know if this will fix the problem, but it's worth a shot. > Thanks - > > Eliezer Kanal > > [1] > http://groups.google.com/group/versions/browse_thread/thr > ead/8275849edd0c94ab > [2] http://code.google.com/p/support/issues/detail? > id=3312#c42 -- 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.
Re: Problem: Google Code SSL certificates - Reopened
I've started experiencing this problem now. After reading the archived discussion on the google, I wonder whether another certificate change is the culprit. I notice that the problem is currently marked as "fixed" in google's bug tracking database, and I added a comment asking to reopen it. Anyone else started having this problem again? Elli > > > > -- Original message -- > From: Dirk Stoop > Date: Dec 23 2009, 4:00 pm > Subject: Problem: Google Code SSL certificates - Reopened > To: Versions > > > Same here, > > The good people at Google Code say that a new cert has been issued two > days ago, so seeing those dialogs once more is expected. I'm hoping > they'll stop popping up in a day or so. > > The last time they fixed this was on thxgiving, so I'm crossing my > fingers for an xmas fix. ;) > > - Dirk > > the Versions team > > On Dec 23, 2:32 pm, jared wrote: > > > >> after another couple weeks without the problem, it has cropped up >> again, starting last night. :( -- 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.
Re: Problem: Google Code SSL certificates - Reopened
Same here, The good people at Google Code say that a new cert has been issued two days ago, so seeing those dialogs once more is expected. I'm hoping they'll stop popping up in a day or so. The last time they fixed this was on thxgiving, so I'm crossing my fingers for an xmas fix. ;) - Dirk the Versions team On Dec 23, 2:32 pm, jared wrote: > after another couple weeks without the problem, it has cropped up > again, starting last night. :( -- 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.
Re: Problem: Google Code SSL certificates - Reopened
after another couple weeks without the problem, it has cropped up again, starting last night. :( -- 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.
Re: Problem: Google Code SSL certificates - Reopened
The ticket at Google is filled with comments from people who have started seeing those dialogs again, they're working on it.. On Dec 9, 2:45 am, Nitin Madnani wrote: > I am a relatively new user of Versions and am seeing these popups > every few minutes on my Mac running snow leopard. Help! > > Nitin > > On Nov 26, 12:57 pm, Dirk Stoop wrote: > > > > > 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 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 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 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 acceptedcertificatefor a > > > > > particular URL and one that's being used on a new connection, SVN > > > > > chokes and asks the user to accept the newcertificate. > > > > > > 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.comcertificatethat 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 thecertificate > > > > > 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.
