ISSUE-20: What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes
key and attribute storage
What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes
- State:
- CLOSED
- Product:
- Web Cryptography API
- Raised by:
- Virginie GALINDO
- Opened on:
- 2012-08-13
- Description:
- 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).
- Related Actions Items:
- No related actions
- Related emails:
- Draft minutes, 9/4 call (from wseltzer@w3.org on 2012-09-04)
- Code: 83263 / Re: W3C Web Crypto WG - agenda for 4th of sept call - today (from wseltzer@w3.org on 2012-09-04)
- W3C Web Crypto WG - agenda for 4th of sept call - today (from Virginie.GALINDO@gemalto.com on 2012-09-04)
- CLOSING ISSUE-20 (from sleevi@google.com on 2012-08-30)
- 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 sysbot+tracker@w3.org on 2012-08-13)
Related notes:
No additional notes.
Display change log
