> In particular I hope, that Mozilla will not follow your example and > won’t entice users to proprietary isolated keyserver [0]
The Hagrid codebase is not proprietary. It's been fully open sourced and is developed by the same people behind the open-source SequoiaPGP. I understand you don't like a single point of failure. However, the SKS system is simply no longer sustainable. Point-blank, it is dead as far as Enigmail is considered. Imagine you're using Enigmail with an SKS-configured keyserver. You have a question about Enigmail, so you decide to email one of Enigmail's user-outreach guys -- namely, me. So you find my email address, pull down my certificate from the keyserver, and now GnuPG is *completely* wedged. Yes, you can say "but users shouldn't even be suffering that any more, GnuPG fixed the quadratic-time key parsing bug". But there's a big difference between saying what users *should* do and recognizing what users *actually do*, which is (a) not update GnuPG, and (b) blame Enigmail for anything which goes wrong, and (c) yell at me. So unless you're willing to field all the hate mail from users, well, this complaint's going in the circular file. :)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
