crypto-ISSUE-20 (key and attribute storage): What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes [Web Cryptography API] from Web Cryptography Working Group Issue Tracker on 2012-08-13 (public-webcrypto@w3.org from August 2012)

From: Web Cryptography Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 13 Aug 2012 21:11:08 +0000
To: public-webcrypto@w3.org
Message-Id: <E1T11um-0005ep-TZ@tibor.w3.org>

crypto-ISSUE-20 (key and attribute storage): What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes [Web Cryptography API]

http://www.w3.org/2012/webcrypto/track/issues/20

Raised by: Virginie GALINDO
On product: Web Cryptography API

During the 6th of August conference call it was discussed the possibility to tight key and its attribute in a common storage. While some views mentioned that a logical model of the key was enough to manage the consistency of the 'couple' key-attributes, some other view wanted to clearly have the same ___location to store key and attributes which are not set by application, but browser (e.g. extractable).

Received on Monday, 13 August 2012 21:11:17 UTC