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

Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]

From: Arthur Barstow <Art.Barstow@nokia.com>
Date: Thu, 9 Apr 2009 09:56:12 -0400
Message-Id: <1D1FCD44-B8C4-49EB-9822-8A3333D1219B@nokia.com>
Cc: "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com>, Web Applications Working Group WG <public-webapps@w3.org>
To: Marcos Caceres <marcosc@opera.com>, "Priestley, Mark, VF-Group" <Mark.Priestley@vodafone.com>
On Apr 9, 2009, at 9:52 AM, ext Marcos Caceres wrote:

> On Thu, Apr 9, 2009 at 2:17 PM, Priestley, Mark, VF-Group
> <Mark.Priestley@vodafone.com> wrote:
>> Hi Art, All,
>>
>> If there is no use case for accessing this information (I was  
>> after why
>> you would want to access this information because I think just  
>> saying it
>> might be interesting to do so isn't justification enough), then I  
>> think
>> my original proposal holds - make the signature files unavailable  
>> to the
>> widget at runtime.
>>
>> For clarification I was not suggesting that an API should be added to
>> the DigSig spec but rather that some of the information could be  
>> exposed
>> via an API defined in the APIs and Events spec. But I don't think  
>> this
>> is necessary or worth the additional specification effort.
>
>
> FWIW, I agree with Mark.

Please propose text that will address your concerns.

-Thanks, Art Barstow
Received on Thursday, 9 April 2009 13:57:58 GMT

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