public-webcrypto@w3.org from September 2014 by date

Tuesday, 30 September 2014

• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org

Monday, 29 September 2014

• Fwd: Parameter validation Mark Watson
• Parameter validation Mark Watson
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [W3C Web Crypto WG] our next call is on 13th of October, can you make it ? GALINDO Virginie
• W3C Web Crypto WG - minutes of 29th of sept call GALINDO Virginie
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Mark Watson
• RE: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Mike Jones
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Mark Watson
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Harry Halpin
• RE: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call GALINDO Virginie
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Ryan Sleevi
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Harry Halpin
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Mark Watson
• Re: [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call Harry Halpin
• [Bug 25557] Spec should allow returning NotSupportedError for reasons other than failed Algorithm normalization bugzilla@jessica.w3.org
• [W3C Web Crypto WG] today's agenda, including resolution to exit Last Call GALINDO Virginie
• [Bug 25557] Spec should allow returning NotSupportedError for reasons other than failed Algorithm normalization bugzilla@jessica.w3.org
• [Bug 26741] Reject invalid EC public keys bugzilla@jessica.w3.org

Friday, 26 September 2014

• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25625] Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 26911] Attempting to use a EC key with mis-matched curve should be InvalidAccessError bugzilla@jessica.w3.org
• [Bug 26315] ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous bugzilla@jessica.w3.org
• [Bug 26315] ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous bugzilla@jessica.w3.org
• [Bug 26911] Attempting to use a EC key with mis-matched curve should be InvalidAccessError bugzilla@jessica.w3.org
• [Bug 25557] Spec should allow returning NotSupportedError for reasons other than failed Algorithm normalization bugzilla@jessica.w3.org
• [Bug 26315] ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 26300] Normalization: "If alg is an IDL object" is confusing bugzilla@jessica.w3.org
• [Bug 25912] DOMException.prototype.message is up to implementations bugzilla@jessica.w3.org
• [Bug 25624] Update Promise-using language to reflect the addition of Promises to ES6 bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26536] Length property of HmacDerivedKeyParams seems redundant bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 25706] Incomplete Key Generation Definitions bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25912] DOMException.prototype.message is up to implementations bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 26895] use ArrayBufferData typedef bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25741] RSA-OAEP is under-specified when the parameters define an operation not supported by the key size bugzilla@jessica.w3.org
• [Bug 26911] Attempting to use a EC key with mis-matched curve should be InvalidAccessError bugzilla@jessica.w3.org
• [Bug 26911] New: Attempting to use a EC key with mis-matched curve should be InvalidAccessError bugzilla@jessica.w3.org
• [Bug 25624] Update Promise-using language to reflect the addition of Promises to ES6 bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26301] Normalization: Should throw instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 26301] Normalization: Should throw instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 26322] Definitions "algorithm" and "usages" properties of CryptoKey make no sense bugzilla@jessica.w3.org
• [Bug 26301] Normalization: Should through instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 26322] Definitions "algorithm" and "usages" properties of CryptoKey make no sense bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25625] Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 24827] Be clearer about the distinction between operations and methods bugzilla@jessica.w3.org
• [Bug 25198] Turn KeyFormat into an enum bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 26536] Length property of HmacDerivedKeyParams seems redundant bugzilla@jessica.w3.org
• [Bug 26536] Length property of HmacDerivedKeyParams seems redundant bugzilla@jessica.w3.org
• [Bug 26674] Use required dictionary entries instead of hacks with nullable bugzilla@jessica.w3.org
• [Bug 26331] Usage Intersection is defined as operating on arrays, rather than sequences bugzilla@jessica.w3.org
• [Bug 26380] importKey doesn't define handling of keyData in some cases bugzilla@jessica.w3.org
• [Bug 26320] RsaHashedKeyAlgorithm inherits from RsaKeyAlgorithm bugzilla@jessica.w3.org
• [Bug 26214] Define consistent error when calling exportKey() with unsupported key format bugzilla@jessica.w3.org
• [Bug 26902] RSA SSA/PSS validation of use field during JWK import is wrong bugzilla@jessica.w3.org
• [Bug 26905] PBKDF2 should support usage value of deriveBits bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 26413] Inconsistent handling of usages parameter between importKey and generateKey bugzilla@jessica.w3.org
• [Bug 26674] Use required dictionary entries instead of hacks with nullable bugzilla@jessica.w3.org

Thursday, 25 September 2014

• [Bug 26674] Use required dictionary entries instead of hacks with nullable bugzilla@jessica.w3.org
• [Bug 26331] Usage Intersection is defined as operating on arrays, rather than sequences bugzilla@jessica.w3.org
• [Bug 26380] importKey doesn't define handling of keyData in some cases bugzilla@jessica.w3.org
• [Bug 26741] Reject invalid EC public keys bugzilla@jessica.w3.org
• [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? bugzilla@jessica.w3.org
• [Bug 26320] RsaHashedKeyAlgorithm inherits from RsaKeyAlgorithm bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 26411] Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org
• [Bug 26412] Asymmetric algorithms do not specify how to compute usages/extractability during importKey bugzilla@jessica.w3.org
• [Bug 26902] RSA SSA/PSS validation of use field during JWK import is wrong bugzilla@jessica.w3.org
• [Bug 26905] PBKDF2 should support usage value of deriveBits bugzilla@jessica.w3.org
• [Bug 26903] Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• Re: Method and operation names Mark Watson
• [Bug 26905] New: PBKDF2 should support usage value of deriveBits bugzilla@jessica.w3.org
• [Bug 26903] New: Parameter validation errors should return SyntaxError not DataError bugzilla@jessica.w3.org
• [Bug 26902] RSA SSA/PSS validation of use field during JWK import is wrong bugzilla@jessica.w3.org
• [Bug 26902] New: RSASSA validation of use field during JWK import is wrong bugzilla@jessica.w3.org
• Method and operation names Mark Watson
• New security fetaure : Looking for a home for a proposed Credential Management API. GALINDO Virginie

Wednesday, 24 September 2014

• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25468] "CONCAT" KDF only supports deriveBits, not deriveKey bugzilla@jessica.w3.org
• [Bug 25433] Wrong operations in registered algorithms table bugzilla@jessica.w3.org
• [Bug 26011] Add importKey/exportKey marks for PBKDF2 bugzilla@jessica.w3.org
• [Bug 25857] Extractability is not always specified when importing keys (in particular public keys) bugzilla@jessica.w3.org
• [Bug 25717] Provide informative text noting when a parameter in an SPKI/PKCS8/JWK is ignored bugzilla@jessica.w3.org
• [Bug 25659] AES-CBC mode does not describe concretely how padding is added bugzilla@jessica.w3.org
• [Bug 25625] Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25382] What error is returned when key mismatches operation? bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 26895] New: use ArrayBufferData typedef bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 26348] Allow JWK for PBKDF2 bugzilla@jessica.w3.org
• [Bug 26413] Inconsistent handling of usages parameter between importKey and generateKey bugzilla@jessica.w3.org
• [Bug 26011] Add importKey/exportKey marks for PBKDF2 bugzilla@jessica.w3.org
• [Bug 26011] Add importKey/exportKey marks for PBKDF2 bugzilla@jessica.w3.org
• [Bug 25857] Extractability is not always specified when importing keys (in particular public keys) bugzilla@jessica.w3.org
• [Bug 25717] Provide informative text noting when a parameter in an SPKI/PKCS8/JWK is ignored bugzilla@jessica.w3.org

Tuesday, 23 September 2014

• [Bug 25659] AES-CBC mode does not describe concretely how padding is added bugzilla@jessica.w3.org
• [Bug 25659] AES-CBC mode does not describe concretely how padding is added bugzilla@jessica.w3.org
• [Bug 25625] Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 25468] "CONCAT" KDF only supports deriveBits, not deriveKey bugzilla@jessica.w3.org
• [Bug 25433] Wrong operations in registered algorithms table bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25382] What error is returned when key mismatches operation? bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• Resolving minor bugs this week Mark Watson

Monday, 22 September 2014

• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• Re: Urgent: Register for TPAC 2014 Web Crypto F2F meeting Harry Halpin
• Re: Urgent: Register for TPAC 2014 Web Crypto F2F meeting Richard Barnes
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 26301] Normalization: Should through instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 26178] ECMAScript standard library bugzilla@jessica.w3.org
• [Bug 26301] Normalization: Should through instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 26536] Length property of HmacDerivedKeyParams seems redundant bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? bugzilla@jessica.w3.org
• [Bug 26411] Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org
• [Bug 26348] Allow JWK for PBKDF2 bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26315] ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26214] Define consistent error when calling exportKey() with unsupported key format bugzilla@jessica.w3.org
• [Bug 26178] ECMAScript standard library bugzilla@jessica.w3.org
• [Bug 25857] Extractability is not always specified when importing keys (in particular public keys) bugzilla@jessica.w3.org
• [Bug 25815] Spec encourages unsafe handling of secret data for JWK import of RSA/ECC keys bugzilla@jessica.w3.org
• [Bug 25741] RSA-OAEP is under-specified when the parameters define an operation not supported by the key size bugzilla@jessica.w3.org
• [Bug 25717] Provide informative text noting when a parameter in an SPKI/PKCS8/JWK is ignored bugzilla@jessica.w3.org
• [Bug 25625] Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 25468] "CONCAT" KDF only supports deriveBits, not deriveKey bugzilla@jessica.w3.org
• [Bug 25433] Wrong operations in registered algorithms table bugzilla@jessica.w3.org
• [Bug 25389] Define octet string bugzilla@jessica.w3.org
• [Bug 25383] UnknownError, DataError are also defined by Indexed DB spec bugzilla@jessica.w3.org
• [Bug 24827] Be clearer about the distinction between operations and methods bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• Re: On the late side again? Agenda for 2014-09-23 Harry Halpin
• [W3C web crypto WG] Exit Web Crypto API from Last Call (for WG participants only) GALINDO Virginie
• Re: [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API Harry Halpin
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Harry Halpin
• Urgent: Register for TPAC 2014 Web Crypto F2F meeting Harry Halpin

Saturday, 20 September 2014

• [Bug 26741] Reject invalid EC public keys bugzilla@jessica.w3.org

Friday, 19 September 2014

• [Bug 26674] Use required dictionary entries instead of hacks with nullable bugzilla@jessica.w3.org
• [Bug 26866] Add "required" to dictionary members; drop bugzilla@jessica.w3.org
• [Bug 26866] New: Add "required" to dictionary members; drop bugzilla@jessica.w3.org
• [Bug 26011] Add importKey/exportKey marks for PBKDF2 bugzilla@jessica.w3.org
• [Bug 25382] What error is returned when key mismatches operation? bugzilla@jessica.w3.org

Tuesday, 16 September 2014

• [W3C Web Crypto WG] new publication tool GALINDO Virginie
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification GALINDO Virginie
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• W3C Web Crypto WG - Workshop outcome GALINDO Virginie
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification GALINDO Virginie

Thursday, 11 September 2014

• crypto-ACTION-147: Review sysapps secure element discussion Web Cryptography Working Group Issue Tracker
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson

Wednesday, 10 September 2014

• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification Mike Jones
• [Bug 25972] Please require a secure origin bugzilla@jessica.w3.org

Tuesday, 9 September 2014

• [Bug 25571] Add JOSE mappings for RSA in A.1 bugzilla@jessica.w3.org

Monday, 8 September 2014

• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Ryan Sleevi
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• [W3C Web Crypto WG] - our F2F meeting in Santa Clara on 30th of Oct during TPAC GALINDO Virginie
• W3C Web Crypto WG - the web crypto next workshop is this week GALINDO Virginie
• W3C Web Crypto WG - our next call will be on monday 29th of September @ 20:00 UTC GALINDO Virginie

Friday, 5 September 2014

• Re: How to handle invalid EC public keys Richard Barnes
• [Bug 26741] New: Reject invalid EC public keys bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API Richard Barnes
• RE: [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API Lu HongQian Karen

Thursday, 4 September 2014

• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Ryan Sleevi
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification Mike Jones
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Ryan Sleevi
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification Mike Jones
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Ryan Sleevi
• RE: How to handle invalid EC public keys Vijay Bharadwaj
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification Brian LaMacchia
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API - vote before the 16th of sept GALINDO Virginie
• Re: How to handle invalid EC public keys Ryan Sleevi
• How to handle invalid EC public keys Richard Barnes

Tuesday, 2 September 2014

• [Bug 26413] Inconsistent handling of usages parameter between importKey and generateKey bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Ryan Sleevi
• Re: [W3C Web Crypto WG] about extensions to Web Crypto specification Mark Watson
• RE: [W3C Web Crypto WG] about extensions to Web Crypto specification Mike Jones
• Re: [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API Mark Watson
• RE: [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API Mike Jones
• [W3C Web Crypto WG] about extensions to Web Crypto specification GALINDO Virginie
• [W3C Web Crypto WG] CfC : Call for Consensus on the integration of new curves in Web Crypto API GALINDO Virginie

Monday, 1 September 2014

• No meeting today Harry Halpin

Last message date: Tuesday, 30 September 2014 14:22:08 UTC