Den tors 13 juli 2023 kl 19:08 skrev David Aldrich < david.aldr...@emea.nec.com>:
> Hi Doug > > > > Thanks for your reply. > > > > > Gnome keyring is the normal answer, yes. Once setup it's pretty stable. > > > > The issue for us is that I believe Gnome keyring requires a GUI desktop. > We want something that works in a terminal ssh session (no desktop). Do you > know of a way around this? > > > > Would svn+ssh actually avoid password authentication in this scenario? > Unfortunately, it’s not easy to understand how to go about it. > svn+ssh can be made to work this way if you setup public key authentication. See for example https://www.ssh.com/academy/ssh/public-key-authentication The first step is probably to make sure you can access the server via SSH using your public/private key. Next you must make sure that your user has write access to the repository. It is possible to configure the server to only allow SVN access (no shell access) if that is desired. The Subversion book has a lot of useful information, for example: https://svnbook.red-bean.com/en/1.7/svn.serverconfig.choosing.html#svn.serverconfig.choosing.svn-ssh https://svnbook.red-bean.com/en/1.7/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth Of course, if you protect your private key with a passphrase, you will have to enter that passphrase every time you access the server, basically substituting one password for another. You can store your private key without a passphrase but it is up to you to decide if that is acceptable from a security perspective. If you allow storing the private key without a passphrase (=> basically letting anyone with enough authority on the computer to access the home directory also access the Subversion server) you could also consider storing the Subversion password in plain text. For more information, see the following FAQ item on our website: https://subversion.apache.org/faq.html#plaintext-passwords Kind regards, Daniel Sahlberg
