With Chrome's relatively new native-messaging-api system, it wouldn't be terribly hard to spawn off external processes to do gpg work. You just have to implement a JSON messaging api between an extension and platform-specific executable. On Jun 4, 2014 7:31 PM, "a k'wala" <akw...@gmail.com> wrote:
> On 06/04/2014 08:45 AM, Ciprian Dorin Craciun wrote: > > Personally I won't use any browser plugin that operates on cryptographic > material inside it's own process. Instead I would expect it to delegate > such operations to something similar to the GnuPG agent. > > I happened to come across one that uses an external gpg binary: > http://thinkst.com/tools/cr-gpg/. It's last release was an alpha in 2012. > > > aslamK > > PGP key <http://is.gd/aslampgpmit> fingerprint: 736C D83E 32DB A2FD 0208 > 9113 0FC8 BA7D FECF 84FB > > > _______________________________________________ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
