public-webcrypto@w3.org from August 2012 by author

Ali Asad

• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• RE: Proposed text to close ISSUE-13 (Wednesday, 29 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• RE: [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API (Wednesday, 29 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Tuesday, 28 August)
• RE: 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] (Tuesday, 28 August)
• RE: [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API (Tuesday, 28 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Tuesday, 28 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited (Monday, 27 August)
• [W3C Web Crypto WG] - Comments on Draft API v21 (Monday, 27 August)
• RE: [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 27 August)
• RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Monday, 27 August)
• RE: [W3C Web Crypto WG] next call on 4th of september ? please vote (Friday, 24 August)
• RE: New Editor's Draft published (Monday, 20 August)
• RE: Agenda for Monday Aug 13th meeting (today!) (Monday, 13 August)

Arun Ranganathan

• Re: New Editor's Draft (Tuesday, 28 August)
• Re: Use Cases | ACTION-13 Revisited (Monday, 27 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• Re: New Editor's Draft (Wednesday, 22 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Tuesday, 21 August)
• Re: Use Cases | ACTION-13 Revisited (Friday, 17 August)
• Use Cases | ACTION-13 Revisited (Thursday, 16 August)

Channy Yun

• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Sunday, 26 August)
• Re: suggest to move weekly concall time from UTC 19:00 to different time. (Sunday, 26 August)

Christopher Kula

• Re: [W3C Web Crypto WG] ACTION-29 : a possible test framework (Friday, 3 August)

Davenport, James L.

• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Monday, 27 August)
• RE: [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 27 August)
• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Monday, 27 August)
• Regrets (Monday, 6 August)

David Dahl

• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 27 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 20 August)
• Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Monday, 20 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Thursday, 9 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Wednesday, 8 August)

David McGrew (mcgrew)

• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Friday, 24 August)

GALINDO Virginie

• W3C Web Crypto WG - ACTION-20 closed (Friday, 31 August)
• W3C Web Crypto WG - ACTION-18 closed (Friday, 31 August)
• W3C Web Crypto WG - ACTION-9 closed (Friday, 31 August)
• W3C Web Crypto WG - ACTION-6 closed (Friday, 31 August)
• Web Crypto WG - ACTION-14 associated with ISSUE-37 (Friday, 31 August)
• W3C Web Crypto WG - ACTION-15 closed (Friday, 31 August)
• W3C Web Crypto WG - draft API v 1.25 has been published (Friday, 31 August)
• W3C Web Crypto WG - our next call is on 4th of Sept @ 19:00 UTC and will deal with FPWD (Wednesday, 29 August)
• Web Crypto WG - status on pending ISSUE-3 related to algo discovery ? (Monday, 27 August)
• Web Crypto WG - ISSUE-4 : algorithm Must versus Should - CLOSED (Monday, 27 August)
• crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API (Monday, 27 August)
• [Web Crypto WG] ACTION-39 : adding sample code in the draft API (Monday, 27 August)
• W3C Web Crypto WG - agenda for 27th of august call - today (Monday, 27 August)
• RE: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• W3C Web Crypto WG - call for WG participants to review the draft API before FPWD (Thursday, 23 August)
• [W3C Web Crypto WG] functional features list in draft API and issue tracker (Wednesday, 22 August)
• [W3C Web Crypto WG] functional features list in draft API and issue tracker (Tuesday, 21 August)
• [W3C Web Crypto WG] next call on 4th of september ? please vote (Tuesday, 21 August)
• [W3C Web Crypto WG] Take away from 20th of august call (Tuesday, 21 August)
• [W3C Web Crypto WG] draft minutes of our call - 20th of august (Monday, 20 August)
• [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 20 August)
• W3C Web Crypto WG - agenda for 20th of august call (Friday, 17 August)
• RE: Use Case: Cryptographic primitives can help check source integrity before executing Javascript code previously stored in local storage. (Friday, 17 August)
• RE: [W3C Web Crypto WG] preparing the FPWD - collecting comments (Friday, 17 August)
• [W3C Web Crypto WG] preparing the FPWD - collecting comments (Friday, 17 August)
• [W3C Web Crypto WG] action and issue update (Monday, 13 August)
• [W3C Web Crypto WG] action-16 related to key query mechanism (Monday, 13 August)
• [W3C Web Crypto WG] draft minutes of 13th of August call (Monday, 13 August)
• [W3C Web Crypto WG] how to scribe and other tips (Monday, 13 August)
• RE: Draft minutes from today's Web Crypto Telecon (Wednesday, 8 August)
• [W3C Web Crypto WG] agenda of 6th of August @ 19:00 UTC (Monday, 6 August)
• JavaScript-only test suite project - action-29 (Friday, 3 August)
• [W3C Web Crypto WG] ACTION-29 : a possible test framework (Friday, 3 August)

Harry Halpin

• Re: W3C Web Crypto WG - ACTION-35 closed (Friday, 31 August)
• W3C Web Crypto WG - ACTION-35 closed (Friday, 31 August)
• Note on process re closing ISSUES (Friday, 31 August)
• Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Tuesday, 28 August)
• Draft meeting minutes for August 27th (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Editorial comments on Web Crypto API (Monday, 27 August)
• Re: suggest to move weekly concall time from UTC 19:00 to different time. (Sunday, 26 August)
• Re: New Editor's Draft published (Monday, 20 August)
• ACTION-23: Find out status of getrandom in HTML5 (Monday, 20 August)
• Please attempt to close ACTIONs before the next meeting (Monday, 20 August)
• Process for going to FPWD: Review the spec! (Monday, 13 August)
• Agenda for Monday Aug 13th meeting (today!) (Monday, 13 August)
• Fwd: RE: JOSE WG request from W3C WebCrypto API (Monday, 13 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Thursday, 9 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Wednesday, 8 August)
• Draft minutes from today's Web Crypto Telecon (Monday, 6 August)
• JOSE WG request (Monday, 6 August)
• crypto-ISSUE-4: Some proposed text for the spec to close the issue (Monday, 6 August)
• Re: [W3C Web Crypto WG] ACTION-29 : a possible test framework (Friday, 3 August)

Håvard Molland

• Re: ACTION-23: Find out status of getrandom in HTML5 (Monday, 20 August)

Jarred Nicholls

• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Wednesday, 8 August)

John Bradley

• Re: JOSE WG request (Friday, 10 August)

Lu HongQian Karen

• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• [W3C Web Crypto WG] - Comments on Draft API v22 (Monday, 27 August)
• RE: [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 27 August)

Mark Watson

• Re: Use Cases | ACTION-13 Revisited (Thursday, 30 August)
• Re: Use Cases | ACTION-13 Revisited (Thursday, 30 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 28 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• ACTION-38: pre-shared keys (Monday, 27 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• ACTION-36: key exchange with DH (Monday, 27 August)
• Re: Use Cases | ACTION-13 Revisited (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Re: [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Explanation of deriveKey (was Re: ACTION-22: Key export) (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Monday, 20 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Monday, 20 August)
• Re: Origin-bound keys (Tuesday, 14 August)
• Re: Origin-bound keys (Tuesday, 14 August)
• Re: Origin-bound keys (Monday, 13 August)
• Re: Origin-bound keys (Friday, 10 August)
• Re: Origin-bound keys (Thursday, 9 August)
• Re: Origin-bound keys (Monday, 6 August)
• Re: Origin-bound keys (Monday, 6 August)
• Origin-bound keys (Monday, 6 August)

Mike Jones

• RE: Proposed text to close ISSUE-13 (Wednesday, 29 August)
• RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Friday, 17 August)
• RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Friday, 17 August)
• RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Friday, 17 August)
• RE: RE: JOSE WG request from W3C WebCrypto API (Thursday, 16 August)
• RE: RE: JOSE WG request from W3C WebCrypto API (Thursday, 16 August)
• RE: JOSE WG request (Monday, 13 August)

Mitch Zollinger

• Re: ISSUE-17: Key Attributes - Proposed resolution (Thursday, 30 August)
• Re: ACTION-22: Key export (Tuesday, 28 August)
• Re: ACTION-22: Key export (Sunday, 26 August)
• Re: ACTION-22: Key export (Saturday, 25 August)
• Re: ACTION-22: Key export (Wednesday, 22 August)
• Re: Support for generic authentication tokens (Tuesday, 21 August)
• Re: ACTION-22: Key export (Thursday, 16 August)
• Re: Support for generic authentication tokens (Wednesday, 15 August)
• Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Tuesday, 14 August)
• Re: ACTION-22: Key export (Tuesday, 14 August)
• Support for generic authentication tokens (Saturday, 11 August)

Mountie Lee

• Key Generation via CMP (Certificate Management Protocol) (Wednesday, 29 August)
• suggest to move weekly concall time from UTC 19:00 to different time. (Sunday, 26 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Friday, 24 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• origin bound key generation (Wednesday, 22 August)
• Re: [W3C Web Crypto WG] preparing the FPWD - collecting comments (Friday, 17 August)
• Re: [W3C Web Crypto WG] how to scribe and other tips (Tuesday, 14 August)
• Re: Draft minutes from today's Web Crypto Telecon (Thursday, 9 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Monday, 6 August)
• Re: Draft minutes from today's Web Crypto Telecon (Tuesday, 7 August)
• Re: Origin-bound keys (Tuesday, 7 August)

Nadim Kobeissi

• Re: Agenda for Monday Aug 13th meeting (today!) (Monday, 13 August)

Richard Barnes

• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)

Richard L. Barnes

• Re: JOSE WG request (Friday, 10 August)

Ryan Sleevi

• Support for ECB (Friday, 31 August)
• Re: ISSUE-17: Key Attributes - Proposed resolution (Friday, 31 August)
• New Editor's Draft Published (Friday, 31 August)
• Re: (Minor) New version published (Friday, 31 August)
• Re: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] (Friday, 31 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Friday, 31 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Friday, 31 August)
• Re: W3C Web Crypto WG - ACTION-35 closed (Friday, 31 August)
• Re: W3C Web Crypto WG - draft API v 1.25 has been published (Friday, 31 August)
• Closing ISSUE-16 (Thursday, 30 August)
• CLOSING ISSUE-20 (Thursday, 30 August)
• Re: Use Cases | ACTION-13 Revisited (Thursday, 30 August)
• Re: crypto-ISSUE-37: Method naming [Web Cryptography API] (Thursday, 30 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Proposed text to close ISSUE-13 (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: Key Generation via CMP (Certificate Management Protocol) (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-37: Method naming [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API (Wednesday, 29 August)
• Re: 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] (Tuesday, 28 August)
• Re: Editorial comments on Web Crypto API (Tuesday, 28 August)
• Re: (Minor) New version published (Tuesday, 28 August)
• Re: (Minor) New version published (Tuesday, 28 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• ISSUE-8: Clean key neutering (was Re: New Editor's Draft) (Tuesday, 28 August)
• Re: [W3C Web Crypto WG] - Comments on Draft API v22 (Tuesday, 28 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Tuesday, 28 August)
• ISSUE-17: Key Attributes - Proposed resolution (Tuesday, 28 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Tuesday, 28 August)
• Re: New Editor's Draft (Tuesday, 28 August)
• Re: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] (Tuesday, 28 August)
• Re: Recognized algorithm names for SHA-2 algorithms (Monday, 27 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Monday, 27 August)
• Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Monday, 27 August)
• Re: [W3C Web Crypto WG] - Comments on Draft API v21 (Monday, 27 August)
• Re: Web Crypto WG - status on pending ISSUE-3 related to algo discovery ? (Monday, 27 August)
• Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Monday, 27 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• Re: ACTION-38: pre-shared keys (Monday, 27 August)
• Re: Use Cases | ACTION-13 Revisited (Monday, 27 August)
• Re: Explanation of deriveKey (was Re: ACTION-22: Key export) (Monday, 27 August)
• Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Monday, 27 August)
• Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Monday, 27 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Monday, 27 August)
• Re: ACTION-22: Key export (Monday, 27 August)
• Re: ACTION-22: Key export (Saturday, 25 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Saturday, 25 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Friday, 24 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• (Minor) New version published (Wednesday, 22 August)
• ISSUE-26 (was Re: origin bound key generation) (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: ACTION-22: Key export (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: Recognized algorithm names for SHA-2 algorithms (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: [W3C Web Crypto WG] functional features list in draft API and issue tracker (Tuesday, 21 August)
• Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• Re: New Editor's Draft published (Monday, 20 August)
• Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Monday, 20 August)
• Re: crypto-ISSUE-23: Should CryptoOperations and/or Keys support Transferrable semantics? (Monday, 20 August)
• Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Monday, 20 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 20 August)
• New Editor's Draft published (Monday, 20 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Friday, 17 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Friday, 17 August)
• Re: New Editor's Draft (Friday, 17 August)
• Re: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Friday, 17 August)
• Re: Support for generic authentication tokens (Friday, 17 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Friday, 17 August)
• Re: Use Cases | ACTION-13 Revisited (Thursday, 16 August)
• Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Tuesday, 14 August)
• Re: Origin-bound keys (Monday, 13 August)
• Re: ACTION-22: Key export (Monday, 13 August)
• Re: Support for generic authentication tokens (Saturday, 11 August)
• Re: Origin-bound keys (Friday, 10 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Thursday, 9 August)
• Re: New Editor's Draft (Thursday, 9 August)
• Re: New Editor's Draft (Thursday, 9 August)
• Re: Origin-bound keys (Thursday, 9 August)
• Re: Origin-bound keys (Thursday, 9 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Wednesday, 8 August)
• Re: crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] (Monday, 6 August)
• Re: Origin-bound keys (Monday, 6 August)
• Re: Origin-bound keys (Monday, 6 August)
• New Editor's Draft (Monday, 6 August)
• Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-15: Discovering certificates associated with (private) keys [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Monday, 6 August)
• Re: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Monday, 6 August)
• [W3C Web Crypto WG] ACTION-29 : a possible test framework (Friday, 3 August)
• Re: crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token (Friday, 3 August)
• Re: crypto-ISSUE-8 (key neutering): Making sure we describe the clean key neutering [Web Cryptography API] (Wednesday, 1 August)

Seetharama Rao Durbha

• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Wednesday, 29 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• Re: [W3C Web Crypto WG] comments on draft API - section 4 (Monday, 27 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Friday, 24 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• Re: origin bound key generation (Wednesday, 22 August)
• regrets (Monday, 13 August)
• Re: Regrets (Monday, 6 August)
• Re: crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token (Friday, 3 August)

Vijay Bharadwaj

• RE: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• RE: (Minor) New version published (Tuesday, 28 August)
• RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 28 August)
• RE: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Tuesday, 28 August)
• RE: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Tuesday, 28 August)
• RE: ISSUE-17: Key Attributes - Proposed resolution (Tuesday, 28 August)
• RE: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] (Tuesday, 28 August)
• RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Tuesday, 28 August)
• RE: Explanation of deriveKey (was Re: ACTION-22: Key export) (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited (Tuesday, 28 August)
• RE: [W3C Web Crypto WG] comments on draft API - section 4 (Tuesday, 28 August)
• RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] (Tuesday, 28 August)
• RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 28 August)
• RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Tuesday, 28 August)
• RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Tuesday, 28 August)
• RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Monday, 27 August)
• RE: (Minor) New version published (Monday, 27 August)
• RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Monday, 27 August)
• RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Monday, 27 August)
• RE: Use Cases | ACTION-13 Revisited (Monday, 27 August)
• RE: ACTION-22: Key export (Thursday, 16 August)
• RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Tuesday, 14 August)
• RE: Origin-bound keys (Tuesday, 14 August)
• RE: ACTION-22: Key export (Tuesday, 14 August)
• RE: ACTION-22: Key export (Tuesday, 14 August)
• RE: Origin-bound keys (Tuesday, 14 August)
• RE: Support for generic authentication tokens (Tuesday, 14 August)
• RE: New Editor's Draft (Tuesday, 14 August)
• RE: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Tuesday, 14 August)
• RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Tuesday, 14 August)
• RE: crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] (Tuesday, 14 August)
• RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Tuesday, 14 August)
• RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Monday, 13 August)
• RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Monday, 13 August)
• ACTION-22: Key export (Monday, 13 August)

Wan-Teh Chang

• Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Friday, 31 August)
• Re: Closing ISSUE-16 (Friday, 31 August)
• Re: crypto-ISSUE-37: Method naming [Web Cryptography API] (Thursday, 30 August)
• Re: crypto-ISSUE-37: Method naming [Web Cryptography API] (Thursday, 30 August)
• Re: [W3C Web Crypto WG] - Comments on Draft API v22 (Thursday, 30 August)
• Re: Proposed text to close ISSUE-13 (Wednesday, 29 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Tuesday, 28 August)
• Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Tuesday, 28 August)
• Re: ACTION-38: pre-shared keys (Monday, 27 August)
• Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Monday, 27 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Saturday, 25 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Friday, 24 August)
• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Friday, 24 August)
• Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Friday, 24 August)
• Re: [W3C Web Crypto WG] next call on 4th of september ? please vote (Thursday, 23 August)
• Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Thursday, 23 August)
• Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Thursday, 23 August)
• Recognized algorithm names for SHA-2 algorithms (Wednesday, 22 August)
• Re: New Editor's Draft published (Wednesday, 22 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Tuesday, 21 August)
• Re: RE: JOSE WG request from W3C WebCrypto API (Thursday, 16 August)
• Re: crypto-ISSUE-4: Some proposed text for the spec to close the issue (Saturday, 11 August)
• Re: Support for generic authentication tokens (Saturday, 11 August)
• Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Wednesday, 8 August)

Web Cryptography Working Group Issue Tracker

• crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API] (Thursday, 30 August)
• crypto-ISSUE-37: Method naming [Web Cryptography API] (Wednesday, 29 August)
• crypto-ISSUE-36 (derivation): Semantics for key generation versus key derivation [Web Cryptography API] (Tuesday, 28 August)
• crypto-ISSUE-35 (wrapping): Handling of wrap/unwrap operations [Web Cryptography API] (Tuesday, 28 August)
• crypto-ISSUE-34 (certificate-format): Representation of certificates [Web Cryptography API] (Tuesday, 28 August)
• 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] (Tuesday, 28 August)
• 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] (Tuesday, 28 August)
• crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] (Monday, 27 August)
• crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] (Monday, 27 August)
• crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] (Wednesday, 22 August)
• crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] (Wednesday, 22 August)
• crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] (Wednesday, 22 August)
• crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] (Wednesday, 22 August)
• crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] (Tuesday, 21 August)
• crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] (Monday, 20 August)
• crypto-ISSUE-23: Should CryptoOperations and/or Keys support Transferrable semantics? (Monday, 20 August)
• crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] (Monday, 20 August)
• crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 20 August)
• 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] (Monday, 13 August)
• crypto-ISSUE-19 (origin-bound key): Does it make sense to have authorized-origin and specific-origin keys [Web Cryptography API] (Monday, 13 August)
• crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-15: Discovering certificates associated with (private) keys [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] (Monday, 6 August)
• crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token (Friday, 3 August)
• crypto-ISSUE-10 (pure js environment): Making sure our API is usable with pure js environement (Wednesday, 1 August)
• crypto-ISSUE-9 (user consent): what will be the mean to integrate in the API the fact that key usage may need user consent ? [Web Cryptography API] (Wednesday, 1 August)
• crypto-ISSUE-8 (key neutering): Making sure we describe the clean key neutering [Web Cryptography API] (Wednesday, 1 August)
• crypto-ISSUE-7 (high level API): Deciding if we integrate a high level API in our deliverable [Web Cryptography API] (Wednesday, 1 August)

Wendy Seltzer

• Re: [W3C Web Crypto WG] Take away from 20th of august call (Tuesday, 21 August)

Zooko Wilcox-OHearn

• Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] (Monday, 27 August)

Last message date: Friday, 31 August 2012 23:26:17 UTC