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

Thursday, 31 July 2014

• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields 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 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org

Wednesday, 30 July 2014

• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 26465] New: Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields bugzilla@jessica.w3.org
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org

Tuesday, 29 July 2014

• [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 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? 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 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? 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 26458] New: Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? bugzilla@jessica.w3.org

Monday, 28 July 2014

• [Bug 25721] extractable keys should be disabled by default bugzilla@jessica.w3.org
• Next WebCrypto call: Monday August 11, 20 UTC Wendy Seltzer
• Draft minutes from [W3C Web Crypto WG] 28 July call Wendy Seltzer
• Meeting minutes for July 28th meeting Harry Halpin
• Next call August 11th: Dedicated to extension and ECC Curves Harry Halpin
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec bugzilla@jessica.w3.org
• [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: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Ryan Sleevi
• [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
• Re: [W3C Web Crypto WG] Call for contributors on curve 25519 extension Ryan Sleevi
• [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
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• [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
• [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec 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

Sunday, 27 July 2014

• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org

Saturday, 26 July 2014

• [W3C Web Crypto WG] suggested resolution for NUMS curves, as part of the bug 25839 related to curve25519 GALINDO Virginie
• [W3C Web Crypto WG] Call for contributors on curve 25519 extension GALINDO Virginie
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 GALINDO Virginie
• RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 GALINDO Virginie
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org

Friday, 25 July 2014

• RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Brian LaMacchia
• RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Ryan Sleevi
• RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Brian LaMacchia
• Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Ryan Sleevi
• Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 GALINDO Virginie
• Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 Ryan Sleevi
• [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 GALINDO Virginie
• [W3C Web Crypto WG] suggested resolution for bug 25985 on browser interoperability GALINDO Virginie
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• RE: [W3C Web Crypto WG] suggested resolution for bug 26080 on removing non-NIST algo GALINDO Virginie
• [W3C Web Crypto WG] suggested resolution for bug 25607 related to security recommendation GALINDO Virginie
• [W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside GALINDO Virginie
• [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
• RE: [W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside Mike Jones

Thursday, 24 July 2014

• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25607] Need to advise authors about security considerations bugzilla@jessica.w3.org
• RE: [Cfrg] CFRG@IETF90 summary GALINDO Virginie
• Fwd: [Cfrg] CFRG@IETF90 summary Wendy Seltzer
• [W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside GALINDO Virginie
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org

Wednesday, 23 July 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 25815] Spec encourages unsafe handling of secret data for JWK import of RSA/ECC keys bugzilla@jessica.w3.org
• [Bug 26411] Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org

Tuesday, 22 July 2014

• [Bug 26411] Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org
• [Bug 26413] New: Inconsistent handling of usages parameter between importKey and generateKey bugzilla@jessica.w3.org
• [Bug 26412] New: Asymmetric algorithms do not specify how to compute usages/extractability during importKey bugzilla@jessica.w3.org
• [Bug 26411] Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org
• [Bug 26411] New: Caller can't force JWK to be distinguished as public or private key bugzilla@jessica.w3.org

Sunday, 20 July 2014

• V1.1 of MSR ECCLib for NUMS Curves library released (now supporting GCC on Linux) Brian LaMacchia

Friday, 18 July 2014

• Workshop item to be discussed 조상래
• Re: importKey doesn't seem to define handling of the keyData argument in some cases Boris Zbarsky

Thursday, 17 July 2014

• Re: importKey doesn't seem to define handling of the keyData argument in some cases Ryan Sleevi
• [Bug 26380] New: importKey doesn't define handling of keyData in some cases bugzilla@jessica.w3.org

Wednesday, 16 July 2014

• [Bug 26348] Allow JWK for PBKDF2 bugzilla@jessica.w3.org
• [Bug 26348] New: Allow JWK for PBKDF2 bugzilla@jessica.w3.org
• Re: importKey doesn't seem to define handling of the keyData argument in some cases Boris Zbarsky
• Re: importKey doesn't seem to define handling of the keyData argument in some cases Ryan Sleevi

Tuesday, 15 July 2014

• importKey doesn't seem to define handling of the keyData argument in some cases Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky

Monday, 14 July 2014

• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• [Bug 26331] New: Usage Intersection is defined as operating on arrays, rather than sequences bugzilla@jessica.w3.org
• How many curves should a UA support? Brian LaMacchia

Sunday, 13 July 2014

• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky
• [Bug 26322] New: Definitions "algorithm" and "usages" properties of CryptoKey make no sense bugzilla@jessica.w3.org
• Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Ryan Sleevi
• Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense Boris Zbarsky

Saturday, 12 July 2014

• [Bug 26080] Remove unsafe named curves from Web Crypto API bugzilla@jessica.w3.org
• [Bug 26320] New: RsaHashedKeyAlgorithm inherits from RsaKeyAlgorithm bugzilla@jessica.w3.org
• [Bug 25839] Curve25519 Named Curve bugzilla@jessica.w3.org
• [Bug 26080] Remove unsafe named curves from Web Crypto API bugzilla@jessica.w3.org
• RE: Changes required to add the NUMS curves to Web Cryptography API GALINDO Virginie
• [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
• Re: Changes required to add the NUMS curves to Web Cryptography API Ryan Sleevi
• [Bug 26315] New: ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous bugzilla@jessica.w3.org
• RE: Changes required to add the NUMS curves to Web Cryptography API Brian LaMacchia
• Re: Changes required to add the NUMS curves to Web Cryptography API Ryan Sleevi

Friday, 11 July 2014

• Changes required to add the NUMS curves to Web Cryptography API Brian LaMacchia
• [Bug 26311] New: Algorithm names should be enforced to be ASCII and normalized to lowercase bugzilla@jessica.w3.org

Thursday, 10 July 2014

• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky

Wednesday, 9 July 2014

• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• [Bug 26301] Normalization: Should through instead of returning an Error instance bugzilla@jessica.w3.org
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Richard Barnes
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• [Bug 26301] New: Normalization: Should through instead of returning an Error instance bugzilla@jessica.w3.org
• [Bug 26300] New: Normalization: "If alg is an IDL object" is confusing bugzilla@jessica.w3.org
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Richard Barnes
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Ryan Sleevi
• Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels Boris Zbarsky

Tuesday, 8 July 2014

• Re: Web Crypto API - about named curve addition Richard Barnes
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org

Monday, 7 July 2014

• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org
• [W3C Web Crypto WG] our next call on 28th of July @ 20:UTC (with some votes inside) GALINDO Virginie
• Re: RE : [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) Harry Halpin
• RE : [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) GALINDO Virginie
• [Bug 25985] WebCrypto should be inter-operable bugzilla@jessica.w3.org

Sunday, 6 July 2014

• RE: [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) Brian LaMacchia

Friday, 4 July 2014

• [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) GALINDO Virginie

Tuesday, 1 July 2014

• [Bug 25721] extractable keys should be disabled by default 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] 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

Last message date: Thursday, 31 July 2014 20:24:54 UTC