Support for ECB
New Editor's Draft Published
W3C Web Crypto WG - ACTION-35 closed
W3C Web Crypto WG - ACTION-20 closed
W3C Web Crypto WG - ACTION-18 closed
W3C Web Crypto WG - ACTION-9 closed
W3C Web Crypto WG - ACTION-6 closed
Web Crypto WG - ACTION-14 associated with ISSUE-37
W3C Web Crypto WG - ACTION-15 closed
W3C Web Crypto WG - draft API v 1.25 has been published
Note on process re closing ISSUES
crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
Closing ISSUE-16
CLOSING ISSUE-20
Proposed text to close ISSUE-13
Key Generation via CMP (Certificate Management Protocol)
W3C Web Crypto WG - our next call is on 4th of Sept @ 19:00 UTC and will deal with FPWD
crypto-ISSUE-37: Method naming [Web Cryptography API]
crypto-ISSUE-36 (derivation): Semantics for key generation versus key derivation [Web Cryptography API]
crypto-ISSUE-35 (wrapping): Handling of wrap/unwrap operations [Web Cryptography API]
ISSUE-8: Clean key neutering (was Re: New Editor's Draft)
crypto-ISSUE-34 (certificate-format): Representation of certificates [Web Cryptography API]
crypto-ISSUE-33 (Clarify key tainting): Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario [Web Cryptography API]
crypto-ISSUE-32 (Key security): Section 5.2 in API draft should mention use of secure element in the context of key security [Web Cryptography API]
ISSUE-17: Key Attributes - Proposed resolution
- RE: ISSUE-17: Key Attributes - Proposed resolution
- Re: ISSUE-17: Key Attributes - Proposed resolution
crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API]
Web Crypto WG - status on pending ISSUE-3 related to algo discovery ?
Web Crypto WG - ISSUE-4 : algorithm Must versus Should - CLOSED
crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
ACTION-38: pre-shared keys
[Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API
[Web Crypto WG] ACTION-39 : adding sample code in the draft API
[W3C Web Crypto WG] - Comments on Draft API v22
ACTION-36: key exchange with DH
Draft meeting minutes for August 27th
Editorial comments on Web Crypto API
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments]
- Re: Use Cases | ACTION-13 Revisited [and latest API draft comments]
- RE: Use Cases | ACTION-13 Revisited [and latest API draft comments]
- RE: Use Cases | ACTION-13 Revisited [and latest API draft comments]
- RE: Use Cases | ACTION-13 Revisited [and latest API draft comments]
suggest to move weekly concall time from UTC 19:00 to different time.
W3C Web Crypto WG - call for WG participants to review the draft API before FPWD
crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
- Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API]
(Minor) New version published
ISSUE-26 (was Re: origin bound key generation)
crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API]
crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API]
- RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API]
- Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API]
crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
- Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API]
Recognized algorithm names for SHA-2 algorithms
origin bound key generation
[W3C Web Crypto WG] functional features list in draft API and issue tracker
[W3C Web Crypto WG] Take away from 20th of august call
- Re: [W3C Web Crypto WG] Take away from 20th of august call
- [W3C Web Crypto WG] next call on 4th of september ? please vote
crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
- Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API]
[W3C Web Crypto WG] draft minutes of our call - 20th of august
crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API]
- Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API]
New Editor's Draft published
crypto-ISSUE-23: Should CryptoOperations and/or Keys support Transferrable semantics?
crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API]
- Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API]
crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- RE: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
ACTION-23: Find out status of getrandom in HTML5
[W3C Web Crypto WG] comments on draft API - section 4
Please attempt to close ACTIONs before the next meeting
W3C Web Crypto WG - agenda for 20th of august call
RE: Use Case: Cryptographic primitives can help check source integrity before executing Javascript code previously stored in local storage.
[W3C Web Crypto WG] preparing the FPWD - collecting comments
Use Cases | ACTION-13 Revisited
- Re: Use Cases | ACTION-13 Revisited
crypto-ISSUE-20 (key and attribute storage): What are the requirements and the possible technical solution(s) to control the storage of key and associated attributes [Web Cryptography API]
[W3C Web Crypto WG] action-16 related to key query mechanism
[W3C Web Crypto WG] draft minutes of 13th of August call
[W3C Web Crypto WG] how to scribe and other tips
regrets
Process for going to FPWD: Review the spec!
Agenda for Monday Aug 13th meeting (today!)
Fwd: RE: JOSE WG request from W3C WebCrypto API
ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- RE: ACTION-22: Key export
- Re: ACTION-22: Key export
- RE: ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- RE: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- RE: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- RE: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: Explanation of deriveKey (was Re: ACTION-22: Key export)
- RE: Explanation of deriveKey (was Re: ACTION-22: Key export)
- Re: ACTION-22: Key export
- Re: ACTION-22: Key export
- RE: ACTION-22: Key export
- Re: ACTION-22: Key export
- RE: ACTION-22: Key export
- Re: ACTION-22: Key export
crypto-ISSUE-19 (origin-bound key): Does it make sense to have authorized-origin and specific-origin keys [Web Cryptography API]
Support for generic authentication tokens
Draft minutes from today's Web Crypto Telecon
JOSE WG request
crypto-ISSUE-4: Some proposed text for the spec to close the issue
crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API]
Origin-bound keys
[W3C Web Crypto WG] agenda of 6th of August @ 19:00 UTC
Regrets
New Editor's Draft
crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API]
- Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API]
- Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API]
- Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API]
crypto-ISSUE-15: Discovering certificates associated with (private) keys [Web Cryptography API]
crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
- RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API]
crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
- Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API]
crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API]
- Re: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API]