You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bebop52 <gr...@googlemail.com> on 2010/09/14 07:47:14 UTC
Re: Ubuntu: store user credentials for svn-client
Thank you Larry, sorry for the late reply (holidays).
I'm still struggling with the same problem. Here is the whole error-
message (I translated the German parts) commiting a Change in a
Latexfile with Emacs VC from Ubuntu 10.04:
"""Login: <https://xyz.googlecode.com:443> Google Code Subversion
Repository
Password for »myLinuxUsername«: Login: <https://xyz.googlecode.com:
443> Google Code Subversion Repository
Username: svn: Transmission failed (Details folllow):
svn: MKACTIVITY from »/svn/!svn/act/
87b61f4b-1512-4235-82d2-6541103d5e74«: Authorisation failed: Could not
authenticate to server: rejected Basic challenge (https://
xyz.googlecode.com)"""
I did not change anything in my
~/.subversion/servers
file, so everything is commented out.
In my
~/.subversion/config
file I have something like this:
[groups]
# group1 = *.collab.net
myProject = https://xyz.googlecode.com/svn/trunk/
# myProject = https://xyz.googlecode.com/ did not work either
### Information for myProject:
[myProject]
# http-proxy-host = proxy1.some-domain-name.com
# http-proxy-port = 80
# http-proxy-username = blah
# http-proxy-password = doubleblah
# http-timeout = 60
# http-auth-types = basic;digest;negotiate #uncommenting this did not
work
# neon-debug-mask = 130
store-plaintext-passwords = yes #don't care about secutity in this
case
username = myGoogleCodeUsername
Authentication should use myGoogleCodeUsername instead of
myLinuxUsername and prompt me for a password (?)
So my (very basic newbie) question remains:
How do I configure subversion on Ubuntu 10.04 to be able to
authenticate to a GoogleCode Repository?
Thanks for any help.
On 30 Aug., 16:13, Larry Evans <cp...@suddenlink.net> wrote:
> On 08/27/10 11:02, Larry Evans wrote:
> [snip]
>
>
>
> > I can't help but can sympathize. I found a very similar problem
> > after upgrading ubuntu 8.04 -> ubuntu 10.04.
>
> > However, my symptoms were slightly different. I got the:
>
> > Could not authenticate
>
> > message but before that I got some query containing "gnome keyring".
>
> > Here's the actual session:
>
> > [CODE]
> > ~/prog_dev/boost-svn/ro/sandbox/rw/variadic_templates $ svn commit -m
> > "add macro, ARG_CONSTANCY, to test driver"
> > Password for '(null)' GNOME keyring:
> > svn: Commit failed (details follow):
> > svn: MKACTIVITY of
> > '/svn/boost/!svn/act/018d0a5a-eee7-49b3-b42e-b5295ef7b8f8':
> > authorization failed: Could not authenticate to server: rejected Basic
> > challenge (https://svn.boost.org)
> > ~/prog_dev/boost-svn/ro/sandbox/rw/variadic_templates $
> > [/CODE]
>
> > So, I'd like to echo bebop52's plea for help.
>
> > -Larry
>
> The solution my problem is in:
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessa...
Re: Ubuntu: store user credentials for svn-client
Posted by bebop52 <gr...@googlemail.com>.
Hi Michael,
thanks for your helpful reply.
I did find a solution for the problem recently:
I installed a GUI-Client (SVN-Workbench) and did one Commit with this
client, using the dialog-windows. This worked out, and SVN-Workbench
wrote a cache file with my user credentials in the ~/.subversion/auth/
svn.simple directory (K=Key, V=Value):
K 8
passtype
V 6
simple
K 8
password
V 12
myGoogleCodePassword
K 15
svn:realmstring
V 70
<https://xyz.googlecode.com:443> Google Code Subversion Repository
K 8
username
V 7
myGoogleCodeUsername
END
>From this moment on I could use Emacs VC for my project and did not
need SVN-Workbench anymore. But I still did not understand whats going
on. Reading your mail and the links it seems clear now that Subversion
just used my Ubuntu username and password from GNOME Keyring and
therefore never prompted me for my Google Code credentials:
""You should be able to disable support for GNOME Keyring (and KDE
Wallet,
> for that matter) altogether by specifying "password-stores" accordingly
> in the "[auth]" section of your config file""
Beeing quite new to Linux I had never heard of GNOME Keyring and KDE
Wallet before, and I had no idea that such a simple cache-file in the /
auth/svn.simple directory is all thats needed.
Of course storing the plain text password on disk leaves room to
improvement, but for this project I'm happy it works, next project I
worry about security...
cheers
b.
On 22 Sep., 17:27, Michael Diers <md...@elegosoft.com> wrote:
> On 2010-09-14 09:47, bebop52 wrote:
>
> > Thank you Larry, sorry for the late reply (holidays).
> > I'm still struggling with the same problem. Here is the whole error-
> > message (I translated the German parts) commiting a Change in a
> > Latexfile with Emacs VC from Ubuntu 10.04:
>
> Hi,
>
> you don't need to translate anything if you run Subversion in an English
> locale setting:
>
> env LANG=en_US.utf8 svn ...
>
> To find out what locales are available, run "locale -a".
>
>
>
>
>
> > """Login: <https://xyz.googlecode.com:443> Google Code Subversion
> > Repository
> > Password for »myLinuxUsername«: Login: <https://xyz.googlecode.com:
> > 443> Google Code Subversion Repository
> > Username: svn: Transmission failed (Details folllow):
> > svn: MKACTIVITY from »/svn/!svn/act/
> > 87b61f4b-1512-4235-82d2-6541103d5e74«: Authorisation failed: Could not
> > authenticate to server: rejected Basic challenge (https://
> > xyz.googlecode.com)"""
>
> > I did not change anything in my
> > ~/.subversion/servers
> > file, so everything is commented out.
>
> > In my
> > ~/.subversion/config
> > file I have something like this:
>
> > [groups]
> > # group1 = *.collab.net
> > myProject =https://xyz.googlecode.com/svn/trunk/
> > # myProject =https://xyz.googlecode.com/ did not work either
>
> What about the following?
>
> myProject = xyz.googlecode.com
>
>
>
>
>
> > ### Information for myProject:
> > [myProject]
> > # http-proxy-host = proxy1.some-domain-name.com
> > # http-proxy-port = 80
> > # http-proxy-username = blah
> > # http-proxy-password = doubleblah
> > # http-timeout = 60
> > # http-auth-types = basic;digest;negotiate #uncommenting this did not
> > work
> > # neon-debug-mask = 130
> > store-plaintext-passwords = yes #don't care about secutity in this
> > case
> > username = myGoogleCodeUsername
>
> > Authentication should use myGoogleCodeUsername instead of
> > myLinuxUsername and prompt me for a password (?)
> > So my (very basic newbie) question remains:
> > How do I configure subversion on Ubuntu 10.04 to be able to
> > authenticate to a GoogleCode Repository?
> > Thanks for any help.
>
> What's in the "[auth]" section of your ~/.subversion/config?
>
> You should be able to disable support for GNOME Keyring (and KDE Wallet,
> for that matter) altogether by specifying "password-stores" accordingly
> in the "[auth]" section of your config file, like so:
>
> [auth]
> password-stores = keychain,windows-cryptoapi
>
> http://subversion.apache.org/faq.html#plaintext-passwords
>
> http://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html...
>
> http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn...
>
> Here's the beginning of a fresh ~/.subversion/config file. You can have
> svn generate one if you just move the existing ~/.subversion out of the
> way first:
>
> $ mv ~/.subversion ~/.subversion.keep.me
> $ svn lshttp://svn.apache.org/repos/asf/subversion
> $ cat ~/.subversion/config
>
> ### This file configures various client-side behaviors.
> ###
> ### The commented-out examples below are intended to demonstrate
> ### how to use this file.
>
> ### Section for authentication and authorization customizations.
> [auth]
> ### Set password stores used by Subversion. They should be
> ### delimited by spaces or commas. The order of values determines
> ### the order in which password stores are used.
> ### Valid password stores:
> ### gnome-keyring (Unix-like systems)
> ### kwallet (Unix-like systems)
> ### keychain (Mac OS X)
> ### windows-cryptoapi (Windows)
> # password-stores = gnome-keyring,kwallet
> ###
> ### Set KWallet wallet used by Subversion. If empty or unset,
> ### then the default network wallet will be used.
> # kwallet-wallet =
> ###
> ### Include PID (Process ID) in Subversion application name when
> ### using KWallet. It defaults to 'no'.
> # kwallet-svn-application-name-with-pid = yes
> ###
> ### The rest of this section in this file has been deprecated.
> ### Both 'store-passwords' and 'store-auth-creds' can now be
> ### specified in the 'servers' file in your config directory.
> ### Anything specified in this section is overridden by settings
> ### specified in the 'servers' file.
> ###
> ### Set store-passwords to 'no' to avoid storing passwords in the
> ### auth/ area of your config directory. It defaults to 'yes',
> ### but Subversion will never save your password to disk in
> ### plaintext unless you tell it to (see the 'servers' file).
> ### Note that this option only prevents saving of *new* passwords;
> ### it doesn't invalidate existing passwords. (To do that, remove
> ### the cache files by hand as described in the Subversion book.)
> # store-passwords = no
> ### Set store-auth-creds to 'no' to avoid storing any subversion
> ### credentials in the auth/ area of your config directory.
> ### It defaults to 'yes'. Note that this option only prevents
> ### saving of *new* credentials; it doesn't invalidate existing
> ### caches. (To do that, remove the cache files by hand.)
> # store-auth-creds = no
>
> ...
>
> --
> Michael Diers, elego Software Solutions GmbH,http://www.elego.de
>
> signature.asc
> < 1 KBAnzeigenHerunterladen
Re: Ubuntu: store user credentials for svn-client
Posted by bebop52 <gr...@googlemail.com>.
Hi Michael,
thanks for your helpful reply.
I did find a solution for the problem recently:
I installed a GUI-Client (SVN-Workbench) and did one Commit with this
client, using the dialog-windows. This worked out, and SVN-Workbench
wrote a cache file with my user credentials in the ~/.subversion/auth/
svn.simple directory (K=Key, V=Value):
K 8
passtype
V 6
simple
K 8
password
V 12
myGoogleCodePassword
K 15
svn:realmstring
V 70
<https://xyz.googlecode.com:443> Google Code Subversion Repository
K 8
username
V 7
myGoogleCodeUsername
END
Re: Ubuntu: store user credentials for svn-client
Posted by Michael Diers <md...@elegosoft.com>.
On 2010-09-14 09:47, bebop52 wrote:
> Thank you Larry, sorry for the late reply (holidays).
> I'm still struggling with the same problem. Here is the whole error-
> message (I translated the German parts) commiting a Change in a
> Latexfile with Emacs VC from Ubuntu 10.04:
Hi,
you don't need to translate anything if you run Subversion in an English
locale setting:
env LANG=en_US.utf8 svn ...
To find out what locales are available, run "locale -a".
> """Login: <https://xyz.googlecode.com:443> Google Code Subversion
> Repository
> Password for »myLinuxUsername«: Login: <https://xyz.googlecode.com:
> 443> Google Code Subversion Repository
> Username: svn: Transmission failed (Details folllow):
> svn: MKACTIVITY from »/svn/!svn/act/
> 87b61f4b-1512-4235-82d2-6541103d5e74«: Authorisation failed: Could not
> authenticate to server: rejected Basic challenge (https://
> xyz.googlecode.com)"""
>
> I did not change anything in my
> ~/.subversion/servers
> file, so everything is commented out.
>
> In my
> ~/.subversion/config
> file I have something like this:
>
> [groups]
> # group1 = *.collab.net
> myProject = https://xyz.googlecode.com/svn/trunk/
> # myProject = https://xyz.googlecode.com/ did not work either
What about the following?
myProject = xyz.googlecode.com
> ### Information for myProject:
> [myProject]
> # http-proxy-host = proxy1.some-domain-name.com
> # http-proxy-port = 80
> # http-proxy-username = blah
> # http-proxy-password = doubleblah
> # http-timeout = 60
> # http-auth-types = basic;digest;negotiate #uncommenting this did not
> work
> # neon-debug-mask = 130
> store-plaintext-passwords = yes #don't care about secutity in this
> case
> username = myGoogleCodeUsername
>
> Authentication should use myGoogleCodeUsername instead of
> myLinuxUsername and prompt me for a password (?)
> So my (very basic newbie) question remains:
> How do I configure subversion on Ubuntu 10.04 to be able to
> authenticate to a GoogleCode Repository?
> Thanks for any help.
What's in the "[auth]" section of your ~/.subversion/config?
You should be able to disable support for GNOME Keyring (and KDE Wallet,
for that matter) altogether by specifying "password-stores" accordingly
in the "[auth]" section of your config file, like so:
[auth]
password-stores = keychain,windows-cryptoapi
http://subversion.apache.org/faq.html#plaintext-passwords
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.credcache
http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.layout
Here's the beginning of a fresh ~/.subversion/config file. You can have
svn generate one if you just move the existing ~/.subversion out of the
way first:
$ mv ~/.subversion ~/.subversion.keep.me
$ svn ls http://svn.apache.org/repos/asf/subversion
$ cat ~/.subversion/config
### This file configures various client-side behaviors.
###
### The commented-out examples below are intended to demonstrate
### how to use this file.
### Section for authentication and authorization customizations.
[auth]
### Set password stores used by Subversion. They should be
### delimited by spaces or commas. The order of values determines
### the order in which password stores are used.
### Valid password stores:
### gnome-keyring (Unix-like systems)
### kwallet (Unix-like systems)
### keychain (Mac OS X)
### windows-cryptoapi (Windows)
# password-stores = gnome-keyring,kwallet
###
### Set KWallet wallet used by Subversion. If empty or unset,
### then the default network wallet will be used.
# kwallet-wallet =
###
### Include PID (Process ID) in Subversion application name when
### using KWallet. It defaults to 'no'.
# kwallet-svn-application-name-with-pid = yes
###
### The rest of this section in this file has been deprecated.
### Both 'store-passwords' and 'store-auth-creds' can now be
### specified in the 'servers' file in your config directory.
### Anything specified in this section is overridden by settings
### specified in the 'servers' file.
###
### Set store-passwords to 'no' to avoid storing passwords in the
### auth/ area of your config directory. It defaults to 'yes',
### but Subversion will never save your password to disk in
### plaintext unless you tell it to (see the 'servers' file).
### Note that this option only prevents saving of *new* passwords;
### it doesn't invalidate existing passwords. (To do that, remove
### the cache files by hand as described in the Subversion book.)
# store-passwords = no
### Set store-auth-creds to 'no' to avoid storing any subversion
### credentials in the auth/ area of your config directory.
### It defaults to 'yes'. Note that this option only prevents
### saving of *new* credentials; it doesn't invalidate existing
### caches. (To do that, remove the cache files by hand.)
# store-auth-creds = no
...
--
Michael Diers, elego Software Solutions GmbH, http://www.elego.de