W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: DAP and security (was: Rename "File API" to "FileReader API"?)

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 19 Nov 2009 10:52:01 +0100
To: robert@ocallahan.org
Cc: Marcin Hanclik <Marcin.Hanclik@access-company.com>, Jonas Sicking <jonas@sicking.cc>, David Rogers <david.rogers@omtp.org>, Maciej Stachowiak <mjs@apple.com>, Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>, public-webapps WG <public-webapps@w3.org>
Message-ID: <1258624321.12107.1872.camel@localhost>
Le jeudi 19 novembre 2009 à 22:39 +1300, Robert O'Callahan a écrit :
>         The abstraction of the security concerns within a policy may
>         allow delegation of the security to some third parties.
> 
> There are usually no third parties to delegate to.

That’s true to a certain extent, but a reason for that might well be
that the Web platform hasn’t left enough room for third parties in that
realm.

One could very well imagine that by allowing a certain level of
abstraction in security concerns, we would allow businesses to offer
guarantees against data-loss or data-thief if the user install a
third-party extension that would check Web sites based on a number of
their security aspects.

I’m pretty sure I don’t like all the implications of such a system, and
I’m generally rather in the skeptic side when it comes to the use of a
full-blown policy framework for the Web; but I don’t think it’s fair to
conclude that it is not useful simply based on the fact that it hasn’t
been put to use yet, esp. if it’s currently difficult or impossible to
put it to use.

Dom
Received on Thursday, 19 November 2009 09:52:21 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT