- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Wed, 4 May 2016 08:44:22 +0200
- To: Andrew Swan <aswan@mozilla.com>, Florian Rivoal <florian@rivoal.net>
- Cc: Mike Pietraszak <mikepie@microsoft.com>, "public-browserext@w3.org" <public-browserext@w3.org>
Hi Guys, This is another and implemented proposal for Native Messaging which you can test if you want. It is based on the idea that a native extension is a standard executable augmented with meta-data indicating for the Browser/OS platform that it is intended (maybe even certified) for being callable from the "open Web": https://github.com/cyberphone/web2native-bridge That is, IMO, native messaging should be separated from "in-browser" extensions. The public demo application was created for verifying the concept: https://test.webpki.org/webpay-merchant A security review of Google's take on this matter: https://lists.w3.org/Archives/Public/public-webappsec/2015Oct/0071.html Just to make things a bit more more fuzzy, Google is working on an entirely different solution for Android. Anders Rundgren
Received on Wednesday, 4 May 2016 06:45:08 UTC