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

Friday, 31 August 2012

Support for ECB Ryan Sleevi
Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Wan-Teh Chang
Re: Closing ISSUE-16 Wan-Teh Chang
Re: ISSUE-17: Key Attributes - Proposed resolution Ryan Sleevi
New Editor's Draft Published Ryan Sleevi
Re: (Minor) New version published Ryan Sleevi
Re: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Ryan Sleevi
Re: W3C Web Crypto WG - ACTION-35 closed Harry Halpin
Re: W3C Web Crypto WG - ACTION-35 closed Ryan Sleevi
W3C Web Crypto WG - ACTION-35 closed Harry Halpin
W3C Web Crypto WG - ACTION-20 closed GALINDO Virginie
W3C Web Crypto WG - ACTION-18 closed GALINDO Virginie
W3C Web Crypto WG - ACTION-9 closed GALINDO Virginie
W3C Web Crypto WG - ACTION-6 closed GALINDO Virginie
Web Crypto WG - ACTION-14 associated with ISSUE-37 GALINDO Virginie
W3C Web Crypto WG - ACTION-15 closed GALINDO Virginie
Re: W3C Web Crypto WG - draft API v 1.25 has been published Ryan Sleevi
W3C Web Crypto WG - draft API v 1.25 has been published GALINDO Virginie
Note on process re closing ISSUES Harry Halpin

Thursday, 30 August 2012

crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Closing ISSUE-16 Ryan Sleevi
CLOSING ISSUE-20 Ryan Sleevi
Re: Use Cases | ACTION-13 Revisited Mark Watson
Re: Use Cases | ACTION-13 Revisited Ryan Sleevi
Re: Use Cases | ACTION-13 Revisited Mark Watson
Re: crypto-ISSUE-37: Method naming [Web Cryptography API] Wan-Teh Chang
Re: ISSUE-17: Key Attributes - Proposed resolution Mitch Zollinger
Re: crypto-ISSUE-37: Method naming [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-37: Method naming [Web Cryptography API] Wan-Teh Chang
Re: [W3C Web Crypto WG] - Comments on Draft API v22 Wan-Teh Chang

Wednesday, 29 August 2012

Tuesday, 28 August 2012

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] Ryan Sleevi
RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Ali Asad
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] Ali Asad
RE: [Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API Ali Asad
RE: Explanation of deriveKey (was Re: ACTION-22: Key export) Vijay Bharadwaj
RE: (Minor) New version published Vijay Bharadwaj
Re: Editorial comments on Web Crypto API Ryan Sleevi
Re: (Minor) New version published Ryan Sleevi
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Mark Watson
Re: (Minor) New version published Ryan Sleevi
crypto-ISSUE-36 (derivation): Semantics for key generation versus key derivation [Web Cryptography API] Web Cryptography Working Group Issue Tracker
crypto-ISSUE-35 (wrapping): Handling of wrap/unwrap operations [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Ryan Sleevi
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Wan-Teh Chang
RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Vijay Bharadwaj
ISSUE-8: Clean key neutering (was Re: New Editor's Draft) Ryan Sleevi
RE: Explanation of deriveKey (was Re: ACTION-22: Key export) Vijay Bharadwaj
crypto-ISSUE-34 (certificate-format): Representation of certificates [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: New Editor's Draft Arun Ranganathan
Re: [W3C Web Crypto WG] - Comments on Draft API v22 Ryan Sleevi
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] Web Cryptography Working Group Issue Tracker
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] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Wan-Teh Chang
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Davenport, James L.
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Mark Watson
Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] Harry Halpin
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Vijay Bharadwaj
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Davenport, James L.
RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Ali Asad
RE: Explanation of deriveKey (was Re: ACTION-22: Key export) Vijay Bharadwaj
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Mark Watson
RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Ali Asad
RE: ISSUE-17: Key Attributes - Proposed resolution Vijay Bharadwaj
RE: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Vijay Bharadwaj
RE: Explanation of deriveKey (was Re: ACTION-22: Key export) Vijay Bharadwaj
RE: Use Cases | ACTION-13 Revisited Vijay Bharadwaj
RE: [W3C Web Crypto WG] comments on draft API - section 4 Vijay Bharadwaj
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Vijay Bharadwaj
RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Vijay Bharadwaj
Re: ACTION-22: Key export Mitch Zollinger
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Ryan Sleevi
ISSUE-17: Key Attributes - Proposed resolution Ryan Sleevi
Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Ryan Sleevi
Re: New Editor's Draft Ryan Sleevi
Re: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] Ryan Sleevi

Monday, 27 August 2012

Re: Recognized algorithm names for SHA-2 algorithms Ryan Sleevi
crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Seetharama Rao Durbha
Re: ACTION-38: pre-shared keys Wan-Teh Chang
Re: [W3C Web Crypto WG] - Comments on Draft API v21 Ryan Sleevi
Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Wan-Teh Chang
Re: Web Crypto WG - status on pending ISSUE-3 related to algo discovery ? Ryan Sleevi
Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] Ryan Sleevi
Web Crypto WG - status on pending ISSUE-3 related to algo discovery ? GALINDO Virginie
Web Crypto WG - ISSUE-4 : algorithm Must versus Should - CLOSED GALINDO Virginie
Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Mark Watson
Re: ACTION-38: pre-shared keys Ryan Sleevi
crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] GALINDO Virginie
crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API] Web Cryptography Working Group Issue Tracker
ACTION-38: pre-shared keys Mark Watson
[Web Crypto WG] ACTION-40 : clarifying smart card usage in section 4 of the draft API GALINDO Virginie
[Web Crypto WG] ACTION-39 : adding sample code in the draft API GALINDO Virginie
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Mark Watson
[W3C Web Crypto WG] - Comments on Draft API v22 Lu HongQian Karen
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Zooko Wilcox-OHearn
ACTION-36: key exchange with DH Mark Watson
Re: Use Cases | ACTION-13 Revisited Mark Watson
Draft meeting minutes for August 27th Harry Halpin
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Harry Halpin
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson
RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Mike Jones
RE: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mike Jones
Re: [W3C Web Crypto WG] comments on draft API - section 4 Mark Watson
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Harry Halpin
Re: Use Cases | ACTION-13 Revisited Ryan Sleevi
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Davenport, James L.
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] David Dahl
RE: [W3C Web Crypto WG] comments on draft API - section 4 Lu HongQian Karen
Re: Explanation of deriveKey (was Re: ACTION-22: Key export) Ryan Sleevi
Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Wan-Teh Chang
RE: Use Cases | ACTION-13 Revisited Ali Asad
Re: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson
Re: Use Cases | ACTION-13 Revisited [and latest API draft comments] Ryan Sleevi
Explanation of deriveKey (was Re: ACTION-22: Key export) Mark Watson
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Ryan Sleevi
Editorial comments on Web Crypto API Harry Halpin
Re: ACTION-22: Key export Ryan Sleevi
[W3C Web Crypto WG] - Comments on Draft API v21 Ali Asad
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson
Re: [W3C Web Crypto WG] comments on draft API - section 4 Seetharama Rao Durbha
RE: [W3C Web Crypto WG] comments on draft API - section 4 Ali Asad
Re: Use Cases | ACTION-13 Revisited Arun Ranganathan
RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Ali Asad
RE: [W3C Web Crypto WG] comments on draft API - section 4 Davenport, James L.
W3C Web Crypto WG - agenda for 27th of august call - today GALINDO Virginie
RE: Use Cases | ACTION-13 Revisited [and latest API draft comments] Davenport, James L.
RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Vijay Bharadwaj
RE: (Minor) New version published Vijay Bharadwaj
RE: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Vijay Bharadwaj
RE: Use Cases | ACTION-13 Revisited Vijay Bharadwaj

Sunday, 26 August 2012

Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Channy Yun
Re: suggest to move weekly concall time from UTC 19:00 to different time. Channy Yun
Re: ACTION-22: Key export Mitch Zollinger
Re: suggest to move weekly concall time from UTC 19:00 to different time. Harry Halpin
suggest to move weekly concall time from UTC 19:00 to different time. Mountie Lee

Saturday, 25 August 2012

Re: ACTION-22: Key export Ryan Sleevi
Re: ACTION-22: Key export Mitch Zollinger
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Wan-Teh Chang

Friday, 24 August 2012

Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Wan-Teh Chang
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] David McGrew (mcgrew)
Re: [W3C Web Crypto WG] next call on 4th of september ? please vote Seetharama Rao Durbha
RE: [W3C Web Crypto WG] next call on 4th of september ? please vote Ali Asad
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Mountie Lee
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Wan-Teh Chang
Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Wan-Teh Chang

Thursday, 23 August 2012

Re: [W3C Web Crypto WG] next call on 4th of september ? please vote Richard Barnes
Re: [W3C Web Crypto WG] next call on 4th of september ? please vote Arun Ranganathan

Wednesday, 22 August 2012

Re: New Editor's Draft Arun Ranganathan

Thursday, 23 August 2012

Wednesday, 22 August 2012

Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Seetharama Rao Durbha
Re: crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Seetharama Rao Durbha
Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-29 (block modes): Handling of block encryption modes and padding [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] Mark Watson
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Ryan Sleevi
(Minor) New version published Ryan Sleevi
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Seetharama Rao Durbha
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Mark Watson
ISSUE-26 (was Re: origin bound key generation) Ryan Sleevi
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-28: Short-names for algorithms [Web Cryptography API] Web Cryptography Working Group Issue Tracker
crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] David Dahl
Re: origin bound key generation Seetharama Rao Durbha
crypto-ISSUE-26 (multi-origin access): Should key generation be allowed to specify multi-origin shared access [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: ACTION-22: Key export Ryan Sleevi
Re: origin bound key generation Ryan Sleevi
Re: origin bound key generation Seetharama Rao Durbha
[W3C Web Crypto WG] functional features list in draft API and issue tracker GALINDO Virginie
Re: ACTION-22: Key export Mitch Zollinger
Re: Recognized algorithm names for SHA-2 algorithms Ryan Sleevi
Recognized algorithm names for SHA-2 algorithms Wan-Teh Chang
Re: origin bound key generation Ryan Sleevi
Re: New Editor's Draft published Wan-Teh Chang
Re: origin bound key generation Mountie Lee
Re: origin bound key generation Ryan Sleevi
Re: origin bound key generation Mountie Lee
Re: origin bound key generation Ryan Sleevi
origin bound key generation Mountie Lee
Re: crypto-ISSUE-25 (Global Unique ID): How do we provision Global Unique ID for pre-provisionned symetric keys [Web Cryptography API] Mark Watson

Tuesday, 21 August 2012

Monday, 20 August 2012

[W3C Web Crypto WG] draft minutes of our call - 20th of august GALINDO Virginie
Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] Mark Watson
Re: New Editor's Draft published Ryan Sleevi
Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] Ryan Sleevi
RE: New Editor's Draft published Ali Asad
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] David Dahl
Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] David Dahl
Re: crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] Mark Watson
Re: New Editor's Draft published Harry Halpin
crypto-ISSUE-24: Defining a Synchronous API [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-23: Should CryptoOperations and/or Keys support Transferrable semantics? Ryan Sleevi
Re: crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Ryan Sleevi
New Editor's Draft published Ryan Sleevi
Re: ACTION-23: Find out status of getrandom in HTML5 Håvard Molland
crypto-ISSUE-23: Should CryptoOperations and/or Keys support Transferrable semantics? Web Cryptography Working Group Issue Tracker
crypto-ISSUE-22: Should CryptoOperations be clonable [Web Cryptography API] Web Cryptography Working Group Issue Tracker
crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API] Web Cryptography Working Group Issue Tracker
ACTION-23: Find out status of getrandom in HTML5 Harry Halpin
[W3C Web Crypto WG] comments on draft API - section 4 GALINDO Virginie
Please attempt to close ACTIONs before the next meeting Harry Halpin

Friday, 17 August 2012

Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Ryan Sleevi
RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Mike Jones
Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Ryan Sleevi
Re: New Editor's Draft Ryan Sleevi
Re: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Ryan Sleevi
RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Mike Jones
RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Mike Jones
Re: Support for generic authentication tokens Ryan Sleevi
W3C Web Crypto WG - agenda for 20th of august call GALINDO Virginie
Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Ryan Sleevi
Re: Use Cases | ACTION-13 Revisited Arun Ranganathan
RE: Use Case: Cryptographic primitives can help check source integrity before executing Javascript code previously stored in local storage. GALINDO Virginie
RE: [W3C Web Crypto WG] preparing the FPWD - collecting comments GALINDO Virginie
Re: [W3C Web Crypto WG] preparing the FPWD - collecting comments Mountie Lee
[W3C Web Crypto WG] preparing the FPWD - collecting comments GALINDO Virginie

Thursday, 16 August 2012

Re: Use Cases | ACTION-13 Revisited Ryan Sleevi
Use Cases | ACTION-13 Revisited Arun Ranganathan
RE: ACTION-22: Key export Vijay Bharadwaj
RE: RE: JOSE WG request from W3C WebCrypto API Mike Jones
Re: ACTION-22: Key export Mitch Zollinger
Re: RE: JOSE WG request from W3C WebCrypto API Wan-Teh Chang
RE: RE: JOSE WG request from W3C WebCrypto API Mike Jones

Wednesday, 15 August 2012

Re: Support for generic authentication tokens Mitch Zollinger

Tuesday, 14 August 2012

Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Ryan Sleevi
RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Vijay Bharadwaj
RE: Origin-bound keys Vijay Bharadwaj
Re: Origin-bound keys Mark Watson
RE: ACTION-22: Key export Vijay Bharadwaj
RE: ACTION-22: Key export Vijay Bharadwaj
RE: Origin-bound keys Vijay Bharadwaj
RE: Support for generic authentication tokens Vijay Bharadwaj
RE: New Editor's Draft Vijay Bharadwaj
RE: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Vijay Bharadwaj
Re: [W3C Web Crypto WG] how to scribe and other tips Mountie Lee
Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Mitch Zollinger
Re: ACTION-22: Key export Mitch Zollinger
Re: Origin-bound keys Mark Watson

Monday, 13 August 2012

Re: Origin-bound keys Ryan Sleevi
Re: Origin-bound keys Mark Watson
Re: ACTION-22: Key export Ryan Sleevi
[W3C Web Crypto WG] action and issue update GALINDO Virginie
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] Web Cryptography Working Group Issue Tracker
RE: JOSE WG request Mike Jones
[W3C Web Crypto WG] action-16 related to key query mechanism GALINDO Virginie
[W3C Web Crypto WG] draft minutes of 13th of August call GALINDO Virginie
[W3C Web Crypto WG] how to scribe and other tips GALINDO Virginie
regrets Seetharama Rao Durbha
Process for going to FPWD: Review the spec! Harry Halpin
Re: Agenda for Monday Aug 13th meeting (today!) Nadim Kobeissi
RE: Agenda for Monday Aug 13th meeting (today!) Ali Asad
Agenda for Monday Aug 13th meeting (today!) Harry Halpin
Fwd: RE: JOSE WG request from W3C WebCrypto API Harry Halpin
RE: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Vijay Bharadwaj
RE: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Vijay Bharadwaj
ACTION-22: Key export Vijay Bharadwaj
crypto-ISSUE-19 (origin-bound key): Does it make sense to have authorized-origin and specific-origin keys [Web Cryptography API] Web Cryptography Working Group Issue Tracker

Saturday, 11 August 2012

Re: crypto-ISSUE-4: Some proposed text for the spec to close the issue Wan-Teh Chang
Re: Support for generic authentication tokens Wan-Teh Chang
Re: Support for generic authentication tokens Ryan Sleevi
Support for generic authentication tokens Mitch Zollinger

Friday, 10 August 2012

Re: JOSE WG request John Bradley
Re: JOSE WG request Richard L. Barnes
Re: Origin-bound keys Mark Watson
Re: Origin-bound keys Ryan Sleevi

Thursday, 9 August 2012

Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Harry Halpin
Re: Origin-bound keys Mark Watson
Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] David Dahl
Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Ryan Sleevi
Re: New Editor's Draft Ryan Sleevi
Re: New Editor's Draft Ryan Sleevi
Re: Origin-bound keys Ryan Sleevi
Re: Origin-bound keys Ryan Sleevi
Re: Draft minutes from today's Web Crypto Telecon Mountie Lee

Wednesday, 8 August 2012

RE: Draft minutes from today's Web Crypto Telecon GALINDO Virginie

Monday, 6 August 2012

Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Mountie Lee

Tuesday, 7 August 2012

Re: Draft minutes from today's Web Crypto Telecon Mountie Lee
Re: Origin-bound keys Mountie Lee

Wednesday, 8 August 2012

Monday, 6 August 2012

Draft minutes from today's Web Crypto Telecon Harry Halpin
JOSE WG request Harry Halpin
Re: Origin-bound keys Mark Watson
crypto-ISSUE-4: Some proposed text for the spec to close the issue Harry Halpin
Re: crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] Ryan Sleevi
Re: Origin-bound keys Ryan Sleevi
crypto-ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: Origin-bound keys Mark Watson
Re: Origin-bound keys Ryan Sleevi
Origin-bound keys Mark Watson
Re: Regrets Seetharama Rao Durbha
[W3C Web Crypto WG] agenda of 6th of August @ 19:00 UTC GALINDO Virginie
Regrets Davenport, James L.
New Editor's Draft Ryan Sleevi
Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Ryan Sleevi
Re: crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-16: Definition for Key Expiration [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-15: Discovering certificates associated with (private) keys [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-15: Discovering certificates associated with (private) keys [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-14: Representation of raw key material [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-13: Relationship between the W3C Web Cryptography work product and the IETF JOSE WG [Web Cryptography API] Web Cryptography Working Group Issue Tracker
Re: crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-12: Should the API distinguish between algorithm and operation parameters? [Web Cryptography API] Web Cryptography Working Group Issue Tracker

Friday, 3 August 2012

[W3C Web Crypto WG] ACTION-29 : a possible test framework Ryan Sleevi
Re: [W3C Web Crypto WG] ACTION-29 : a possible test framework Harry Halpin
Re: crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token Ryan Sleevi
Re: [W3C Web Crypto WG] ACTION-29 : a possible test framework Christopher Kula
Re: crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token Seetharama Rao Durbha
crypto-ISSUE-11 (storage attribute): Is there a need for a storage attribute, indicating storage in a hardware token Web Cryptography Working Group Issue Tracker
JavaScript-only test suite project - action-29 GALINDO Virginie
[W3C Web Crypto WG] ACTION-29 : a possible test framework GALINDO Virginie

Wednesday, 1 August 2012

Re: crypto-ISSUE-8 (key neutering): Making sure we describe the clean key neutering [Web Cryptography API] Ryan Sleevi
crypto-ISSUE-10 (pure js environment): Making sure our API is usable with pure js environement Web Cryptography Working Group Issue Tracker
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] Web Cryptography Working Group Issue Tracker
crypto-ISSUE-8 (key neutering): Making sure we describe the clean key neutering [Web Cryptography API] Web Cryptography Working Group Issue Tracker
crypto-ISSUE-7 (high level API): Deciding if we integrate a high level API in our deliverable [Web Cryptography API] Web Cryptography Working Group Issue Tracker

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