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

Thursday, 29 May 2014

• [Bug 25912] DOMException.prototype.message is up to implementations bugzilla@jessica.w3.org
• [Bug 25912] DOMException.prototype.message is up to implementations bugzilla@jessica.w3.org
• [Bug 25912] New: DOMException.prototype.message is up to implementations bugzilla@jessica.w3.org

Wednesday, 28 May 2014

• [W3C Web Crypto WG] Web Crypto API Last Call status (27th of may) GALINDO Virginie

Tuesday, 27 May 2014

• RE: URGENT: Meeting for WebCrypto WG in TPAC at end of October October? 조상래

Monday, 26 May 2014

• Re: URGENT: Meeting for WebCrypto WG in TPAC at end of October October? Richard Barnes
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• URGENT: Meeting for WebCrypto WG in TPAC at end of October October? GALINDO Virginie

Saturday, 24 May 2014

• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• URGENT: Meeting for WebCrypto WG in TPAC at end of October October? Harry Halpin
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org

Wednesday, 21 May 2014

• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25857] New: Extractability is not always specified when importing keys (in particular public keys) bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25842] Web developers given enough crypto rope to shoot selves in foot bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org

Tuesday, 20 May 2014

• [Bug 25842] New: Web developers given enough crypto rope to shoot selves in foot bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] New: Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25826] The "hash attribute of the algorithm attribute of key" is invalid. There is no hash attribute in the algorithm attribute of key. bugzilla@jessica.w3.org
• [Bug 25826] New: The "hash attribute of the algorithm attribute of key" is invalid. There is no hash attribute in the algorithm attribute of key. bugzilla@jessica.w3.org
• Fwd: W3C Workshop: Web Cryptography Next Steps Harry Halpin
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25820] Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25820] New: Should empty key usages be allowed when creating keys? bugzilla@jessica.w3.org
• [Bug 25710] No Key Deletion bugzilla@jessica.w3.org

Monday, 19 May 2014

• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 25819] New: Example of how deriveKey works bugzilla@jessica.w3.org
• [Bug 25710] No Key Deletion bugzilla@jessica.w3.org
• [Bug 25710] No Key Deletion bugzilla@jessica.w3.org
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• [Bug 25710] No Key Deletion bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• OperationError vs DataError Mark Watson
• [Bug 25816] New: DH import of PKCS8 uses OperationError instead of DataError for privateKeyInfo parse failure 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 25815] New: Spec encourages unsafe handling of secret data for JWK import of RSA/ECC keys bugzilla@jessica.w3.org
• [Bug 25799] supercookies bugzilla@jessica.w3.org
• [Bug 25799] supercookies bugzilla@jessica.w3.org
• [Bug 25799] New: supercookies bugzilla@jessica.w3.org
• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org

Sunday, 18 May 2014

• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org

Friday, 16 May 2014

• [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 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 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 25741] RSA-OAEP is under-specified when the parameters define an operation not supported by the key size bugzilla@jessica.w3.org
• [Bug 25741] New: RSA-OAEP is under-specified when the parameters define an operation not supported by the key size bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org

Thursday, 15 May 2014

• [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
• Update to Key Discovery draft Mark Watson
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• Re: Should we do a call Monday re Last Call? Harry Halpin
• Re: Should we do a call Monday re Last Call? Ryan Sleevi
• Re: Should we do a call Monday re Last Call? Harry Halpin
• [Bug 25706] Incomplete Key Generation Definitions bugzilla@jessica.w3.org
• RE: Should we do a call Monday re Last Call? GALINDO Virginie
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• Re: Should we do a call Monday re Last Call? Richard Barnes
• Re: Should we do a call Monday re Last Call? Ryan Sleevi
• Should we do a call Monday re Last Call? Harry Halpin
• [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 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 25721] New: extractable keys should be disabled by default bugzilla@jessica.w3.org

Wednesday, 14 May 2014

• [Bug 25718] New: Support RSA-OAEP with the SHA-2* family of algorithms in JWK bugzilla@jessica.w3.org
• [Bug 24827] Be clearer about the distinction between operations and methods bugzilla@jessica.w3.org
• [Bug 25717] New: Provide informative text noting when a parameter in an SPKI/PKCS8/JWK is ignored bugzilla@jessica.w3.org
• [Bug 23786] Please specify a mapping between WebCrypto AlgorithmIdentifiers and pkcs-1 ones bugzilla@jessica.w3.org
• [Bug 23786] Please specify a mapping between WebCrypto AlgorithmIdentifiers and pkcs-1 ones bugzilla@jessica.w3.org
• [Bug 23786] Please specify a mapping between WebCrypto AlgorithmIdentifiers and pkcs-1 ones bugzilla@jessica.w3.org
• [Bug 24827] Be clearer about the distinction between operations and methods bugzilla@jessica.w3.org
• [Bug 24827] Be clearer about the distinction between operations and methods bugzilla@jessica.w3.org
• [Bug 23786] Please specify a mapping between WebCrypto AlgorithmIdentifiers and pkcs-1 ones bugzilla@jessica.w3.org
• [Bug 25706] Incomplete Key Generation Definitions bugzilla@jessica.w3.org
• [Bug 25711] Not clear if keys persist across sessions bugzilla@jessica.w3.org
• [Bug 25710] No Key Deletion bugzilla@jessica.w3.org
• [Bug 25711] New: Not clear if keys persist across sessions bugzilla@jessica.w3.org
• [Bug 25710] New: No Key Deletion bugzilla@jessica.w3.org
• [Bug 25706] New: Incomplete Key Generation Definitions bugzilla@jessica.w3.org

Tuesday, 13 May 2014

• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org

Monday, 12 May 2014

• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [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 25661] New: Allow algorithms to be implemented "as if", rather than strict adherance bugzilla@jessica.w3.org
• [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 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Harry Halpin
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Ryan Sleevi
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Harry Halpin
• RE: [W3C Web Crypto WG] Security considerations and recommended algorithms bug GALINDO Virginie
• RE: [W3C Web Crypto WG] Security considerations and recommended algorithms bug GALINDO Virginie
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Harry Halpin
• RE: [W3C Web Crypto WG] Security considerations and recommended algorithms bug GALINDO Virginie
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Ryan Sleevi
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Harry Halpin
• [Bug 25387] BigInteger bugzilla@jessica.w3.org
• [Bug 25387] BigInteger bugzilla@jessica.w3.org
• [Bug 25390] Use [Exposed] in IDL bugzilla@jessica.w3.org
• [Bug 25390] Use [Exposed] in IDL bugzilla@jessica.w3.org
• [Bug 25658] Need normative reference for ArrayBufferView type bugzilla@jessica.w3.org
• [Bug 25388] Boolean arguments bugzilla@jessica.w3.org
• [Bug 25387] BigInteger bugzilla@jessica.w3.org
• [Bug 25659] New: AES-CBC mode does not describe concretely how padding is added bugzilla@jessica.w3.org
• [Bug 25436] Handling of CryptoOperationData needs to be defined bugzilla@jessica.w3.org
• [Bug 25626] Convert the various KeyAlgorithm interfaces into Dictionaries bugzilla@jessica.w3.org
• [Bug 25658] Need normative reference for ArrayBufferView type bugzilla@jessica.w3.org
• [Bug 25658] New: Need normative reference for ArrayBufferView type bugzilla@jessica.w3.org
• [Bug 23728] CryptoOperationData can be mutated during operation bugzilla@jessica.w3.org
• [Bug 23728] CryptoOperationData can be mutated during operation bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Ryan Sleevi

Saturday, 10 May 2014

• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org

Friday, 9 May 2014

• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• [Bug 25387] BigInteger bugzilla@jessica.w3.org
• [Bug 25431] Error names allow RSAES-PKCS1-v1_5 oracle attack against wrapped keys bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Richard Barnes
• [W3C Web Crypto WG] Security considerations and recommended algorithms bug GALINDO Virginie
• [Bug 25627] New: Indicate that Key objects have internal state, and that the attributes they expose are reflections of that internal state bugzilla@jessica.w3.org
• [Bug 25626] New: Convert the various KeyAlgorithm interfaces into Dictionaries bugzilla@jessica.w3.org
• [Bug 25625] New: Provide a better explanation for the (informative) table in Section 18.1 bugzilla@jessica.w3.org
• [Bug 25624] New: Update Promise-using language to reflect the addition of Promises to ES6 bugzilla@jessica.w3.org
• [Bug 25623] New: Typographic: Web IDL is two words, not one bugzilla@jessica.w3.org
• [Bug 25622] New: Use RangeError instead of QuotaExceededError bugzilla@jessica.w3.org
• [Bug 25621] New: Provide better explanation for the concerns of Section 6 bugzilla@jessica.w3.org
• [Bug 25620] New: Provide informative text regarding the origin-based security model of the API bugzilla@jessica.w3.org
• [Bug 25619] New: Provide (non-normative) explanations for terminology like cryptographic provider bugzilla@jessica.w3.org
• [Bug 25618] New: Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org

Thursday, 8 May 2014

• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25607] New: Need to advise authors about security considerations bugzilla@jessica.w3.org

Tuesday, 6 May 2014

• Re: Is the "Key" interface name too generic? Mark Watson
• Re: Is the "Key" interface name too generic? Boris Zbarsky
• Re: Is the "Key" interface name too generic? Mark Watson
• Re: Is the "Key" interface name too generic? Richard Barnes
• PROPOSAL: Moving from telecons to a more mailinglist/bugzilla-centric working style Harry Halpin
• Minutes from the May 5th telecon Harry Halpin
• Re: Is the "Key" interface name too generic? Boris Zbarsky
• Re: Is the "Key" interface name too generic? Ryan Sleevi
• [W3C Web Crypto] About Payment and Web Crypto intersection GALINDO Virginie
• Re: Is the "Key" interface name too generic? Boris Zbarsky
• [Bug 25577] New: The interface name "Key" is very generic bugzilla@jessica.w3.org
• [Bug 25571] New: Add JOSE mappings for RSA in A.1 bugzilla@jessica.w3.org
• [Bug 25570] New: Need to register RS1 in Section 21.1 bugzilla@jessica.w3.org
• [Bug 25569] New: Suggest adding recommended algorithms to Section 18.2 bugzilla@jessica.w3.org

Monday, 5 May 2014

• [W3C Web Crypto WG] minutes of 05th of May call GALINDO Virginie
• Call is on, if you wanna join.... GALINDO Virginie
• [Bug 25558] New: Editorial nits bugzilla@jessica.w3.org
• [Bug 25557] New: Spec should allow returning NotSupportedError for reasons other than failed Algorithm normalization bugzilla@jessica.w3.org
• W3C Web Crypto WG - status (and lets discuss tonight) GALINDO Virginie

Last message date: Thursday, 29 May 2014 17:40:47 UTC