W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Clipboard API: remove dangerous formats from mandatory data types

From: Paul Libbrecht <paul@hoplahup.net>
Date: Tue, 09 Jun 2015 23:35:16 +0200
Message-ID: <55775C14.5040605@hoplahup.net>
To: Wez <wez@google.com>
CC: Daniel Cheng <dcheng@google.com>, Olli Pettay <olli@pettay.fi>, public-webapps <public-webapps@w3.org>
But then it goes even further with just about any type for which broken
parsers exists.
HTML is certainly a good example since its very diversely implemented.

An application that lives on a desktop and fails on some images would be
exposing its user if the user downloads a content and opens it with the
application.  Is the difference that the browser warns the user that the
picture has been downloaded? I've never seen a warning about a
downloaded picture.


On 9/06/15 23:25, Wez wrote:
> IIUC that approach won't help, because the problem here is not
> necessarily invalid/malformed data, but even valid data that some
> decoders fail to handle gracefully.
> On 9 June 2015 at 14:13, Paul Libbrecht <paul@hoplahup.net
> <mailto:paul@hoplahup.net>> wrote:
>     On 9/06/15 23:08, Daniel Cheng wrote:
>>         So the solution is to require that browsers that make known
>>         media-types in the clipboard actually parse it for its value?
>>         That sounds doable (and probably even useful: e.g. put other
>>         picture flavours in case of a pictures).
>>     I don't think I understand what this means.
>     Since the browser is what would act on behalf of JS when putting a
>     given data into the clipboard, it could check that this data is
>     well formed and maybe matches the patterns of known exploits.
>     paul

Received on Tuesday, 9 June 2015 21:35:51 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC