WebCryptoWG_issue_structuring_18Sept2012
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Still loading...
ABCDEFGHIJKLMNOPQRST
1
27Sept2012
2
ISSUEStatusDescriptionDomainPriority
3
ISSUE-36RAISEDSemantics for key generation versus key derivationcryptohighhttp://www.w3.org/2012/webcrypto/track/issues/36
4
ISSUE-3PENDING REVIEWDecide whether algorithm discovery is necessaryfunctionalhighhttp://www.w3.org/2012/webcrypto/track/issues/3
5
ISSUE-38RAISEDKey initialization and "finalization"functionalhighhttp://www.w3.org/2012/webcrypto/track/issues/38
6
ISSUE-35RAISEDHandling of wrap/unwrap operationsfunctionalhighhttp://www.w3.org/2012/webcrypto/track/issues/35
7
ISSUE-25RAISEDHow do we provision Global Unique ID for pre-provisionned symetric keyskey definitionhighhttp://www.w3.org/2012/webcrypto/track/issues/25
8
ISSUE-30RAISEDHow does the application know where the key is stored ?key definitionhighhttp://www.w3.org/2012/webcrypto/track/issues/30
9
ISSUE-12RAISEDShould the API distinguish between algorithm and operation parameters?usabilityhighhttp://www.w3.org/2012/webcrypto/track/issues/12
10
ISSUE-14RAISEDRepresentation of raw key materialusabilityhighhttp://www.w3.org/2012/webcrypto/track/issues/14
11
ISSUE-18RAISEDShould it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?usabilityhighhttp://www.w3.org/2012/webcrypto/track/issues/18
12
ISSUE-29RAISEDHandling of block encryption modes and paddingcryptomedium
13
ISSUE-31RAISEDProblems with keys attribute of the Crypto interfacefunctionalmedium
14
ISSUE-40RAISEDHow should we define key discovery, noting asynchronicityfunctionalmedium
15
ISSUE-8RAISEDMaking sure we describe the clean key neuteringfunctionalmedium
16
ISSUE-22RAISEDShould CryptoOperations be clonablefunctionalmedium
17
ISSUE-17RAISEDPublic vs. private key pairs -- managing the key pair via a single or multiple handleskey definitionmedium
18
ISSUE-19RAISEDDoes it make sense to have authorized-origin and specific-origin keyskey definitionmedium
19
ISSUE-2PENDING REVIEWHow to address pre-provisioned keys and managing ACLskey definitionmedium
20
ISSUE-26RAISEDShould key generation be allowed to specify multi-origin shared accesskey definitionmedium
21
ISSUE-21RAISEDRequiring Content-Security-Policysecurity frameworkmedium
22
ISSUE-5RAISEDPublic vs. private key pairs -- managing the key pair via a single or multiple handlesusabilitymedium
23
ISSUE-23RAISEDShould CryptoOperations and/or Keys support Transferrable semantics?usabilitymedium
24
ISSUE-28RAISEDShort-names for algorithmsusabilitymedium
25
ISSUE-37RAISEDMethod namingusabilitymedium
26
ISSUE-27RAISEDSpecification of AES-CTR mode counter bitscrypto
27
ISSUE-10RAISEDMaking sure our API is usable with pure js environementdesign
28
ISSUE-24RAISEDDefining a Synchronous APIdesign
29
ISSUE-7RAISEDDeciding if we integrate a high level API in our deliverabledesign
30
ISSUE-9RAISEDwhat will be the mean to integrate in the API the fact that key usage may need user consent ?design
31
ISSUE-33RAISEDClarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenarioedition
32
ISSUE-32RAISEDSection 5.2 in API draft should mention use of secure element in the context of key securityedition
33
ISSUE-39RAISEDAdd abort() to the KeyOperation interfacefunctional
34
ISSUE-15RAISEDDiscovering certificates associated with (private) keysnext
35
ISSUE-34RAISEDRepresentation of certificatesnext
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Feuille1