Or possibily forking Enigmail to build it as a subextension.
On Wed, Feb 19, 2014 at 1:43 PM, Robert J. Hansen <[email protected]>wrote: > What do you think about that? Would it be too complicated a workflow? >> I personally would welcome a feature like this inside of Enigmail. >> But as mentioned, if you believe this should be added to GnuPG itself >> instead, I'll ask the GnuPG people about their opinion. >> > > There's a serious bootstrapping problem here. > > Enigmail's mission statement: "We provide a convenient front-end to > GnuPG's OpenPGP functionality. No more and no less." > > GnuPG's mission statement: "We provide implementations of OpenPGP > (RFC4880) and S/MIME (RFC5721). No more and no less." > > I don't know enough about Namecoin to talk intelligently about it. > However, until Namecoin becomes a part of either RFC4880 or RFC5721, it is > unlikely to be supported within either GnuPG or Enigmail. > > The best way to proceed, I think, would be to set up a keyserver that > could interact with a Namecoin back-end and communicate over the existing > HKP protocol. If you can get people using Namecoin through a shim like > that, then over time you might be able to get people to use Namecoin > directly. > > > > _______________________________________________ > enigmail-users mailing list > [email protected] > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > -- Kelly John Rose Toronto, ON Phone: +1 647 638-4104 Twitter: @kjrose Skype: kjrose.pr Gtalk: [email protected] MSN: [email protected] Document contents are confidential between original recipients and sender.
_______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
