Reputation: 491

Updating Subversion servers configuration file is not working

I'm trying to update my Subversion configuration so that it won't store passwords in plaintext. I understand that you need to update the configuration in the ~/.subversion/servers file to prevent this by adding a line: "store-plaintext-passwords = no".

I've done this, but my Subversion client continues to show me the standard warning:

———————————————————————————————————-
ATTENTION! Your password for authentication realm:

RainStorm Subversion Repository
can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the ‘store-plaintext-passwords’ option to either ‘yes’ or ‘no’ in
’/home/.subversion/servers’.
———————————————————————————————————-

I've tried logging out and logging back in again from the terminal, but that doesn't seem to make a difference. I assume that with SVN it's just a CLI tool and not a daemon that I have to restart, but I'm not positive.

What might be going on?

Upvotes: 5

Answers (3)

Lazy Badger

Reputation: 97292

I'm trying to update my Subversion configuration so that it won't store passwords in plaintext.

Does it store as plain text?

Windows passwords (for repositories) are always stored securely. It is only Linux where there has been an issue.

SVN 1.6 added two secure options for Linux users -- GNOME Keyring and KDE Kwallet. They are both compile-time options, so the binary you use has to have support for one or both of these.

The CollabNet binaries support GNOME Keyring. If you are using SVN from a graphical GNOME desktop it should "just work".

ADDON 1

Subversion clients store authentication data in ./subversion/auth for each realm.

To remove cached data go to “.subversion/auth/svn.simple” folder and delete the particular file.

Disable caching by opening “config” file in “.subversion” folder and setting the values of “store-passwords” and “store-auth-creds” to “no” or use –no-auth-cache as command line argument.

Somehow