Re: SVN changes

[Dmitriy Setrakyan]

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  wrote:

> On 02.09.2015 21:58, Dmitriy Setrakyan wrote:
> > On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej  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
>

Re: SVN changes

[Dmitriy Setrakyan]

On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej  wrote:

> On 02.09.2015 03:26, Dmitriy Setrakyan wrote:
> > Brane,
> >
> > Since recently I am constantly asked to confirm an SVN certificate before
> > updating or committing. This is really hurting my productivity :)
>
> Yeah, right, one extra keypress, heh.
>
> > Any advise on how this can be fixed?
>
> You should be able to permanently trust the certificate (that Infra
> replaced a while ago). Can you show me the command-line transcript from
> an svn commit? If the client doesn't offer you to permanently trust the
> cert, you're probably Doing Something Wrong™. Don't forget to include
> the output of 'svn --version'.
>

Brane, the situation is actually the reverse. The client always offers to
accept a certificate every time I execute any SVN command, even after  I
had already previously accepted it "permanently".

Here is the output of "svn --version":

--
dsetmac:root $ svn --version
svn, version 1.7.19 (r1643991)
   compiled Jun 17 2015, 13:48:11

Copyright (C) 2014 The Apache Software Foundation.
This software consists of contributions made by many people; see the NOTICE
file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using
Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
  - handles 'http' scheme
  - handles 'https' scheme
---


> -- Brane
>

Re: SVN changes

[Dmitriy Setrakyan]

On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej  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.

I should also mention that this started happening after Apache SVN was
upgraded to a newer version recently.

D.

Re: SVN changes

[Branko Čibej]

On 02.09.2015 09:27, Dmitriy Setrakyan wrote:
> On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej  wrote:
>
>> On 02.09.2015 03:26, Dmitriy Setrakyan wrote:
>>> Brane,
>>>
>>> Since recently I am constantly asked to confirm an SVN certificate before
>>> updating or committing. This is really hurting my productivity :)
>> Yeah, right, one extra keypress, heh.
>>
>>> Any advise on how this can be fixed?
>> You should be able to permanently trust the certificate (that Infra
>> replaced a while ago). Can you show me the command-line transcript from
>> an svn commit? If the client doesn't offer you to permanently trust the
>> cert, you're probably Doing Something Wrong™. Don't forget to include
>> the output of 'svn --version'.
>>
> Brane, the situation is actually the reverse. The client always offers to
> accept a certificate every time I execute any SVN command, even after  I
> had already previously accepted it "permanently".
>
> Here is the output of "svn --version":
>
> --
> dsetmac:root $ svn --version
> svn, version 1.7.19 (r1643991)
>compiled Jun 17 2015, 13:48:11
>
> Copyright (C) 2014 The Apache Software Foundation.
> This software consists of contributions made by many people; see the NOTICE
> file for more information.
> Subversion is open source software, see http://subversion.apache.org/
>
> The following repository access (RA) modules are available:
>
> * ra_neon : Module for accessing a repository via WebDAV protocol using
> Neon.
>   - handles 'http' scheme
>   - handles 'https' scheme
> * ra_svn : Module for accessing a repository using the svn network protocol.
>   - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
>   - handles 'file' scheme
> * ra_serf : Module for accessing a repository via WebDAV protocol using
> serf.
>   - handles 'http' scheme
>   - handles 'https' scheme
> ---

What's the value of the store-auth-creds setting in your
~/.subversion/servers or /etc/subversion/servers file?

-- Brane

Re: SVN changes

[Branko Čibej]

On 02.09.2015 11:29, Branko Čibej wrote:
> On 02.09.2015 09:27, Dmitriy Setrakyan wrote:
>> On Tue, Sep 1, 2015 at 8:01 PM, Branko Čibej  wrote:
>>
>>> On 02.09.2015 03:26, Dmitriy Setrakyan wrote:
 Brane,

 Since recently I am constantly asked to confirm an SVN certificate before
 updating or committing. This is really hurting my productivity :)
>>> Yeah, right, one extra keypress, heh.
>>>
 Any advise on how this can be fixed?
>>> You should be able to permanently trust the certificate (that Infra
>>> replaced a while ago). Can you show me the command-line transcript from
>>> an svn commit? If the client doesn't offer you to permanently trust the
>>> cert, you're probably Doing Something Wrong™. Don't forget to include
>>> the output of 'svn --version'.
>>>
>> Brane, the situation is actually the reverse. The client always offers to
>> accept a certificate every time I execute any SVN command, even after  I
>> had already previously accepted it "permanently".
>>
>> Here is the output of "svn --version":
>>
>> --
>> dsetmac:root $ svn --version
>> svn, version 1.7.19 (r1643991)
>>compiled Jun 17 2015, 13:48:11
>>
>> Copyright (C) 2014 The Apache Software Foundation.
>> This software consists of contributions made by many people; see the NOTICE
>> file for more information.
>> Subversion is open source software, see http://subversion.apache.org/
>>
>> The following repository access (RA) modules are available:
>>
>> * ra_neon : Module for accessing a repository via WebDAV protocol using
>> Neon.
>>   - handles 'http' scheme
>>   - handles 'https' scheme
>> * ra_svn : Module for accessing a repository using the svn network protocol.
>>   - handles 'svn' scheme
>> * ra_local : Module for accessing a repository on local disk.
>>   - handles 'file' scheme
>> * ra_serf : Module for accessing a repository via WebDAV protocol using
>> serf.
>>   - handles 'http' scheme
>>   - handles 'https' scheme
>> ---
> What's the value of the store-auth-creds setting in your
> ~/.subversion/servers or /etc/subversion/servers file?

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.

-- Brane