It is not possible to make SVN storage passwords, even if the configuration is configured so that it allows

Question

I did everything that the book wrote, i.e. deleted authentication files from .subversion / auth and explicitly set the appropriate configuration parameters to yes , although this is the default value, the shell SVN commands request a password each time. The repository is on cvsdude.com, and the client is Linux. I also use the Subclipse plugin that caches the OK password.

I vaguely remember that when I started working with him, the team requested interactively if I wanted to keep a clear password, and I said no. Can this choice be stored somewhere and take precedence over configuration?

Answer 1

Thanks to your comments, I found a problem - these are settings in the server file (do not store simple passwords). I wonder why this redundancy exists in the [auth] section of the configuration file. The SVN book also does not mention this when it comes to storing passwords.

Answer 2

In the latest versions of Subversion (~ 1.8), you can configure password caching through $HOME/.subversion/servers :

 [global] store-passwords = yes store-plaintext-passwords = yes 

But depending on your system, this may not be enough. If this is not the case, make sure $HOME/.subversion/config contains:

 [auth] password-stores = 

This means that the password-store variable is explicitly set with an empty string (the background is that svn now contains support for some key agent tools), and the interface with default elements can be fragile, which silently ignores the above parameters and behavior without caching).

When using svn for the first time, the $HOME/.subversion is created after the first svn operation — for example, during the first check. Subversion then creates the specified files and fills them with the most important parameters - commented out, including some documentation.

Thus, it makes sense to move the old $HOME/.subversion to have a specific starting point.

Another mistake is permissions, that is, files that cannot be read in $HOME/.subversion , but this is not often a problem, because when svn creates them, it takes care of the correct permissions (for example, only the auth directory that the user reads, not group / all, regardless of umask configured).

Answer 3

I would like to provide a detailed answer if it helps someone in the future.

Subversion 1.6 and later will cache your default username and password, however it will not cache plaintext passwords unless you explicitly allow this via the command line or change the configuration of Subversion.

If you checked your working copy using the --username and --password options, you will see the following message:

 ----------------------------------------------------------------------- ATTENTION! Your password for authentication realm: <https://subversion.assembla.com:443> Assembla Restricted Area 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 '~/.subversion/servers'. ----------------------------------------------------------------------- Store password unencrypted (yes/no)? 

So, as indicated in the message, subversion will keep the password unencrypted if you enter yes. If you do this, you will not need to add the --username or --password options when executing svn commands in the future.

However, if you prefer not to see this prompt at all, you can change the global configuration for your Subversion client by changing the configuration file called the “server” on your local computer. It is stored here:

 ~/.subversion/server 

You will need to add the following lines to the "server" file:

 [global] store-plaintext-passwords = yes 

With this change, you need to run the svn command using the --username and --password options once. Subversion will then automatically save your credentials without the above hint.

For more information about disabling this warning about caching passwords in text form, see the Subversion 1.6 Security Improvements blog.

Answer 4

I ran into the same problem and believe that I installed all the relevant configs in .subversion / servers and .subversion / config, also tried to remove .subversion / auth, etc., but to no avail.

I ended up saving credentials by moving the .subversion directory (or deleting it will work too) and running svn co. I received the following message:

 ----------------------------------------------------------------------- ATTENTION! Your password for authentication realm: <http://sweeney:80> 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/davids/.subversion/servers'. ----------------------------------------------------------------------- Store password unencrypted (yes/no)? 

I typed yes and then received the same message. Stubbornly, I again typed "yes." Now my password seems to be saved.

Somewhat surprisingly, looking at the configuration in .subversion, none of the options were uncommented; they are all set to default values, so I assume that I will have to answer this warning twice to save the password for another server in the future.

Hope this helps.

Answer 5

I needed to make changes to the server file to make this work for me

 # Password / passphrase caching parameters: store-passwords = yes store-plaintext-passwords = yes 

Answer 6

Delete the old saved password, for example rm ~ / .subversion / auth / svn.simple / * . I tried all other suggestions and it helped me.

Answer 7

You can use gnome-keyring even without X. You must run

 export `gnome-keyring-daemon` 

upon logging in and

 kill $GNOME_KEYRING_PID 

before logging out.

Then you can use the keyring_tool command line utility.

Answer 8

I think I found a useful hint here: http://svn.haxx.se/users/archive-2013-07/0094.shtml

As I understand it, the client forgot to check whether gpg-agent is running now.

It by default adds "passtype" = "gpg-agent" to ~/.subversion/auth/svn.simple/ -cache files.

This is mistake!

As a solution (and to avoid changing the cache password of the files in ~. / Subversion / auth / svn.simple / manually) delete this file (but make a copy of the save).

Add a line to ~/.subversion/config ([auth] section):

 password-stores= 

(CONSIDER: null! This prevents the client from choosing any wrong things and accepting the “simple” ones.)

Now, for example, try:

 svn up 

Subversion now warns you of saving simple passwords.

If you have no problem with this, enter yes and everything will be fine.

Subversion then created a cache file for a specific server, and you can delete the password-stores -entry again.

Answer 9

On Windows with slikSVN, I had the same problem, but only with one of the projects, so I went to% AppData% \ Roaming \ Subversion \ auth \ svn.simple and deleted the file containing this project information.

The next SVN command I typed in asked for a password and created the file again, and now it works fine.

Perhaps the fact that I changed the configuration and the server files also helped, but it did not work until I deleted this file (and it also worked with the previous configuration, until the server had a password problem and the administrator reset permissions )

Answer 10

From what I read in the previous answers, none of them worked. What I found to work for me can be a combination of things or this last step, which is to open the keychain application, find the corresponding key.

Right-click and select "get information." Click the access control section at the top. Then click "Allow all applications to access this item." Although this may do something unintentional.

Answer 11

If you are trying to reset authentication on an existing working copy, I would recommend that you check the new copy after making all the above changes. This was the only thing that worked for me when I tried to release the project using the maven-release plugin (which uses the saved svn credentials to automatically commit your tags, etc.)

Answer 12

For some odd reason, my .subversion folder did not belong to me, and SVN did not save the password certificates.

I just did sudo chown -R me ~/.subversion and now everything works!

Answer 13

Remember that there is a difference in storing passwords between svn co / up and svn log!

I tried all the hints above and always tried to check with 'svn log' - the svn team always asked me again and again about the password, regardless of whether the store-plaintext-password parameters were set correctly or yes. But when I did a new check or update, I suddenly got the right behavior and my password got saved

I guess this is a bug for subversion to have different password storage handling for different teams - at least I haven't read about this before.

Answer 14

I experienced such problems after changing the password and cured the removal of the SVN configuration (and thus recreated it from scratch).

Answer 15

Delete the files from the directory below:

For Windows:

For example:

C: \ Users \ abcd.xyz \ AppData \ Roaming \ Subversion \ Auth \ svn.simple

abcd.xyz -> username

Note. Delete all files. These files contain metadata about the statement. The next time you store your password, it will automatically create a file here.

Remove the .keyring file from the STS / Eclipse installation. Stop Eclipse and delete the file.

For example:

D: \ Executables \ New STS \ STS-3.5.0-e4.3.2-Win64 \ Configuration \ org.eclipse.core.runtime -. > Keychain

Answer 16

The solution that worked for me (not even the best solution, at least led me to flight) was to give my local user all permissions for the ~ / .subversion directory and subdirectories. Then I could quickly perform operations on subversion without prompting username and password.