Thanks, Brane. I think upgrading the client solved the issue. I will keep an eye on it.
D. On Wed, Sep 2, 2015 at 11:24 PM, Branko Čibej <br...@apache.org> wrote: > On 02.09.2015 21:58, Dmitriy Setrakyan wrote: > > On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej <br...@apache.org> wrote: > >> Also, any info about the platform you're using, and what kind of > >> authentication store you're using (KWallet? Gnome Keyring? OSX > >> Keychain?) would be useful here. > >> > > I am running on Mac. To my knowledge I am not using any authentication > > store. > > Keychain is probably enabled, but it doesn't usually play a role in > trusting the server (public) certificate. You're using the default svn > on OSX which is hacked a bit ... in fact so much that I can't find where > it's storing the server cert :) > > In any case: I wasn't able to reproduce what you describe, using > /usr/bin/svn; it did ask about trusting the cert the first time, and > apparently recorded that *somewhere*. > > > I should also mention that this started happening after Apache SVN was > > upgraded to a newer version recently. > > I expect it started happening when Infra replaced the server certs; > that's more likely, since trusting the cert is a completely client-side > decision. > > If you use Homebrew, I suggest you 'brew install subversion' which will > (currently) give you 1.8.14. > > -- Brane >
