[pkg-gnupg-maint] Bug#919856: Bug#919856: gpg-agent: agent refuses operation again

[NIIBE Yutaka]

Hello,

I have been chasing the bug in gpg-agent, pinentry, libscret, and
gnome-keyring.  But, I forgot to consider about a simple problem of
data.  Sorry, I should have considered that, in the first place.

The exact cause would be there is an empty cache remained in
gnome-keyring-daemon.  In my case, it is under:

    ~/.local/share/keyrings/

I don't know the reason why it was created, but it makes sence to
remove the entry... to see if it's working well again. 

Attached is a Python script (I name it test_clear.py) to clear the cache
entry (your specific keygrip is hard-coded).  You need python3-gi
package (and ignoring warning about version specification).


Here is an example session of mine.
==========================
$ python3 test_clear.py 
test_clear.py:1: PyGIWarning: Secret was imported without specifying a version first. Use gi.require_version('Secret', '1') before import to ensure that the right version gets loaded.
  from gi.repository import Secret
False
==========================

In your case, it prints out "True".  After clearing the entry, it should
work again if this is the case.



While gpg-agent supports clearing cache entry for normal and user
usages (by CLEAR_PASSPHRASE command), currently, it doesn't support 
SSH usage.  I just created a task to request this feature.

    https://dev.gnupg.org/T4340

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_clear.py
Type: text/x-python
Size: 463 bytes
Desc: a python script to clear the cache entry in Secret Service
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20190125/17b8c4e2/attachment.py>