ISSUE-1![(edit)](/2002/09/wbs/icons/stock_edit2) Mandatory |
CLOSED |
Should we have mandatory algorithms? |
2012-07-02 |
Web Cryptography API |
0 |
ISSUE-2![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
How to address pre-provisioned keys and managing ACLs |
2012-07-09 |
key definition for Web Crypto API |
0 |
ISSUE-4![(edit)](/2002/09/wbs/icons/stock_edit2) MUST or SHOULD |
CLOSED |
Will the set of algorithm be required with a SHOULD or a MUST in Web Crypto API ? |
2012-07-19 |
Web Cryptography API |
0 |
ISSUE-5![(edit)](/2002/09/wbs/icons/stock_edit2) Keypair |
CLOSED |
Public vs. private key pairs -- managing the key pair via a single or multiple handles |
2012-07-25 |
usability for Web Crypto API |
0 |
ISSUE-6![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Concern around KeyQueryList being synchronous |
2012-07-25 |
Web Cryptography API |
0 |
ISSUE-7![(edit)](/2002/09/wbs/icons/stock_edit2) high level API |
CLOSED |
Deciding if we integrate a high level API in our deliverable |
2012-08-01 |
design for Web Crypto API |
0 |
ISSUE-8![(edit)](/2002/09/wbs/icons/stock_edit2) key neutering |
CLOSED |
Making sure we describe the clean key neutering |
2012-08-01 |
Web Cryptography API |
0 |
ISSUE-9![(edit)](/2002/09/wbs/icons/stock_edit2) user consent |
CLOSED |
what will be the mean to integrate in the API the fact that key usage may need user consent ? |
2012-08-01 |
design for Web Crypto API |
0 |
ISSUE-10![(edit)](/2002/09/wbs/icons/stock_edit2) pure js environment |
CLOSED |
Making sure our API is usable with pure js environement |
2012-08-01 |
design for Web Crypto API |
0 |
ISSUE-11![(edit)](/2002/09/wbs/icons/stock_edit2) storage attribute |
CLOSED |
Is there a need for a storage attribute, indicating storage in a hardware token |
2012-08-03 |
|
0 |
ISSUE-12![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Should the API distinguish between algorithm and operation parameters? |
2012-08-06 |
usability for Web Crypto API |
1 |
ISSUE-13![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Relationship between the W3C Web Cryptography work product and the IETF JOSE WG |
2012-08-06 |
Web Cryptography API |
0 |
ISSUE-14![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Representation of raw key material |
2012-08-06 |
usability for Web Crypto API |
0 |
ISSUE-16![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Definition for Key Expiration |
2012-08-06 |
Web Cryptography API |
0 |
ISSUE-17![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Define the scope and API for custom key attributes |
2012-08-06 |
key definition for Web Crypto API |
0 |
ISSUE-18![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? |
2012-08-06 |
usability for Web Crypto API |
0 |
ISSUE-19![(edit)](/2002/09/wbs/icons/stock_edit2) origin-bound key |
CLOSED |
Does it make sense to have authorized-origin and specific-origin keys |
2012-08-13 |
key definition for Web Crypto API |
0 |
ISSUE-20![(edit)](/2002/09/wbs/icons/stock_edit2) key and attribute storage |
CLOSED |
What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes |
2012-08-13 |
Web Cryptography API |
0 |
ISSUE-21![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Requiring Content-Security-Policy |
2012-08-20 |
security framework for Web Crypto API |
0 |
ISSUE-22![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Should CryptoOperations be clonable |
2012-08-20 |
functional for Web Crypto API |
0 |
ISSUE-23![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Should CryptoOperations and/or Keys support Transferrable semantics? |
2012-08-20 |
usability for Web Crypto API |
0 |
ISSUE-24![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Defining a Synchronous API |
2012-08-20 |
|
0 |
ISSUE-25![(edit)](/2002/09/wbs/icons/stock_edit2) Global Unique ID |
CLOSED |
How do we provision Global Unique ID for pre-provisionned symetric keys |
2012-08-21 |
Web Crypto Key Discovery API |
0 |
ISSUE-26![(edit)](/2002/09/wbs/icons/stock_edit2) multi-origin access |
CLOSED |
Should key generation be allowed to specify multi-origin shared access |
2012-08-22 |
key definition for Web Crypto API |
0 |
ISSUE-27![(edit)](/2002/09/wbs/icons/stock_edit2) aes ctr |
CLOSED |
Specification of AES-CTR mode counter bits |
2012-08-22 |
crypto for Web Crypto API |
0 |
ISSUE-28![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Short-names for algorithms |
2012-08-22 |
usability for Web Crypto API |
1 |
ISSUE-29![(edit)](/2002/09/wbs/icons/stock_edit2) block modes |
CLOSED |
Handling of block encryption modes and padding |
2012-08-22 |
crypto for Web Crypto API |
0 |
ISSUE-30![(edit)](/2002/09/wbs/icons/stock_edit2) where is the key ? |
CLOSED |
How does the application know where the key is stored ? |
2012-08-27 |
Web Crypto Key Discovery API |
0 |
ISSUE-31![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Problems with keys attribute of the Crypto interface |
2012-08-27 |
functional for Web Crypto API |
0 |
ISSUE-32![(edit)](/2002/09/wbs/icons/stock_edit2) Key security |
CLOSED |
Section 5.2 in API draft should mention use of secure element in the context of key security |
2012-08-28 |
Web Cryptography API |
1 |
ISSUE-33![(edit)](/2002/09/wbs/icons/stock_edit2) Clarify key tainting |
CLOSED |
Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario |
2012-08-28 |
Web Cryptography API |
0 |
ISSUE-35![(edit)](/2002/09/wbs/icons/stock_edit2) wrapping |
CLOSED |
Handling of wrap/unwrap operations |
2012-08-28 |
functional for Web Crypto API |
0 |
ISSUE-36![(edit)](/2002/09/wbs/icons/stock_edit2) derivation |
CLOSED |
Semantics for key generation versus key derivation |
2012-08-28 |
crypto for Web Crypto API |
1 |
ISSUE-37![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Method naming |
2012-08-29 |
usability for Web Crypto API |
0 |
ISSUE-38![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Key initialization and "finalization" |
2012-08-30 |
next for Web Crypto API |
0 |
ISSUE-39![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Add abort() to the KeyOperation interface |
2012-09-06 |
functional for Web Crypto API |
0 |
ISSUE-40![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
How should we define key discovery, noting asynchronicity |
2012-09-17 |
Web Crypto Key Discovery API |
0 |
ISSUE-41![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Clean up algorithm normalization and support checks |
2013-04-01 |
design for Web Crypto API |
0 |
ISSUE-42![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Flatten AlgorithmParameters |
2013-04-18 |
design for Web Crypto API |
0 |
ISSUE-43![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Separate method for key agreement |
2013-04-23 |
design for Web Crypto API |
0 |
ISSUE-44![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Require creation of random IVs by default for CBC, CFB, GCM |
2013-04-23 |
|
1 |
ISSUE-45![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
HMAC key generation params needs a length field |
2013-06-05 |
crypto for Web Crypto API |
0 |
ISSUE-46![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Optional algorithm parameters must have default values |
2013-06-05 |
crypto for Web Crypto API |
1 |
ISSUE-47![(edit)](/2002/09/wbs/icons/stock_edit2) jimsch |
CLOSED |
AES-GCM Algorithm is missing tag properties for authentication tag |
2013-07-08 |
Web Cryptography API |
0 |
ISSUE-48![(edit)](/2002/09/wbs/icons/stock_edit2) jimsch |
CLOSED |
Does verify fulfill or rejectwhen a MAC/Signature does not verify |
2013-07-08 |
Web Cryptography API |
0 |
ISSUE-49![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Using Streams or something similar to support Multi-part on WebCrypto APIs |
2013-07-08 |
functional for Web Crypto API |
0 |
ISSUE-50![(edit)](/2002/09/wbs/icons/stock_edit2) ENTROPYNOTE |
CLOSED |
Should an informative note mention that entropy is expected? |
2013-09-30 |
|
0 |
ISSUE-51![(edit)](/2002/09/wbs/icons/stock_edit2) DECRYPT NOTE |
CLOSED |
Informative note about developer expectation re user access to decrypted data? |
2013-09-30 |
|
0 |
ISSUE-52![(edit)](/2002/09/wbs/icons/stock_edit2) DYNAMIC NONCE |
CLOSED |
Should the nonce, IV, and associated data be separated? |
2013-09-30 |
design for Web Crypto API |
0 |
ISSUE-53![(edit)](/2002/09/wbs/icons/stock_edit2) CBC |
CLOSED |
Add a note to AES-CBC/AES-CFB and add AES-PSM? |
2013-09-30 |
|
0 |
ISSUE-54![(edit)](/2002/09/wbs/icons/stock_edit2) RAWAES |
CLOSED |
Raw AES access? |
2013-09-30 |
|
0 |
ISSUE-55![(edit)](/2002/09/wbs/icons/stock_edit2) PBKDF2 Parameter |
CLOSED |
PBKDF2 Parameter Warning? |
2013-09-30 |
|
0 |
ISSUE-56![(edit)](/2002/09/wbs/icons/stock_edit2) EXTENSION |
CLOSED |
Should algorithms (ECC in particular) be extensible? |
2013-09-30 |
|
0 |
ISSUE-57![(edit)](/2002/09/wbs/icons/stock_edit2) DHIDL |
CLOSED |
IDLs for DH and ECDH |
2013-09-30 |
|
0 |
ISSUE-58![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Define how to derive/generate PBKDF2 keys |
2013-11-13 |
crypto for Web Crypto API |
0 |
ISSUE-59![(edit)](/2002/09/wbs/icons/stock_edit2) |
CLOSED |
Promises Programming Pattern Verification |
2013-11-14 |
design for Web Crypto API |
0 |