Thanks for pointing that out. So, just for my understanding: Are you
happy - design-wise - with the fact that if the keyring is not
unlocked a user is asked for the GPG key even it is already available
in the keyring?
This is pretty far outside our responsibility. The better question is
what
Am 02.01.20 um 17:36 schrieb Patrick Brunschwig:
> Robert J. Hansen wrote on 02.01.2020 16:26:
>>> Using Enigmail for some time now - thanks for your work!
>> Patrick deserves all the credit; the rest of us just try to help him
>> with the load of questions. :) Which is hard, given that he
Hello.
I had a similar issue with ssh passphrase caching when I switched from
using plain GNOME to the i3 window manager in Ubuntu. The problem was
that the GNOME Keyring Daemon is automatically started when GNOME starts
but that does not happen when i3 starts.
The solution, in my case, was to
Robert J. Hansen wrote on 02.01.2020 16:26:
>> Using Enigmail for some time now - thanks for your work!
>
> Patrick deserves all the credit; the rest of us just try to help him
> with the load of questions. :) Which is hard, given that he usually
> beats us to answering them!
>
>> As I
Using Enigmail for some time now - thanks for your work!
Patrick deserves all the credit; the rest of us just try to help him
with the load of questions. :) Which is hard, given that he usually
beats us to answering them!
As I understand, the GPG key for a specific email address is saved
Hello,
Using Enigmail for some time now - thanks for your work!
As I understand, the GPG key for a specific email address is saved inside the
keyring, in my case the GNOME keyring. To decrypt an encrypted email Enigmail
needs to have access to that keyring. Which means, the GNOME keyring needs
