W3C home > Mailing lists > Public > public-browserext@w3.org > February 2017

Native Messaging. Re: Minutes of the 2017-02-02 teleconf

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Mon, 6 Feb 2017 06:49:10 +0100
To: Florian Rivoal <florian@rivoal.net>, public-browserext@w3.org
Message-ID: <413acb37-676d-6fc5-1a5f-c2cf02b18d92@gmail.com>
On 2017-02-02 07:54, Florian Rivoal wrote:
> Minutes of the 2017-02-02 teleconf are available here:
> http://browserext.github.io/minutes/2017-02-02.html

Thanx Florian,

Since my interest is limited to Native Messaging which (AFAICT), in the current incarnation
doesn't address iOS and Android (i.e. missing 97% of the mobile device market), I will drop
off until I see this topic being dealt with by a larger group of interested parties.

That Google who is the originator of Native Messaging isn't a participant also makes me
questioning the value of *this* part of the work.  From what I understood, neither Apple
nor Google have yet been approached which seems like a huge waste of resources and time.

Using "in-browser" extensions and Native Messaging in for example Android makes no sense
since Android has a WebView component which is way more powerful than a browser which is
why I insist that Native Messaging and in-browser extensions should be *separated*.

As a "workaround" [1] the scheme implemented by Mozilla and Google is just fine.  However,
as a "standard" it doesn't meet reasonable deployment and security expectations.

Some kind of manual application vetting is simply put necessary, at least on systems that
do not support application sand-boxing and declared usage of privileges.

I find it slightly odd that Mozilla and Microsoft spend time on developing a *single-purpose,
Native Messaging scheme* in the Web Payment WG when I have shown [2] that a much simpler universal
solution can do the same job and still address thousands of entirely different applications!


1] https://www.cnet.com/news/google-paves-over-hole-left-by-chrome-plug-in-ban/

2] https://test.webpki.org/webpay-merchant

> If you wish to correct the minutes, please submit a pull request on the CG's github repository: https://github.com/browserext/browserext.github.io
> Resolutions taken during teleconfs or face to face meeting are tentative, and have a github issue associated with them. You can find these issues by following the links from the minutes. Comments in these issues are welcome. Resolutions will be considered to be the consensus of the Community Group unless dissenting opinions are expressed within 10 days.
> Work on based on tentative resolutions may begin before the 10 days are elapsed, but any such work will be rescinded if the eventual consensus disagrees with the tentative resolution.
> Best regards,
> Florian Rivoal
> Co-chair
Received on Monday, 6 February 2017 05:49:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:02 UTC