- From: Mark Watson <watsonm@netflix.com>
- Date: Mon, 27 Aug 2012 21:07:55 +0000
- To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
- CC: Lu HongQian Karen <karen.lu@gemalto.com>, Ali Asad <Asad.Ali@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
As mentioned on the call, I think this is related to ISSUE-25. One way for an application to know where a pre-shared key is stored is for that key to have an associated unique identifier which is communicated to the application server out-of-band as well as by the client. �Mark On Aug 27, 2012, at 1:49 PM, GALINDO Virginie wrote: > Karen, Asad, and all, > As per your request of todays call, I have created an issue about the ___location of the key. Feel free to amend/comment its description and agree with the editors to make sure it is correctly expressed in the version of our draft API going to the FPWD. > Regards, > Virginie > Gemalto > Chair of the Web Crypto WG > > -----Original Message----- > From: Web Cryptography Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] > Sent: lundi 27 ao�t 2012 22:46 > To: public-webcrypto@w3.org > Subject: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] > > crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] > > http://www.w3.org/2012/webcrypto/track/issues/30 > > Raised by: Karen Lu > On product: Web Cryptography API > > During our discussion on the 27th of august, the problem related to usage of keys stored in secure element has been discussed. While a previous issue (#11] has been already closed about the definition of a specific attribute for indicating if the key was stored in a specific secure element (or crypto providers), the problem about making sure the application is aware of the key ___location is still pending. The means for solving this specific problem do not need to rely on a specific attribute. > > >
Received on Monday, 27 August 2012 21:08:23 UTC