초기단계에서 적절한 의견을 제시하면 빠르게 피드백을 받을 수 있는 장점이 있습니다.
---------- Forwarded message ----------
From:
Web Cryptography Working Group Issue Tracker <sysbot+...@w3.org>Date: Tue, Aug 14, 2012 at 6:11 AM
Subject: 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]
To:
public-w...@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).