Tails

#3 Updated by sajolida 2015-05-18 11:59:27

I’ve never really used it myself and should train myself to use Seahorse more systematically to see if it’s good enough.

I don’t think this ticket is a blocking Feature #5663 and I think it’s low priority (until having this feature of Enigmail is a problem, for example for frontdesk).

#4 Updated by intrigeri 2015-05-18 15:05:30

> I don’t think this ticket is a blocking Feature #5663

Well, if we don’t block Feature #5663 on this ticket at all, then it implicitly means that we consider it’s fine to ship Enigmail’s key management GUI, at least for a while… which is IMO exactly the discussion we should have here.

> and I think it’s low priority (until having this feature of Enigmail is a problem, for example for frontdesk).

IMO it’s always a UX problem to ship two different pieces of software that basically do the same thing, and that’s why we generally try hard to avoid that. I’m sure we already agree on that general policy anyway :)

Bonus technical info: in the specific case at hand, if we enable Enigmail’s key management GUI, then we’ll have to make sure it is configured in a way that’s similar to Seahorse (or better if we can). E.g. keyservers (IIRC Enigmail basically overrides the settings configured in gpg.conf) and default key length come to mind first. This work might take as much time as disabling that key management feature, to be checked.

Also, the blueprint currently says that “Enigmail has a much easier guide for generating a key and setting up GnuPG. The guide starts pretty much automatically and is very informative.” (I guess it’s compared to Claws Mail?) This might be a good reason to include this feature despite the aforementioned drawbacks.

#6 Updated by kytv 2015-09-28 05:46:06

One data point: in all the time that I’ve used Enigmail (and other methods) to refresh/retrieve keys over Tor I’ve never had a crash. Seahorse on the other hand…

Sometimes when syncing keys the Seahorse window will just disappear with a segfault (Bug #9970).

After ~9 months of working on the test suite and seeing these crashes I’m not a fan of Seahorse. :/

#7 Updated by intrigeri 2015-10-03 04:14:35

> Sometimes when syncing keys the Seahorse window will just disappear with a segfault (Bug #9970).

It might be that this has been fixed in Jessie, and we won’t know before I’ve fixed Bug #9792.

#9 Updated by intrigeri 2015-12-19 10:18:13

kytv, this is an important change if we decide to do it, that should IMO go into 2.0~rc1, and might take some development time. With all this in mind, status / ETA?

#14 Updated by kytv 2015-12-22 13:08:43

intrigeri wrote:

> I’d prefer if you discussed this with your team-mates, unless it’s about something that I know something you folks don’t :)

All good. :)

Email sent to the ML.

#15 Updated by Anonymous 2015-12-30 04:47:09

I’d rather not disable this feature. Sometimes, when there are missing keys for any recipient, Icedove/Enigmail will show a window telling you this. This window has buttons to access the key management feature. It seems weird to hide this if a user wants to access this again, at a later point in time.

I also agree with kytv’s remark on the ML that people who used Enigmail with Windows or Mac OS before might feel lost if they do not have access here.

I am aware that this adds a lot of documentation work, but I feel that that’s not a valid reason to disable this.