On Sat, Aug 20, 2022 at 8:40 AM Olaf van der Spek <olafvds...@gmail.com> wrote: > > Op za 20 aug. 2022 om 12:39 schreef Daniel Sahlberg > <daniel.l.sahlb...@gmail.com>: > > > > Den lör 20 aug. 2022 kl 12:20 skrev Olaf van der Spek > > <olafvds...@gmail.com>: > > Check the available authentication credential caches: > > [[[ > > $ svn --version > > [...] > > The following authentication credential caches are available: > > > > * Plaintext cache in /home/daniel/.subversion > > * Gnome Keyring > > * GPG-Agent > > * KWallet (KDE) > > ]]] > > > > If you are missing the Plaintext cache then your distribution compiled > > Subversion without the support for storing passwords in the plaintext > > cache. (The compile-time option changed in Subversion 1.12 to disable the > > plaintext cache unless explicitly enabled). > > Right, thanks! > Does it really have to be this hard to store passwords? ;) > > I'm running a local svnserve, is there a better way to handle this?
Easy to use and access conflicts with secure from others, especially the root user. Have you considered using 'svn+ssh' based access, with ssh-agent setups? I used those especially with tools like Jenkins, so I could demand a pass-phrase when starting sensitive tasks.
