Opened 14 years ago
Closed 14 years ago
#25765 closed defect (invalid)
subversion-1.6.12 http auth via keychain broken
Reported by: | marcus@… | Owned by: | danielluke (Daniel J. Luke) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | j.bugzilla2@… | |
Port: | subversion |
Description
For the last few versions of subversion 1.6, keychain storage of subversion http authentication details has stopped working for me on two different machines. Every time I do an 'svn up' or commit, it asks for my password, where previously it was remembered. The id and pass are present and correct in the keychain, and the same keychain entry works fine where it's used on a trac installation (at the same domain with same valid SSL cert). I'm running OS X 10.6.4 and my svn server is running apache 2.2.14 with libapache2-svn 1.6.6 (stock Ubuntu Lucid packages)
Change History (7)
comment:1 Changed 14 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 14 years ago by danielluke (Daniel J. Luke)
Owner: | changed from macports-tickets@… to dluke@… |
---|---|
Status: | new → assigned |
comment:3 Changed 14 years ago by danielluke (Daniel J. Luke)
Port: | subversion added |
---|
comment:5 Changed 14 years ago by marcus@…
Seems that svn gets a bit confused sometimes. I followed this advice to delete the auth entry I was having trouble with (in ~/.subversion/auth/svn.simple/
). The next time I did an svn up it asked for a password (as expected), then I did it again and it asked for keychain access, next time it worked without asking anything.
The auth files look different before and after. Original looked like this:
K 15 svn:realmstring V 78 ...
After recreating it started like this:
K 8 passtype V 8 keychain K 15 svn:realmstring V 78 ...
HTH!
comment:6 Changed 14 years ago by j.bugzilla2@…
Inspired by the last post I looked into my problem again and discovered that it was quite simple, but different than marcus's issue. Somehow my ~/.subversion directory and all its contents were owned by root, not my user. I can't figure out how that happened as I installed MacPorts SVN immediately after installing Snow Leopard. As they were empty and had no config settings applied, I just deleted the directory and let subversion recreate it.
comment:7 Changed 14 years ago by danielluke (Daniel J. Luke)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
You should probably try to resolve this with upstream.
If upstream finds a problem, we can probably include a patch in the macports subversion until it ends up in a release.