Re: [Enigmail] gpg-agent and gnome keyring

2014-08-17 Thread Jogi Hofmüller
Hi Patrick, all

Am 2014-08-14 17:15, schrieb Patrick Brunschwig:
 On 14.08.14 13:41, Jogi Hofmüller wrote:
 After a recent upgrade to enigmail 1.7 (Debian/testing) I got
 annoyed by the gnome hijacked gpg-agent message and disabled the
 gpg part of gnome keyring.  Now enigmail asks for my passphrase
 every time I read an encrypted mail and even twice when I send one,
 despite telling it that it should keep the passphrase in memory.
 
 Why? You should only get the message when you save the Enigmail
 prefrences.

I figured that I schould only get it then, but I kept getting it every
time I started Thunderbird/Icedove.  The wording is also a bit strange
because it suggests that something evil is going on (hijacked).  Guess
users that read it could get overly confused ...

 What's so bad about gnome keyring that all of a sudden enigmail
 doesn't want to work with it anymore?  It worked fine until 1.7
 appeared.  How are others handling this?
 
 The only problem is that Enigmail cannot configure gnome-keyring,
 i.e. when you change the passphrase caching settings, Enigmail cannot
 reconfigure gnome-keyring (which works in gpg-agent).

Uh, well, then I underline my opinion that the wording is too strong.

 Personally I would say that PGP is complicated enough and the new 
 behavior of enigmail doesn't really make things easier ...
 
 Why don't you set up gpg-agent or re-activate gnome-keyring for gpg?

I did set up gpg-agent now and will continue using it for a while.
Still, this is a big hurdle for users not used to editing config files.
 Gnome (and other environments too I guess) is doing a pretty good job
in making Linux usable for the masses.  Why should crypto hang behind
and make things overly complicated?

Anyhow, just my thoughts on this recent experience.

Regards,
-- 
j.hofmüller aka Thesix  -#!$@@@? http://thesix.mur.at/



signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] gpg-agent and gnome keyring

2014-08-17 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 17.08.14 11:37, Jogi Hofmüller wrote:

 Uh, well, then I underline my opinion that the wording is too
 strong.

If you are you referring to this message:

+The GNOME keyring manager hijacked the GnuPG agent.;
+GnuPG will not work proberly - please configure that 
+tool to not interfere with the GnuPG system!;

then this comes directly from the underlying gpg2. We cannot influence
the text. I also think, that the gnupg developpers did not deliberatly
choose such a strong wording.

 Personally I would say that PGP is complicated enough and the
 new behavior of enigmail doesn't really make things easier ...
 
 Why don't you set up gpg-agent or re-activate gnome-keyring for
 gpg?
 
 I did set up gpg-agent now and will continue using it for a while. 
 Still, this is a big hurdle for users not used to editing config
 files. Gnome (and other environments too I guess) is doing a pretty
 good job in making Linux usable for the masses.  Why should crypto
 hang behind and make things overly complicated?

I agree completely with don't make crypto overly complicated.

However, Enigmail relies completely on gnupg for the crypto stuff. If
gnupg decides to hate the gnome keyring behaviour regarding
gnupg-agent, then we are only the messenger of the gnupg status output.

If you want to discuss gnupg behaviour, the best place would be the
gnupg-users list (gnupg-us...@gnupg.org).

HTH

Ludwig

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJT8H2WAAoJEA52XAUJWdLj+VgH/jqKlmHyVVsVrKbAphWuBMQr
BxrFRkgIxl6e4k6GhScZLNOJToqzT/92vkSbqJjGtiUzGoLcBvs8hOvYkWuYb4Y7
3MTJxjwKJ8qct/5bxtETv+3DSdmiD7KF2YmWjoWQK3BP5Fzvx1ep/VIAThDvhG/3
YzUZIYp1w3lkTIG09vO6YufnXm2VzsEZLmHIoTN+0A6fdFYhpBdJyLijJfosw9OJ
Eftiy/u7Ir1Pqv1aJTgNsKzqXy78SlV0azdPYdUfaeBvQkm6IkeHTNT0H0wOYSZh
gf4rFSZscFQmq9JZNTqYTBYt2zOlCYG1ygzoX/FcCZK1o4b6OUN1vhZ4WsdJk+I=
=3XMu
-END PGP SIGNATURE-

___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


[Enigmail] gpg-agent and gnome keyring

2014-08-14 Thread Jogi Hofmüller
Dear all,

After a recent upgrade to enigmail 1.7 (Debian/testing) I got annoyed by
the gnome hijacked gpg-agent message and disabled the gpg part of
gnome keyring.  Now enigmail asks for my passphrase every time I read an
encrypted mail and even twice when I send one, despite telling it that
it should keep the passphrase in memory.

What's so bad about gnome keyring that all of a sudden enigmail doesn't
want to work with it anymore?  It worked fine until 1.7 appeared.  How
are others handling this?

Personally I would say that PGP is complicated enough and the new
behavior of enigmail doesn't really make things easier ...

Cheers,
-- 
j.hofmüller

mur.sat -- a space art projecthttp://sat.mur.at/



signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] gpg-agent and gnome keyring

2014-08-14 Thread Patrick Brunschwig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 14.08.14 13:41, Jogi Hofmüller wrote:
 Dear all,
 
 After a recent upgrade to enigmail 1.7 (Debian/testing) I got
 annoyed by the gnome hijacked gpg-agent message and disabled the
 gpg part of gnome keyring.  Now enigmail asks for my passphrase
 every time I read an encrypted mail and even twice when I send one,
 despite telling it that it should keep the passphrase in memory.

Why? You should only get the message when you save the Enigmail
prefrences.

 What's so bad about gnome keyring that all of a sudden enigmail
 doesn't want to work with it anymore?  It worked fine until 1.7
 appeared.  How are others handling this?

The only problem is that Enigmail cannot configure gnome-keyring,
i.e. when you change the passphrase caching settings, Enigmail cannot
reconfigure gnome-keyring (which works in gpg-agent).

 Personally I would say that PGP is complicated enough and the new 
 behavior of enigmail doesn't really make things easier ...

Why don't you set up gpg-agent or re-activate gnome-keyring for gpg?

- -Patrick
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQEVAwUBU+zSqsk25cDiHiw+AQgADQf/aHgaXzIyfW716riWCtDGzNNcJyq0b7Ud
TMUgYTMIQy7GTv2x5Ko9AgJw9X/V5AeAErlXOABVcJ2zOVPVkABRjW7FVPYECoFy
NXyKRgftNabsqSuqcoZFYakyP0WQ3s65BIx5cfBsLUrZGIlqNypL8hvS7eq2Gx8Y
YSziJZhsxa6qYyXgGF0Nk6RmHkbaXJSvj/Gc/xwHZywUAWVAG8mO8jLHFZjehF+z
ySUKXdcxZbor2pConAlPAfJQgGRJDTLtVwLy5MkW3rIBfjjxZ/KlJ2ifA8pShzXL
ICRVrLVC5zmElokv8aKIB7H3f/het/dOQBIMs4EzDG9t381LEpWO0w==
=uuRu
-END PGP SIGNATURE-

___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net