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

[Bug 25607] Need to advise authors about security considerations

[Bug 25618] Extensibility: Offer spec-blessed ways to extend the algorithms and curves, rather than monkey-patching the spec

[Bug 25721] extractable keys should be disabled by default

[Bug 25815] Spec encourages unsafe handling of secret data for JWK import of RSA/ECC keys

[Bug 25839] Curve25519 Named Curve

[Bug 25985] WebCrypto should be inter-operable

[Bug 26080] Remove unsafe named curves from Web Crypto API

[Bug 26300] New: Normalization: "If alg is an IDL object" is confusing

[Bug 26301] New: Normalization: Should through instead of returning an Error instance

[Bug 26301] Normalization: Should through instead of returning an Error instance

[Bug 26311] Algorithm names should be enforced to be ASCII and normalized to lowercase

[Bug 26311] New: Algorithm names should be enforced to be ASCII and normalized to lowercase

[Bug 26315] New: ECDSA/ECDH: "namedCurve ASN.1 type" is ambiguous

[Bug 26320] New: RsaHashedKeyAlgorithm inherits from RsaKeyAlgorithm

[Bug 26322] New: Definitions "algorithm" and "usages" properties of CryptoKey make no sense

[Bug 26331] New: Usage Intersection is defined as operating on arrays, rather than sequences

[Bug 26348] Allow JWK for PBKDF2

[Bug 26348] New: Allow JWK for PBKDF2

[Bug 26380] New: importKey doesn't define handling of keyData in some cases

[Bug 26411] Caller can't force JWK to be distinguished as public or private key

[Bug 26411] New: Caller can't force JWK to be distinguished as public or private key

[Bug 26412] New: Asymmetric algorithms do not specify how to compute usages/extractability during importKey

[Bug 26413] New: Inconsistent handling of usages parameter between importKey and generateKey

[Bug 26458] Are all the API methods really returning Promise<any>, or can the return value be specified more precisely?

[Bug 26458] New: Are all the API methods really returning Promise<any>, or can the return value be specified more precisely?

[Bug 26465] Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields

[Bug 26465] New: Algorithm normalization doesn't allow arbitrary operations for AlgorithmIdentifier fields

[Cfrg] CFRG@IETF90 summary

[W3C Web Crypto WG] Call for contributors on curve 25519 extension

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

[W3C Web Crypto WG] our next call on 28th of July @ 20:UTC (with some votes inside)

[W3C Web Crypto WG] suggested resolution for bug 25607 related to security recommendation

[W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519

[W3C Web Crypto WG] suggested resolution for bug 25985 on browser interoperability

[W3C Web Crypto WG] suggested resolution for bug 26080 on removing non-NIST algo

[W3C Web Crypto WG] suggested resolution for NUMS curves, as part of the bug 25839 related to curve25519

[W3C Web Crypto WG] WG call next monday @ 20:00 UTC - with bug resolutions and votes inside

Changes required to add the NUMS curves to Web Cryptography API

Draft minutes from [W3C Web Crypto WG] 28 July call

Fwd: [Cfrg] CFRG@IETF90 summary

How many curves should a UA support?

importKey doesn't seem to define handling of the keyData argument in some cases

Meeting minutes for July 28th meeting

Next call August 11th: Dedicated to extension and ECC Curves

Next WebCrypto call: Monday August 11, 20 UTC

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

Spec for CryptoKey.algorithm and CryptoKey.usages doesn't really make sense

Spec for RSA-OAEP doesn't say what to do for null or missing or array buffer view labels

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

Web Crypto API - about named curve addition

Workshop item to be discussed

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