Correct me if I am wrong Nathan, but there is no option that allows plaintext passwords on Linux. https://subversion.apache.org/docs/release-notes/1.14.html#plaintext-passwords-disabled
I thought that was a change in trunk to put that back as an option for 1.15? https://svn.apache.org/repos/asf/subversion/trunk/CHANGES Mark On Fri, Dec 1, 2023 at 12:55 AM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Thu, Nov 30, 2023 at 6:43 PM Bo Berglund <bo.bergl...@gmail.com> wrote: > > > > When I installed subversion on a Raspberry Pi4B and checked the installed > > version afterwards it printed this: > > > > $ svn --version > > svn, version 1.14.2 (r1899510) > > compiled Nov 12 2022, 20:30:30 on arm-unknown-linux-gnueabihf > > > > Copyright (C) 2022 The Apache Software Foundation. > > This software consists of contributions made by many people; > > see the NOTICE file for more information. > > Subversion is open source software, see http://subversion.apache.org/ > > > > < cut > > > > > The following authentication credential caches are available: > > > > * Plaintext cache in /home/bosse/.subversion > > * Gnome Keyring > > * GPG-Agent > > * KWallet (KDE) > > > > I have had a lot of problems with password caching for a number of years > > since I > > am working on these devices mainly on the command line via ssh and when I > > issue > > a svn command against a server on our LAN what happens is that svn pops up a > > password entry dialog on the (invisible) **GUI screen**! > > And the operation started on the command line fails... > > > > It was not always so but some svn update changed the way svn operates.... > > > > Now I see the banner above where it looks like it is again available: > > > > * Plaintext cache in /home/bosse/.subversion > > > > The problem is that in the config file there is no example of the syntax for > > enabling this.... > > > > So my question here is: > > How do I enable the plaintext cache in svn client version 1.14.2 on a > > Raspberry > > Pi4B running Pi-OS? > > > > > > -- > > Bo Berglund > > Developer in Sweden > > > In the user's home directory, there should be a subdirectory called > .subversion which contains a file called config. In that file, there > is a section called [auth] which contains a setting called > "password-stores". It might be commented, or it might say something > like "password-stores = gpg-agent,gnome-keyring,kwallet". This setting > determines the order in which the different password stores > (credential caches) are used. You could set this to "password-stores = > plaintext". Make sure you don't have "store-passwords = no" or > "store-plaintext-passwords = no". I think this will solve the issue -- > though note that if the password has not been saved to the plaintext > cache yet, the SVN client should prompt for it once, and then prompt > whether you accept the risk to save it in the plaintext cache. This > should take place on the command line, so I think you won't have the > issue with the inaccessible GUI dialog box on the remote machine. Once > saved, it shouldn't prompt for it anymore. > > Note: In addition to the user's ~/.subversion/config file I mentioned > above, there is also a systemwide /etc/subversion/config. If changes > in the user-level file don't appear to work, check the systemwide one > as well. > > Hope this helps, > Nathan
