Account Options>

  1. Sign in
WEB Crypto WG - Issue Prioritization - 17Sept2012
 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
date17/09/2012
2
ISSUEStatusDescriptionDomainPriority
3
ISSUE-36RAISEDSemantics for key generation versus key derivationcryptohigh
4
ISSUE-3PENDING REVIEWDecide whether algorithm discovery is necessaryfunctionalhigh
5
ISSUE-38RAISEDKey initialization and "finalization"functionalhigh
6
ISSUE-35RAISEDHandling of wrap/unwrap operationsfunctionalhigh
7
ISSUE-12RAISEDShould the API distinguish between algorithm and operation parameters?usabilityhigh
8
ISSUE-14RAISEDRepresentation of raw key materialusabilityhigh
9
ISSUE-18RAISEDShould it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?usabilityhigh
10
ISSUE-29RAISEDHandling of block encryption modes and paddingcryptomedium
11
ISSUE-31RAISEDProblems with keys attribute of the Crypto interfacefunctionalmedium
12
ISSUE-17RAISEDDefine the scope and API for custom key attributesfunctionalmedium
13
ISSUE-6RAISEDConcern around KeyQueryList being synchronousfunctionalmedium
14
ISSUE-8RAISEDMaking sure we describe the clean key neuteringfunctionalmedium
15
ISSUE-22RAISEDShould CryptoOperations be clonablefunctionalmedium
16
ISSUE-5RAISEDPublic vs. private key pairs -- managing the key pair via a single or multiple handlesusabilitymedium
17
ISSUE-23RAISEDShould CryptoOperations and/or Keys support Transferrable semantics?usabilitymedium
18
ISSUE-28RAISEDShort-names for algorithmsusabilitymedium
19
ISSUE-37RAISEDMethod namingusabilitymedium
20
ISSUE-19RAISEDDoes it make sense to have authorized-origin and specific-origin keysaccess control
21
ISSUE-2PENDING REVIEWHow to address pre-provisioned keys and managing ACLsaccess control
22
ISSUE-21RAISEDRequiring Content-Security-Policyaccess control
23
ISSUE-26RAISEDShould key generation be allowed to specify multi-origin shared accessaccess control
24
ISSUE-27RAISEDSpecification of AES-CTR mode counter bitscrypto
25
ISSUE-10RAISEDMaking sure our API is usable with pure js environementdesign
26
ISSUE-24RAISEDDefining a Synchronous APIdesign
27
ISSUE-7RAISEDDeciding if we integrate a high level API in our deliverabledesign
28
ISSUE-9RAISEDwhat will be the mean to integrate in the API the fact that key usage may need user consent ?design
29
ISSUE-33RAISEDClarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenarioedition
30
ISSUE-32RAISEDSection 5.2 in API draft should mention use of secure element in the context of key securityedition
31
ISSUE-39RAISEDAdd abort() to the KeyOperation interfacefunctional
32
ISSUE-25RAISEDHow do we provision Global Unique ID for pre-provisionned symetric keyskey
33
ISSUE-30RAISEDHow does the application know where the key is stored ?key
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