Re: Why is svn not saving my password in Pi-OS?

On Tue, 29 Dec 2020 00:47:32 -0500, Nathan Hartman
<hartman.nathan_at_gmail.com> wrote:

>On Mon, Dec 28, 2020 at 3:16 PM Bo Berglund <bo.berglund_at_gmail.com> wrote:
>
>> On Sun, 20 Dec 2020 11:59:11 +0100, Bo Berglund
>> >5) Then the commit worked!
>> >
>> >So it seems like the svn config file must be modified and then it
>> >starts working again.
>> >
>>
>> Except now it has reverted to popping up the GUI login dialog when I
>> am checking in via a PuTTY session.
>> In PuTTY it just sits there doing nothing, if I then open the VNC
>> window into the RPi then I see the login dialog there. :(
>>
>> How should the setting in subversions config file look like?
>> Right now it is as follows (uncommented the existing line)
>>
>> password-stores = gpg-agent,gnome-keyring,kwallet
>>
>> Should something be taken out or something else added to make it stop
>> this behaviour and always demand login on the terminal that issues the
>> svn operation?
>>
>> It seems so strange that svn would use a completely different window
>> to get the credentials from than the one where svn itself runs.
>
>
>Hi Bo,
>
>The order of the 'password-stores' setting is significant. Based on what
>you wrote the last time, that means gpg-agent is tried first, followed by
>gnome-keyring, followed by kwallet.
>
>It sounds to me like one of these is putting up the GUI password dialog
>that you want to avoid.
>
>It is probably enough to choose just one of these password caches and set
>it up properly, to ensure that you'll only use that one.
>
>Here is some information about getting gpg-agent and gnome-keyring to
>prompt for password in the console, not in the GUI. I'm also including a
>link about KWallet, though that one doesn't look as encouraging to me as
>the other two... you might want to remove that one from password-stores
>(and you might want to remove one of the other two, leaving just one).
>
>
>gpg-agent
>=========
>
>To get gpg-agent to prompt for password in the console, see the following
>two questions and answers:
>
>https://superuser.com/questions/520980/how-to-force-gpg-to-use-console-mode-pinentry-to-prompt-for-passwords
>
>https://stackoverflow.com/questions/17769831/how-to-make-gpg-prompt-for-passphrase-on-cli
>
>Namely, these explain how to setup gpg-agent to use a console-based
>pinentry program, either pinentry-tty or pinentry-curses.
>
>gnome-keyring
>=============
>
>Regarding gnome-keyring, see this question:
>
>https://superuser.com/questions/141036/use-of-gnome-keyring-daemon-without-x
>
>and in particular see Stephen Gray's answer (currently the 2nd from the
>top). It includes a link to "source material" which is a WANdisco article
>but that link is broken; the updated link is:
>
>https://community.wandisco.com/s/article/How-to-set-up-encrypted-svn-password-storage-using-gnome-keyring-in-an-ssh-session
>
>In particular, see the part about setting up a dbus session to interface
>with the GNOME Keyring; I think that's the key step that allows it to work
>without X (without a GUI).
>
>kwallet
>=======
>
>Less encouraging than the other two, but:
>
>https://bbs.archlinux.org/viewtopic.php?id=253391
>
>Hope one of these helps...

Well I had a look and it does not seem like there is much of this on
the RPi4...
 .gnupg/ is empty including its subdir private-keys-v1.d/
 /etc/pam.d/login has a lot of settings but the referenced so files do
not exist (on path at least)

I read your links and I did not understand a lot of it.

But in the "Gray's answer" part I could follow 1.1 and 1.2 (edit the
config file).

But for item 2 I drew a blank...
The Collabnet keyring_tool does not exist on my system:
$ which keyring_tool
(no output)

So the instruction to "Create a keyring for your password."
by the operations below cannot be executed:

keyring_tool --create=svn
or
keyring_tool --setdef=svn

And apt is no help either:

$ sudo apt install keyring_tool
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package keyring_tool

Seems such a pity that a tool like Subversion can be so broken by some
"upgrade" that it becomes unusable...

-- 
Bo Berglund
Developer in Sweden