subversion authentication "--no-auth-cache"

subversion authentication "--no-auth-cache"

[daniel.litschauer]

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

Hello,

I know variations of this question already popped up a few times, but I wasn’t able to find a answer that satisfied my needs.

Authentication when using subversion can be as easy as typing:

SRC_URI = "svn://myrepos/proj1;module=vip;protocol=http;rev=667;user=user;pswd=password"

As I said easy, but with the drawback that I have to save my username and password to a textfile. Subversion usually tries to find client credentials in a “ GNOME Keyring ” , “ KDE Wallet ” , or “ GnuPG Agent ” service and if there is nothing to find at ~/.subversion/auth. Read about it if you are interested ( http://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache ).

But this "system" is blocked by bitbake in the svn.py file ( https://github.com/openembedded/bitbake/blob/master/lib/bb/fetch2/svn.py ). At line 78 it states: options. append ( "--no-auth-cache" )

Is there a reason for this that I am not thinking about? And if there is no reason for this would it be possible to add a switch for this?

SRC_URI = "svn://myrepos/proj1;module=vip;protocol=http;rev=667;user=user;use_auth_cache=no"

Thank you in advance.

Yours sincerely,

Daniel

[-- Attachment #2: Type: text/html, Size: 1693 bytes --]

Re: [bitbake-devel] subversion authentication "--no-auth-cache"

[Richard Purdie]

On Mon, 2020-03-30 at 06:15 -0700, daniel.litschauer via
Lists.Openembedded.Org wrote:
> I know variations of this question already popped up a few times, but
> I wasn’t able to find a answer that satisfied my needs.
> 
> Authentication when using subversion can be as easy as typing:
> 
> SRC_URI =
> "svn://myrepos/proj1;module=vip;protocol=http;rev=667;user=user;pswd=
> password"
> As I said easy, but with the drawback that I have to save my username
> and password to a textfile. Subversion usually tries to find client
> credentials in a “GNOME Keyring”, “KDE Wallet”, or “GnuPG Agent”
> service and if there is nothing to find at ~/.subversion/auth. Read
> about it if you are interested.
> 
> But this "system" is blocked by bitbake in the svn.py file. At line
> 78 it states: options.append("--no-auth-cache")
> 
> Is there a reason for this that I am not thinking about? And if there
> is no reason for this would it be possible to add a switch for this?

I did look back in the history but the reasoning isn't clear. In
general it is bad for the system not to be self contained. Accessing
/home/ during a build would make a build hard to reproduce for someone
else.

> SRC_URI =
> "svn://myrepos/proj1;module=vip;protocol=http;rev=667;user=user;use_a
> uth_cache=no"
> Thank you in advance.

I think adding a parameter to enable this would seem reasonable
(leaving the default as is).

Cheers,

Richard

Re: subversion authentication "--no-auth-cache"

[daniel.litschauer]

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

Thank you for your reply!

I did test it now without the "use_auth_cache".

It works with the clear text caching at ~/.subversion/auth , but unfortunately it doesn't with the encrypted methods. It seems to me that this is the case because svn is depending on another application to retrieve it. Do you have any clue what I am missing and how I can add it to the HOSTTOOLS (at least I thing it needs to go there).

[-- Attachment #2: Type: text/html, Size: 458 bytes --]