Boris Zbarsky
- Re: importKey doesn't seem to define handling of the keyData argument in some cases (Friday, 18 July)
- Re: importKey doesn't seem to define handling of the keyData argument in some cases (Wednesday, 16 July)
- importKey doesn't seem to define handling of the keyData argument in some cases (Tuesday, 15 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Tuesday, 15 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Tuesday, 15 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Sunday, 13 July)
- Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Sunday, 13 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Thursday, 10 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Thursday, 10 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
Brian LaMacchia
bugzilla@jessica.w3.org
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Thursday, 31 July)
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Thursday, 31 July)
- [Bug 25985] WebCrypto should be inter-operable (Thursday, 31 July)
- [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase (Thursday, 31 July)
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Thursday, 31 July)
- [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase (Thursday, 31 July)
- [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase (Thursday, 31 July)
- [Bug 25985] WebCrypto should be inter-operable (Thursday, 31 July)
- [Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase (Thursday, 31 July)
- [Bug 25985] WebCrypto should be inter-operable (Thursday, 31 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Wednesday, 30 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Wednesday, 30 July)
- [Bug 25985] WebCrypto should be inter-operable (Wednesday, 30 July)
- [Bug 25985] WebCrypto should be inter-operable (Wednesday, 30 July)
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Wednesday, 30 July)
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Wednesday, 30 July)
- [Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Wednesday, 30 July)
- [Bug 26465] New: Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields (Wednesday, 30 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Wednesday, 30 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Wednesday, 30 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Wednesday, 30 July)
- [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 26458] New: Are all the API methods really returning Promise<any>, or can the return value be specified more precisely? (Tuesday, 29 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25607] Need to advise authors about security considerations (Monday, 28 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Monday, 28 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Monday, 28 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Monday, 28 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25607] Need to advise authors about security considerations (Monday, 28 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Monday, 28 July)
- [Bug 25721] extractable keys should be disabled by default (Monday, 28 July)
- [Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec (Monday, 28 July)
- [Bug 25607] Need to advise authors about security considerations (Monday, 28 July)
- [Bug 25607] Need to advise authors about security considerations (Monday, 28 July)
- [Bug 25985] WebCrypto should be inter-operable (Sunday, 27 July)
- [Bug 25839] Curve25519 Named Curve (Sunday, 27 July)
- [Bug 25839] Curve25519 Named Curve (Saturday, 26 July)
- [Bug 25839] Curve25519 Named Curve (Saturday, 26 July)
- [Bug 25985] WebCrypto should be inter-operable (Friday, 25 July)
- [Bug 25839] Curve25519 Named Curve (Friday, 25 July)
- [Bug 25839] Curve25519 Named Curve (Friday, 25 July)
- [Bug 25839] Curve25519 Named Curve (Friday, 25 July)
- [Bug 25839] Curve25519 Named Curve (Thursday, 24 July)
- [Bug 25607] Need to advise authors about security considerations (Thursday, 24 July)
- [Bug 25839] Curve25519 Named Curve (Thursday, 24 July)
- [Bug 25839] Curve25519 Named Curve (Thursday, 24 July)
- [Bug 25839] Curve25519 Named Curve (Wednesday, 23 July)
- [Bug 25839] Curve25519 Named Curve (Wednesday, 23 July)
- [Bug 25839] Curve25519 Named Curve (Wednesday, 23 July)
- [Bug 25815] Spec encourages unsafe handling of secret data for JWK import of RSA/ECC keys (Wednesday, 23 July)
- [Bug 26411] Caller can't force JWK to be distinguished as public or private key (Wednesday, 23 July)
- [Bug 26411] Caller can't force JWK to be distinguished as public or private key (Tuesday, 22 July)
- [Bug 26413] New: Inconsistent handling of usages parameter between importKey and generateKey (Tuesday, 22 July)
- [Bug 26412] New: Asymmetric algorithms do not specify how to compute usages/extractability during importKey (Tuesday, 22 July)
- [Bug 26411] Caller can't force JWK to be distinguished as public or private key (Tuesday, 22 July)
- [Bug 26411] New: Caller can't force JWK to be distinguished as public or private key (Tuesday, 22 July)
- [Bug 26380] New: importKey doesn't define handling of keyData in some cases (Thursday, 17 July)
- [Bug 26348] Allow JWK for PBKDF2 (Wednesday, 16 July)
- [Bug 26348] New: Allow JWK for PBKDF2 (Wednesday, 16 July)
- [Bug 26331] New: Usage Intersection is defined as operating on arrays, rather than sequences (Monday, 14 July)
- [Bug 26322] New: Definitions "algorithm" and "usages" properties of CryptoKey make no sense (Sunday, 13 July)
- [Bug 26080] Remove unsafe named curves from Web Crypto API (Saturday, 12 July)
- [Bug 26320] New: RsaHashedKeyAlgorithm inherits from RsaKeyAlgorithm (Saturday, 12 July)
- [Bug 25839] Curve25519 Named Curve (Saturday, 12 July)
- [Bug 26080] Remove unsafe named curves from Web Crypto API (Saturday, 12 July)
- [Bug 25607] Need to advise authors about security considerations (Saturday, 12 July)
- [Bug 25607] Need to advise authors about security considerations (Saturday, 12 July)
- [Bug 26315] New: ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous (Saturday, 12 July)
- [Bug 26311] New: Algorithm names should be enforced to be ASCII and normalized to lowercase (Friday, 11 July)
- [Bug 25985] WebCrypto should be inter-operable (Wednesday, 9 July)
- [Bug 26301] Normalization: Should through instead of returning an Error instance (Wednesday, 9 July)
- [Bug 26301] New: Normalization: Should through instead of returning an Error instance (Wednesday, 9 July)
- [Bug 26300] New: Normalization: "If alg is an IDL object" is confusing (Wednesday, 9 July)
- [Bug 25985] WebCrypto should be inter-operable (Tuesday, 8 July)
- [Bug 25985] WebCrypto should be inter-operable (Monday, 7 July)
- [Bug 25985] WebCrypto should be inter-operable (Monday, 7 July)
- [Bug 25721] extractable keys should be disabled by default (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
- [Bug 25607] Need to advise authors about security considerations (Tuesday, 1 July)
GALINDO Virginie
- [W3C Web Crypto WG] suggested resolution for NUMS curves, as part of the bug 25839 related to curve25519 (Saturday, 26 July)
- [W3C Web Crypto WG] Call for contributors on curve 25519 extension (Saturday, 26 July)
- Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Saturday, 26 July)
- RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Saturday, 26 July)
- Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Friday, 25 July)
- [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Friday, 25 July)
- [W3C Web Crypto WG] suggested resolution for bug 25985 on browser interoperability (Friday, 25 July)
- RE: [W3C Web Crypto WG] suggested resolution for bug 26080 on removing non-NIST algo (Friday, 25 July)
- [W3C Web Crypto WG] suggested resolution for bug 25607 related to security recommendation (Friday, 25 July)
- [W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside (Friday, 25 July)
- RE: [Cfrg] CFRG@IETF90 summary (Thursday, 24 July)
- [W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside (Thursday, 24 July)
- RE: Changes required to add the NUMS curves to Web Cryptography API (Saturday, 12 July)
- [W3C Web Crypto WG] our next call on 28th of July @ 20:UTC (with some votes inside) (Monday, 7 July)
- RE : [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) (Monday, 7 July)
- [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside) (Friday, 4 July)
Harry Halpin
Mike Jones
Richard Barnes
Ryan Sleevi
- Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Monday, 28 July)
- Re: [W3C Web Crypto WG] Call for contributors on curve 25519 extension (Monday, 28 July)
- RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Friday, 25 July)
- Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Friday, 25 July)
- Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519 (Friday, 25 July)
- Re: importKey doesn't seem to define handling of the keyData argument in some cases (Thursday, 17 July)
- Re: importKey doesn't seem to define handling of the keyData argument in some cases (Wednesday, 16 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Tuesday, 15 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Tuesday, 15 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Monday, 14 July)
- Re: Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense (Sunday, 13 July)
- Re: Changes required to add the NUMS curves to Web Cryptography API (Saturday, 12 July)
- Re: Changes required to add the NUMS curves to Web Cryptography API (Saturday, 12 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Thursday, 10 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
- Re: Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels (Wednesday, 9 July)
Wendy Seltzer
์กฐ์๋
Last message date: Thursday, 31 July 2014 20:24:54 UTC