On Sun, 20 Dec 2020 00:29:40 -0500, Nathan Hartman
<hartman.nathan_at_gmail.com> wrote:
>On Fri, Aug 14, 2020 at 7:35 AM Bo Berglund <bo.berglund_at_gmail.com> wrote:
>> How can I configure (?) svn such that it caches the password in the
>> same way as it has done on all of my other RPi units before.
>>
>> I need to be able to work on this device BOTH via SSH login using
>> PuTTY and inside the GUI when connecting via VNC.
>
>I don't think you want to enable plaintext password storage. Also I
>don't think that's part of the problem here.
You are correct, I don't care how the password is stored just that the
login should not move to a *different and invisible window* than the
one I am working in when I want to commit something!
Especially frustrating when I use an SSH terminal like PuTTY.
>The first thing you should do is run "svn --version" on the machine in
>question and look for the list of available authentication credential
>caches toward the end. On my Debian box, that looks like this:
>
>[[[
>The following authentication credential caches are available:
>
>* Gnome Keyring
>* GPG-Agent
>* KWallet (KDE)
>]]]
>
This is what I get:
$ svn --version
svn, version 1.10.4 (r1850624)
compiled Jul 28 2019, 02:44:06 on arm-unknown-linux-gnueabihf
Copyright (C) 2019 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/
The following repository access (RA) modules are available:
* ra_svn : Module for accessing a repository using the svn network
protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol
using serf.
- using serf 1.3.9 (compiled with 1.3.9)
- handles 'http' scheme
- handles 'https' scheme
The following authentication credential caches are available:
* Plaintext cache in /home/pi/.subversion
* Gnome Keyring
* GPG-Agent
* KWallet (KDE)
>Those are much better than plaintext storage because the password
>caches are stored encrypted.
Fine, that is OK for me. I never open any password file anyway.
>If you don't have any credential caches listed, you'll need to either
>request from the package maintainer(s) to do something about it, or
>ensure you have the right dependencies installed and build the SVN
>client from sources.
Well, as you see they are there, but if they are non-GUI they seem not
to be used anyway.
>If you do get a list of credential caches that the SVN client
>recognizes, then you should pick one and ensure it is setup correctly.
How do I "pick one"?
Inside the ~/.subversion/config ot ~/.subversion/servers files????
And how to "setup"?
>For example, if your SVN client supports gnome-keyring and you want to
>use that, you'll need to ensure you have whatever required packages
>installed on the RPi and may need to do some configuration so that the
>keyring will be "unlocked" when you login via ssh (with PuTTY). That
>should make the stored passwords available automatically and (at least
>after the first time to initially enter the password) eliminate the
>(GUI) password prompt.
I do not know what any of these are, I just want the login dialog to
show in the text based SSH window where I issued the svn command....
Which one of these will make the GUI dialog go away? The names
indicate that they are related to Linux GUI desktops, which I don't
use..
Subversion was so easy to use on the command line but now it is a
PITA...
I just want to *use* svn.
--
Bo Berglund
Developer in Sweden
Received on 2020-12-20 09:06:16 CET