Bug#886126: mini-buildd: using alt.files as keyring backend is highly impractical

2018-01-02 Thread Stephan Sürken
Hi "ydirson",

On Tue, 2018-01-02 at 16:09 +0100, ydir...@free.fr wrote:
> Package: mini-buildd
> Version: 1.0.29
> 
> With no external keyring software installed, python-keyring defaults
> to alt.files, and the impact
> on scripting (eg. launching auto-setup for a test) is quite high:
> 
> * have to enter keyring password for each keyring access
> * a single error in one of those numerous prompts stops the whole
> process:

to change the default of python-keyring, add a file
'~/.local/share/python_keyring/keyringrc.cfg':

--
[backend]
default-keyring=keyrings.alt.file.PlaintextKeyring
--

This will (not be very secure) but ok for a auto-setup test drive. I
definitely would not change the default keyring backend of python-
keyring in mini-buildd code.

auto-setup is currently a bash script, repeatedly calling m-b-t
(python), which adds to the "problem". For the future, auto-setup will
be integrated into mini-buildd itself; for now, the only option is to
properly configure python-keyring for the calling user...

Hth!

S



Bug#886126: mini-buildd: using alt.files as keyring backend is highly impractical

2018-01-02 Thread ydirson
Package: mini-buildd
Version: 1.0.29

With no external keyring software installed, python-keyring defaults to 
alt.files, and the impact
on scripting (eg. launching auto-setup for a test) is quite high:

* have to enter keyring password for each keyring access
* a single error in one of those numerous prompts stops the whole process:

Please enter password for encrypted keyring:
E: admin@yantop:8066: Login failed: admin@redacted:8066: Incorrect Password
root #