W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2009

Re: ACTION-38: "Should issue recommendation on the granularity of the security system" + proposal for a "Secure Credential API"

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Wed, 16 Dec 2009 09:16:19 -0500
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>, "'public-device-apis@w3.org'" <public-device-apis@w3.org>
Message-Id: <49F2B0D9-A775-4FC4-8466-7719720552BA@nokia.com>
To: "ext Nilsson, Claes1" <Claes1.Nilsson@sonyericsson.com>
Claes

Thanks for the proposals.

Secure Cred Manager should be deferred to future work.

I have a few questions regarding the "File Granularity Access Policy",  
to help me understand it:

Is it correct to say that the essence of the  "file granularity access  
policy" proposal is to determine an application id from either the X. 
509 cert or signed widget config, and then pass this application id in  
all API calls?

What value does this add? An example might help me understand the  
benefit.

Who manages application ids, is there a registry? What prevents any  
widget from including any application id it wants?

What happens in a web case (not widget), where there is no such Id?

What if X.509 certs are not used in certain cases, where does the  
application id come from?

Is there an "application id" lifecycle?

regards, Frederick

Frederick Hirsch
Nokia



On Dec 15, 2009, at 5:15 AM, ext Nilsson, Claes1 wrote:

> Hi,
>
> I attach two proposals:
>
> 1.       “File granularity access policy”. This is response to my  
> action 38. The proposal is based on “Policy Based Device Access  
> Security” (Steve Lewontin/Nokia  http://lists.w3.org/Archives/Public/public-device-apis/2009Nov/att-0012/SecurityPolicy_09.pdf) 
>  that Steve presented at the Santa Clara meeting. My proposal adds a  
> finer granularity to restrict access to APIs based on application  
> identity.
> 2.       “Secure Cred Manager”. This proposal is based on 1 above  
> and is an API for retrieving securely stored data, “credentials”, in  
> the device. A major use case for this API is Social Networking  
> Services web application application login to the service. I have a  
> humble view on this and understand the security issues with  
> JavaScript. However, by referencing existing security mechanisms  
> such as Digital signing, TLS/SSL and WARP, I believe that such an  
> API is possible. Furthermore, I realize that it is not possible to  
> include this API in the phase 1 delivery from DAP but I want to have  
> it in the list of “Future Work”.
>
> Best regards
>   Claes
> Claes Nilsson M.Sc.E.E
> Senior Staff Engineer
> CTO - R&T Europe - UI/App/Web
>
> Sony Ericsson Mobile Communications
>  Phone:  +46 10 80 15178
> Mobile: +46 705 56 68 78
> Switchboard: +46 10 80 00000
> E-Mail: mailto:claes1.nilsson@sonyericsson.com
> Visiting Address; Nya Vattentornet
> SE-221 88 LUND,
> Sweden
> Disclaimer:
> The information in this e-mail is confidential and may be legally  
> privileged. It is intended solely for the named recipient(s) and  
> access to this e-mail by anyone else is unauthorized. The views are  
> those of the sender and not necessarily the views of Sony Ericsson  
> and Sony Ericsson accepts no responsibility or liability whatsoever  
> or howsoever arising in connection with this e-mail.Any  
> attachment(s) to this message has been checked for viruses, but  
> please rely on your own virus checker and procedures. If you contact  
> us by e-mail, we will store your name and address to facilitate  
> communications. If you are not the intended recipient, please inform  
> the sender by replying this transmission and delete the e-mail and  
> any copies of it without disclosing it.
>
>
> <Secure Cred Manager.pptx><File granularity access policy.pptx>
Received on Wednesday, 16 December 2009 14:17:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:03 GMT