blocks|key|24094|text|我遇到了同样的问题，并且相信我在..subversion/server和.+.subversion/config中设置了所有适当的配置，并尝试删除.+.subversion/auth等，但是没有结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|24095|最后，我通过移动.subversion目录(或者删除它也可以)并运行svn来保存凭据。我收到了以下信息：|24096|-----------------------------------------------------------------------
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)?+|code-block|syntax|javascript|24097|我输入了“是”，然后收到了同样的信息。我固执地又打了一遍“是”。现在我的密码似乎被保存了。|24098|有些令人惊讶的是，查看.subversion中的配置，没有一个设置是不注释的；它们都设置为默认设置，所以我想我必须回答这个警告两次，才能在将来为另一个服务器保存密码。|24099|希望这能有所帮助。|24100|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I ran into this same issue, and believe I set all the appropriate configs in .subversion/servers and .subversion/config, too, tried removing .subversion/auth, etc., but to no avail.

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

<pre><code>-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:

 &lt;http://sweeney:80&gt; 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)? 
</code></pre>

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

Somewhat surprisingly, looking at the configs in .subversion, none of the settings are uncommented; they're all set to the defaults, so I imagine I would have to answer this warning twice to save a password for a different server in the future.

Hope this helps.

blocks|key|24120|text|即使没有X，你也可以使用gnome键环。你应该跑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|24121|export+`gnome-keyring-daemon`|code-block|syntax|javascript|24122|在登录和|24123|kill+$GNOME_KEYRING_PID|24124|在退出之前。|24125|然后可以使用keyring_tool命令行实用程序。|offset|length|style|CODE|24126|entityMap^0|0|0|0|0|0|6|C|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$O|10|P|11|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

You may use the gnome-keyring even without X inited.
You should run 

<pre><code>export `gnome-keyring-daemon`
</code></pre>

on login and

<pre><code>kill $GNOME_KEYRING_PID
</code></pre>

before logout.

Then you can use <code>keyring_tool</code> commandline utility.

blocks|key|24149|text|感谢您的评论，我发现了这个问题--这是服务器文件中的设置(不要存储普通密码)。我想知道为什么配置文件的[auth]部分存在这种冗余。在谈到存储密码时，SVN书也没有提到这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|24150|entityMap|0|LINK|mutability|MUTABLE|url|http://svnbook.red-bean.com/^0|1F|6|23|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Thanks to your comments I found the problem - it's the settings in the servers file (don't store plain passwords). I wonder why there is this redundancy with the <code>[auth]</code> section of the configuration file. The <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">SVN book</a> also does not mention this when talking about storing passwords.

blocks|key|1317033|text|我需要对服务器文件进行更改，以使它为我工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317034|#+Password+/+passphrase+caching+parameters:
store-passwords+=+yes
store-plaintext-passwords+=+yes|code-block|syntax|javascript|1317035|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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

<pre><code># Password / passphrase caching parameters:
store-passwords = yes
store-plaintext-passwords = yes
</code></pre>

blocks|key|1574552|text|从我在前面的答案中所读到的，这些都没有用。我发现对我有用的可能是一些东西的组合，或者是最后一步，那就是打开密钥链应用程序，找到问题的关键。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1574553|右击并转到“获取信息”。单击顶部的访问控制部分。然后单击“允许所有应用程序访问此项”。虽然这可能会做一些意想不到的事情。|1574554|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

From what I read in the previous answers, none of these worked. What I found to work for me could be a combination of things or this final step which is to open the keychain app, find the key in question.

Right-click and go to "get info". Click access control section on the top. Then click the "Allow all applications to access this item". Although this might do something unintended.

blocks|key|1574615|text|我想提交一个详细的答案，以防它对未来的人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1574616|Subversion+1.6及更高版本默认情况下将缓存您的用户名和密码，但除非您通过命令行或通过更改Subversion配置显式允许密码，否则它不会以明文形式缓存密码。|1574617|如果使用--用户名和--密码选项签出工作副本，您将看到以下消息：|1574618|-----------------------------------------------------------------------
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)?+|code-block|syntax|javascript|1574619|因此，正如消息中提到的，subversion只有在输入'yes‘时才会保存未加密的密码。如果这样做，那么以后在执行svn命令时不需要添加--用户名或--密码选项。|1574620|但是，如果您根本不想看到这个提示，则可以通过更改本地计算机上名为"server“的配置文件来更改Subversion客户端的全局配置。它存放在这里：|1574621|~/.subversion/server|1574622|您需要在“服务器”文件中添加以下行：|1574623|[global]
store-plaintext-passwords+=+yes|1574624|使用此更改后，只需使用--用户名和--密码选项执行svn命令一次。然后Subversion将在没有上述提示的情况下自动保存凭据。|1574625|有关禁用有关在纯文本中缓存密码的警告的详细信息，请参阅Subversion+1.6安全改进博客文章。|offset|length|1574626|entityMap|0|LINK|mutability|MUTABLE|url|http://www.linuxforu.com/2009/05/subversion-16-security-improvements-illustrated/^0|0|0|0|0|0|0|0|0|0|0|R|I|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|1E|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|1G|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1I|8|@]|9|@$Y|1J|Z|1K|1|1L]]|A|$]]|$1|10|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

I would like to submit a detailed answer in case it helps someone in future.

Subversion 1.6 and later will cache your username and password by default however it will not cache the passwords in plaintext unless you explicitly allow it via the command line or by changing the Subversion configuration. 

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

<pre><code>-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:

&lt;https://subversion.assembla.com:443&gt; 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)? 
</code></pre>

 

So as mentioned in the message, subversion will only save the password unencrypted if you enter 'yes'. If you do so then you should not need to add the --username or --password options when performing svn commands in 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 "server" on your local machine. It is stored here:

<pre><code>~/.subversion/server
</code></pre>

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

<pre><code>[global]
store-plaintext-passwords = yes
</code></pre>

With this change, you only need to perform an svn command using the --username and --password options once. Then Subversion will automatically save your credentials without the above prompt. 

For more information on disabling this warning about caching passwords in plain text see the <a href="http://www.linuxforu.com/2009/05/subversion-16-security-improvements-illustrated/" rel="noreferrer">Subversion 1.6 Security Improvements</a> blog post.

blocks|key|1574680|text|一个对我有用的解决方案(至少不是一个更好的解决方案，至少帮了我的忙)，它授予我的本地用户对~/..subversion目录和子目录的所有权限。然后，我可以在没有提示用户名和密码的情况下对subversion进行快速操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1574681|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

A solution that worked for me (even isnt' the better solution, at least bailed me out), it's to grant my local user all permissions to ~/.subversion directory and subdirectorys. Then i could do operations on subversion fast without prompt username and password.

blocks|key|24373|text|使用Subversion的最新版本(~+1.8)，您可以通过$HOME/.subversion/servers配置密码缓存|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|24374|[global]
store-passwords+=+yes
store-plaintext-passwords+=+yes|code-block|syntax|javascript|24375|但取决于您的系统，这可能是不够的。如果不是，请确保$HOME/.subversion/config包含：|24376|[auth]
password-stores+=|24377|这意味着变量密码存储被显式地设置为空字符串(背景是svn现在包含对某些密钥代理工具的支持，并且默认配置工具的接口可能是脆弱的，从而导致对上述选项的沉默忽略和非缓存行为)。|24378|当第一次使用svn时，在第一次svn操作之后创建分级$HOME/.subversion，例如在执行第一次签出时。Subversion然后创建上述文件并用最重要的选项填充它们--注释掉，包括一些文档。|24379|因此，将旧的$HOME/.subversion目录移开以具有一个定义良好的起点也是有意义的。|24380|另一个缺陷是权限--即在$HOME/.subversion下无法读取的文件--但这不应该经常是问题所在，因为当svn创建它们时，它会处理正确的权限(例如，auth目录仅由用户读取，而不是由组/all读取，与配置的umask无关)。|24381|entityMap^0|U|P|0|0|P|O|0|0|0|Q|H|0|6|H|0|C|H|1J|3|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|16|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|X|$]]

With recent versions of Subversion (~ 1.8) you can configure password caching via <code>$HOME/.subversion/servers</code>:

<pre><code>[global]
store-passwords = yes
store-plaintext-passwords = yes
</code></pre>

But depending on your system this may be not enough. If it is not, make sure that <code>$HOME/.subversion/config</code> contains:

<pre><code>[auth]
password-stores =
</code></pre>

Which means that the variable password-stores is explicitly set to the empty string (background is that svn now contains support for some key-agent tools - and the interfacing to the default configured ones may be fragile - resulting in silent ignoring of the above options and non-caching behaviour).

When using svn for the first time, the hierachy <code>$HOME/.subversion</code> is created after the first svn operation - e.g. when doing the first checkout. Subversion creates then the mentioned files and fills them with the most important options - commented out, including some documentation.

Thus, it also makes sense to move an old <code>$HOME/.subversion</code> directory away to have a well-defined starting point.

Another pitfall are permissions - i.e. files which are not readable under <code>$HOME/.subversion</code> - but this should not often be the problem, because when <code>svn</code> creates them, it takes care of the right permissions (e.g. the auth directory is only readable by the user then, not by the group/all, independent of the configured umask).

blocks|key|1317102|text|如果您试图重置现有工作副本上的身份验证，我建议您在完成上述所有更改后签出一个新副本。当我试图用maven发布插件(它使用存储的svn凭据来自动提交标记等)发布项目时，这是唯一对我有用的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317103|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are trying to reset the authentication on an existing working copy, I'd recommend you checkout a fresh copy after you do all of the above changes. This was the only thing that worked for me when I was trying to release the project with the maven-release-plugin (which uses stored svn credentials in order to auto commit your tags, etc...)

blocks|key|1574787|text|我想我在这里找到了一个有用的提示：http://svn.haxx.se/users/archive-2013-07/0094.shtml|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1574788|据我所知，客户端忘了检查"gpg-agent“是否正在运行。|1574789|默认情况下，它是将"passtype“=+"gpg-agent”插入到~/.subversion/auth/svn.simple/-缓存文件中。|style|CODE|1574790|这是个错误！|1574791|作为一种解决方案(并避免修改~./subversion/auth/svn.simple/手工中的密码缓存文件)，删除这些文件(但要制作一个保存副本)。|1574792|将该行添加到~/.subversion/config+(auth-节)中：|1574793|password-stores=|code-block|syntax|javascript|1574794|(考虑一下:空值！这可以防止客户选择错误的内容，并假设“简单”。)|1574795|现在试一试：|1574796|svn+up|1574797|Subversion现在将警告您保存普通密码。|1574798|如果你对此没有异议，输入“是”，一切都会好起来的。|1574799|在此之后，Subversion为特定服务器创建了一个缓存文件，您可以再次删除“密码存储”-entry。|1574800|entityMap|0|LINK|mutability|MUTABLE|url|http://svn.haxx.se/users/archive-2013-07/0094.shtml^0|H|1F|0|0|0|Z|U|0|0|0|6|K|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1J|8|@$A|1K|B|1L|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1M|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1N|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1O|8|@$A|1P|B|1Q|H|I]]|9|@]|C|$]]|$1|P|3|Q|5|R|7|1R|8|@]|9|@]|C|$S|T]]|$1|U|3|V|5|6|7|1S|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1T|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|R|7|1U|8|@]|9|@]|C|$S|T]]|$1|10|3|11|5|6|7|1V|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|1W|8|@]|9|@]|C|$]]|$1|14|3|15|5|6|7|1X|8|@]|9|@]|C|$]]|$1|16|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]]|17|$18|$5|19|1A|1B|C|$1C|1D]]]]

I think I've found a helpful hint here:
<a href="http://svn.haxx.se/users/archive-2013-07/0094.shtml" rel="noreferrer">http://svn.haxx.se/users/archive-2013-07/0094.shtml</a>

As I understood, the client forgot to check if a "gpg-agent" is currently running.

It is inserting the "passtype" = "gpg-agent" into the <code>~/.subversion/auth/svn.simple/</code>-cache-files by default.

That is a mistake!

As a solution (and to avoid to alter the password-cachefiles in ~./subversion/auth/svn.simple/ by hand) remove these file (but make a save-copy).

Add the line, into <code>~/.subversion/config</code> ([auth]-section):

<pre><code>password-stores=
</code></pre>

(CONSIDER: the empty value! This prevents the client from choosing any wrong stuff and assume "simple".)

Now e.g. try a:

<pre><code>svn up
</code></pre>

Subversion will now warn you to save plain passwords.

If you got no problem with that, type "yes" and all is fine again.

After that, Subversion has created a cache-file for a particular server, and you can remove the "password-stores"-entry again.

blocks|key|1574825|text|由于一些奇怪的原因，我的.subversion文件夹不属于我，SVN也不会保存密码证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1574826|我刚做了一个sudo+chown+-R+me+~/.subversion，现在一切都正常了！|offset|length|style|CODE|1574827|entityMap^0|0|6|U|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For some odd reason, my .subversion folder was not owned by me and SVN wouldn't save certificates of passwords.

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

blocks|key|24551|text|请注意，在svn+co/up和svn日志之间存在与密码存储有关的不同行为！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|24552|我尝试了上面所有的提示，并且总是尝试用'svn日志‘来验证--+svn命令总是一次又一次地问我密码，不管存储明文密码是正确的还是正确的。但是，当我做了一个新的结帐或更新，我突然有正确的行为，我的密码得到保存。|24553|我认为这是一个颠覆的错误，它对不同命令的密码存储有不同的处理方式--至少我以前没有在哪里读到过。|24554|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Please be aware that there is a difference behaviour related to the password storing between a svn co/up and a svn log!

I tried all of the hints above and alway tried to verify with 'svn log' -- the svn command always asked me again and again for password, no matter if store-plaintext-passwords was set correctly to ask or yes. But when I made a new checkout or update I suddenly had the correct behaviour and my password got save

I assume this is a bug to subversion to have different handling of password storing for the different commands -- at least I read no where about that before.

blocks|key|1317153|text|在Windows上，我也有同样的问题，但只有其中一个项目，所以我进入%25AppData%25\Roaming\Subversion\auth\svn.simple并删除了包含该项目信息的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317154|我输入的下一个SVN命令询问密码并再次创建文件，现在它运行得很好。|1317155|也许我更改了配置和服务器文件也有帮助，但直到我删除了该文件(直到服务器上出现密码问题和管理员重置权限之前，它也使用了以前的配置)，它才能正常工作。|1317156|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

On Windows with slikSVN, I was having the same issue, but only with one of the projects, so I went in %AppData%\Roaming\Subversion\auth\svn.simple and deleted the file containing that project information.

The next SVN command I typed asked for the password and created the file again and now it's running great.

Maybe the fact I changed configuration and servers files helped too, but it was not working till I deleted that file (and it was working also with the previous configuration till there was a password issue on the server and the administrator reset permissions).

blocks|key|1317165|text|在密码更改后，我遇到了这样的问题，并将其修复，删除SVN配置(从而从头重新创建它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317166|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I experienced such problems after a password change and cured it deleting the SVN configuration (and thus recreating it from scratch).

blocks|key|1574944|text|删除旧的存储密码，如~/.subversion/auth/svn.simple/*.+rm我已经尝试了所有其他的建议，这就是对我有用的地方。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1574945|entityMap^0|17|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Delete old stored password like rm ~/.subversion/auth/svn.simple/*. I have tried every other suggestion and this is what worked for me.

blocks|key|1317176|text|从以下目录删除文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317177|适用于Windows：|1317178|例如：|1317179|C:\Users\abcd.xyz\AppData\Roaming\Subversion\auth\svn.simple|blockquote|1317180|abcd.xyz-->username|offset|length|style|BOLD|1317181|注意:删除所有文件。这些文件包含有关结帐的元数据。下次当您存储密码时，它将自动在这里创建一个文件。|1317182|从.keyring+STS/Eclipse安装中删除文件。停止Eclipse并删除文件。|CODE|1317183|1317184|D：\可执行文件\新的STS\STS-3.5.0-e4.3.2-win64\configuration\org.eclipse.core.runtime+-->..keyring|1317185|entityMap^0|0|0|0|0|0|J|0|0|1|8|Q|I|0|0|3|0|0|2H|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@$K|13|L|14|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|15|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|16|8|@$K|17|L|18|M|S]|$K|19|L|1A|M|N]]|9|@]|A|$]]|$1|T|3|E|5|6|7|1B|8|@$K|1C|L|1D|M|N]]|9|@]|A|$]]|$1|U|3|V|5|H|7|1E|8|@$K|1F|L|1G|M|N]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|X|$]]

Delete files from the below directory:

For Windows:

For example:

<blockquote>
 C:\Users\abcd.xyz\AppData\Roaming\Subversion\auth\svn.simple
</blockquote>

abcd.xyz-->username

Note: Delete all files. These files contain meta data about the checkout. The next time when you store your password it will automatically create a file here.

Delete the <code>.keyring</code> file from your STS/Eclipse installation. Stop Eclipse and delete the file.

For example:

<blockquote>
 D:\Executables\New
 STS\STS-3.5.0-e4.3.2-win64\configuration\org.eclipse.core.runtime
 -->.keyring
</blockquote>

blocks|key|24687|text|不管我做了什么，对我都没有用。我检查了所有可能的选项，配置文件和谷歌的100页关于这个问题。最后我放弃了，把这个放进了我的.bashrc|type|unstyled|depth|inlineStyleRanges|entityRanges|data|24688|alias+svn='svn+--password+<mypassword>'|code-block|syntax|javascript|24689|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Nothing worked for me, no matter what I've done. I checked all possible options, config files and hundred pages in google about this problem. Eventually I gave up and just put this into my .bashrc

<pre><code>alias svn='svn --password &lt;mypassword&gt;'
</code></pre>

blocks|key|24697|text|自从SVN+1.12+(2019年4月)以来，你基本上不能。来自发行说明。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|24698|在类似Unix的系统上，现在默认情况下，在编译时禁用磁盘上明文密码的客户端存储。建议使用基于Gnome+Keyring、K皮夹或GPG的密码缓存机制.
此更改不影响Windows或Mac平台，在这些平台中，密码始终存储在加密表示形式中。|blockquote|24699|所以..。除非您编译了自己的SVN客户端，否则现在很可能有一个不允许存储明文密码的版本。|24700|顺便说一句，您以前使用的明文密码甚至可能在Subversion升级之后停止工作。|24701|但是，如果您不想在每次会话中输入一次密码，那么使用gpg-agent是非常容易的。只要用gpg-agent+--daemon启动它，运行svn命令输入密码，下一个命令就不会再请求它了。|style|CODE|24702|entityMap|0|LINK|mutability|MUTABLE|url|https://subversion.apache.org/docs/release-notes/1.12#client-server-improvements^0|W|4|0|0|0|0|0|P|9|18|I|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|13|8|@$A|14|B|15|M|N]|$A|16|B|17|M|N]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Since SVN 1.12 (April 2019), you basically can't. From the <a href="https://subversion.apache.org/docs/release-notes/1.12#client-server-improvements" rel="noreferrer">Release Notes</a>:

<blockquote>
 On Unix-like systems, client-side storage of passwords in plaintext on
 disk is now disabled by default at compile-time. Password caching
 mechanisms based on Gnome Keyring, Kwallet, or GPG-Agent, are
 recommended instead.
 
 This change does not affect Windows or Mac OS platforms, where
 passwords have always been stored in an encrypted representation.
</blockquote>

So... unless you compiled your own SVN client, you now most probably have a version that does not allow plaintext passwords to be stored.

By the way, your previously working plaintext password may even stop working after a Subversion upgrade.

If you don't bother entering the password once per session, using <code>gpg-agent</code> is quite easy, though. Just start it with <code>gpg-agent --daemon</code>, run your svn command entering the password, and the next command won't request it anymore.

blocks|key|1317237|text|维尼|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317238|我想我什么都试过了：|1317239|检查服务器配置|unordered-list-item|1317240|检查了~/..subversion权限，全部600|1317241|检查了~/..subversion/config文件|1317242|存储-明文-密码=是|1317243|存储-密码=是|1317244|商店-auth-creds=+yes+|1317245|以上都是用我的用户名在[global]和[groups]部分做的吗？|offset|length|style|CODE|1317246|1317247|1317248|检查了~/..subversion/servers文件|1317249|与上述相同|1317250|1317251|对于所有配置文件，我验证了所有部分，还输入了一个错误的参数，并验证svn客户端停止工作(因此，正在读取配置文件)。|1317252|删除并重新创建~/..subversion/auth目录|1317253|检查$HOME/.subversion/config禁用密码中的客户端配置是否存储：|1317254|[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.
#+password-stores+=+gpg-agent,gnome-keyring,kwallet
###+To+disable+all+password+stores,+use+an+empty+list:
password-stores+=
###+Both+'store-passwords'+and+'store-auth-creds'+can+now+be
###+specified+in+the+'servers'+file+in+your+config+directory
###+and+are+documented+there.+Anything+specified+in+this+section
###+is+overridden+by+settings+specified+in+the+'servers'+file.
store-passwords+=+yes++++#+just+in+case
store-auth-creds+=+yes+++#+just+in+case|code-block|syntax|javascript|1317255|什么都没用。|1317256|维蒂|1317257|然后我看了详细的手册。所有的事情都是共赢的：，你不能做这个。在Unix系统上，默认情况下，在编译时禁用磁盘上明文密码的客户端存储。|BOLD|1317258|维奇|1317259|幸运的是，读取密码的部分仍然在客户机二进制文件中。因此，如果密码碰巧被存储，它就会正常工作。我正在运行SVN+1.13：|1317260|svn,+version+1.13.0+(r1867053)
+++compiled+Mar+24+2020,+12:33:36+on+x86_64-pc-linux-gnu|1317261|因此，我打开了刚刚在~/.subversion/auth/svn.simple目录中创建的文件(它可能包含多个文件，您可能需要检查它们才能找到您想要的域)，并找到以下内容：|1317262|K+15
svn:realmstring
V+37
<svn://home.sweet.home:3690>+Profekto
K+8
username
V+6
lserni
END|1317263|语法很简单："K“是键，后面是键的长度，"V”是值，后面是值的长度。|1317264|在文件的顶部，我手工添加了提供明文密码的八行：|1317265|K+8
passtype
V+6
simple
K+8
password
V+20
NotTheActualPassword|1317266|(Note：在最新的Ubuntu上，passtype默认是gpg-agent，所以我的密码被覆盖了。所以我必须将“K9Vgpg-agent”改为“K6V+simple")。|1317267|现在起作用了。|1317268|entityMap^0|0|0|0|0|1|1|1|2|B|8|K|8|2|1|0|1|1|0|0|0|2|O|0|0|0|0|M|7|0|0|5|1J|0|0|0|2E|A|T|0|0|0|Y|0|0|N|0|0|0|2E|0|0|7|0^^$0|@$1|2|3|4|5|6|7|27|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|28|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|29|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|2A|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|2B|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|2C|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|2D|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|2E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|2F|8|@$S|2G|T|2H|U|V]|$S|2I|T|2J|U|V]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|F|7|2M|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|2N|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2P|8|@]|9|@]|A|$]]|$1|15|3|16|5|F|7|2Q|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2R|8|@$S|2S|T|2T|U|V]]|9|@]|A|$]]|$1|19|3|1A|5|1B|7|2U|8|@]|9|@]|A|$1C|1D]]|$1|1E|3|1F|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2W|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2X|8|@$S|2Y|T|2Z|U|1K]]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|30|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|31|8|@$S|32|T|33|U|1K]]|9|@]|A|$]]|$1|1P|3|1Q|5|1B|7|34|8|@]|9|@]|A|$1C|1D]]|$1|1R|3|1S|5|6|7|35|8|@$S|36|T|37|U|1K]|$S|38|T|39|U|V]]|9|@]|A|$]]|$1|1T|3|1U|5|1B|7|3A|8|@]|9|@]|A|$1C|1D]]|$1|1V|3|1W|5|6|7|3B|8|@$S|3C|T|3D|U|1K]]|9|@]|A|$]]|$1|1X|3|1Y|5|6|7|3E|8|@$S|3F|T|3G|U|1K]]|9|@]|A|$]]|$1|1Z|3|20|5|1B|7|3H|8|@]|9|@]|A|$1C|1D]]|$1|21|3|22|5|6|7|3I|8|@$S|3J|T|3K|U|1K]]|9|@]|A|$]]|$1|23|3|24|5|6|7|3L|8|@$S|3M|T|3N|U|1K]]|9|@]|A|$]]|$1|25|3|-4|5|6|7|3O|8|@]|9|@]|A|$]]]|26|$]]

<h1>Veni</h1>
I believe I tried everything:
<ul>
<li>checked the server configuration</li>
<li>checked the ~/.subversion permissions, all 600</li>
<li>checked the ~/.subversion/config file
<ul>
<li>store-plaintext-passwords = yes</li>
<li>store-passwords = yes</li>
<li>store-auth-creds = yes
<ul>
<li>did the above both in the <code>[global]</code> and <code>[groups]</code> section with my username</li>
</ul>
</li>
</ul>
</li>
<li>checked the ~/.subversion/servers file
<ul>
<li>same as above</li>
</ul>
</li>
</ul>
For all configuration files, I verified all sections, and also entered one wrong parameter and verified that the svn client stopped working (so, the config file was being read).
<ul>
<li>removed and re-created the ~/.subversion/auth directory</li>
</ul>
Checked that the client configuration in <code>$HOME/.subversion/config</code> disabled password stores:
<pre><code>[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.
# password-stores = gpg-agent,gnome-keyring,kwallet
### To disable all password stores, use an empty list:
password-stores =
### Both 'store-passwords' and 'store-auth-creds' can now be
### specified in the 'servers' file in your config directory
### and are documented there. Anything specified in this section
### is overridden by settings specified in the 'servers' file.
store-passwords = yes # just in case
store-auth-creds = yes # just in case
</code></pre>
Nothing worked.
<h1>Vidi</h1>
Then I read the fine manuals. Everything was copacetic: you are not expected to be able to do this. &quot;On Unix systems, client-side storage of passwords in plaintext on disk is disabled by default at compile-time&quot;.
<h1>Vici</h1>
Fortunately, the part that reads the passwords is still there in the client binary. So, if the password happened to be stored, it would work. I am running SVN 1.13:
<pre><code>svn, version 1.13.0 (r1867053)
 compiled Mar 24 2020, 12:33:36 on x86_64-pc-linux-gnu
</code></pre>
So I opened the file just created in the <code>~/.subversion/auth/svn.simple</code> directory (it may contain more than one file, you might need to inspect them to find the one with the realm you want) and found this content:
<pre><code>K 15
svn:realmstring
V 37
&lt;svn://home.sweet.home:3690&gt; Profekto
K 8
username
V 6
lserni
END
</code></pre>
The syntax is straightforward: &quot;K&quot; is the key followed by the length of the key, &quot;V&quot; is the value followed by the length of the value.
At the top of the file, I added by hand the eight lines that supply the plaintext password:
<pre><code>K 8
passtype
V 6
simple
K 8
password
V 20
NotTheActualPassword
</code></pre>
(Note: on the latest Ubuntu, passtype is by default gpg-agent, and so my password gets overwritten. So I have to change &quot;K 9 V gpg-agent&quot; to &quot;K 6 V simple&quot;).
and now it works.

blocks|key|24776|text|能够在macOS，vscode中解决这个问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|24777|svn版本1.14.1|24778|更改$HOME/..subversion/server：|24779|[global]
store-passwords+=+yes|code-block|syntax|javascript|24780|更改$HOME/..subversion/config包含：|24781|[auth]
password-stores+=+keychain|24782|Goto+~/.subversion/auth/svn.simple查找并删除包含我的svn站点的配置文件。|offset|length|style|CODE|24783|打开密钥链访问工具，删除相关的键。|24784|转到我的项目文件夹，运行svn+up+--username+xxxx+--password+xxxx重新打开VSCode。会没事的。|24785|entityMap^0|0|0|0|0|0|0|5|T|0|0|C|12|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|16|8|@$Q|17|R|18|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1A|8|@$Q|1B|R|1C|S|T]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

Was able to resolve this in macOS,vscode,
svn version 1.14.1
Change $HOME/.subversion/servers:
<pre><code>[global]
store-passwords = yes
</code></pre>
Change $HOME/.subversion/config contains:
<pre><code>[auth]
password-stores = keychain
</code></pre>
Goto <code>~/.subversion/auth/svn.simple</code>
Find and delete the config file which contains my svn site.
Open the Keychain Access Tool remove the related keys.
Goto my project folder, run <code>svn up --username xxxx --password xxxx</code>
Reopen VSCode. it will be OK.

blocks|key|24805|text|对于(WSL)用户，首先打开gpg-agent：gpg-agent+--daemon。下次运行svn+update时，它会像往常一样提示您输入密码，但是下一次运行svn+update时，您将收到来自gpg-agent的另一个密码提示。在这里输入您的密码以保存它。如果遇到任何问题，请删除~/.subversion目录重置subversion设置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|24806|entityMap^0|O|I|1B|A|29|A|3Z|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

For Windows Subsystem for Linux (WSL) users, first turn on the gpg-agent: <code>gpg-agent --daemon</code>. The next time you run an <code>svn update</code>, it will prompt you for the password like normal, but the next time you run <code>svn update</code> you will receive a different password prompt from gpg-agent. Enter your password here to save it. If you run into any issues, reset subversion settings by deleting your <code>~/.subversion</code> directory.

blocks|key|1317285|text|Alupotha的解决方案对我有用。我还编辑了~/..subversion/config，并为密码存储只设置了一个密钥存储工具。我删除了所有其他工具，使用了gnome-钥匙链。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1317286|密码-存储=gnome-密钥链|1317287|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Alupotha solution worked for me.
I also edited ~/.subversion/config and for password-stores set only one key storage tool. I removed all other tools and used gnome-keychain.
password-stores = gnome-keychain

I did everything the book says, i.e. removed the authentication files from .subversion/auth, and explicitly set the relevant configuration parameters to 'yes' even though this is a default, and yet the shell SVN commands ask for a password each time. The repository is on cvsdude.com, and the client is Linux. I also use the Subclipse plugin that caches the password OK.

I vaguely remember that when I started working with it, the command asked interactively if I wanted to save clear password, and I said no. Can this choice be stored somewhere and take precedence over the configuration?

Can't make SVN store passwords, even though the configuration is set to allow it

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我做了这本书说的所有事情，即从. .subversion/auth中删除身份验证文件，并且显式地将相关的配置参数设置为'yes'，尽管这是默认的，但是shell SVN命令每次都会请求一个密码。存储库在cvsdude.com上，客户端是Linux。我还使用Subclipse来缓存密码OK。我隐约记得，当我开始使用它时，...

问无法使SVN存储密码，即使配置设置为允许它
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使SVN存储密码，即使配置设置为允许它EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使SVN存储密码，即使配置设置为允许它
EN