public-webcrypto@w3.org from April 2013 by author

Acar, Tolga

• RE: Named key discovery questions (Thursday, 25 April)
• RE: Defaults: Getting concrete (round 2) (Monday, 22 April)
• RE: Separate method for key agreement? (Tuesday, 2 April)
• RE: Potential contradiction in HKDF? (Monday, 1 April)

Alex Russell

• Re: Updated spec examples with Futures (Saturday, 27 April)
• Updated spec examples with Futures (Thursday, 25 April)
• Re: On a Futures-style API (Wednesday, 24 April)

Arun Ranganathan

• Fwd: some input on API (Saturday, 13 April)
• Re: Web Cryptography Use Cases For Review (Wednesday, 3 April)
• Re: On Crypto API Safety in the Hands of Unskilled Developers (Wednesday, 3 April)
• Re: Socializing the high level API during our F2F meeting in April (Wednesday, 3 April)

Aymeric Vitte

• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Monday, 29 April)
• Re: Updated spec examples with Futures (Saturday, 27 April)
• Re: Updated spec examples with Futures (Saturday, 27 April)
• Re: Updated spec examples with Futures (Friday, 26 April)
• Re: Updated spec examples with Futures (Thursday, 25 April)
• Re: On a Futures-style API (Wednesday, 24 April)
• Re: On a Futures-style API (Tuesday, 23 April)
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Tuesday, 23 April)
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Tuesday, 23 April)
• Re: [W3C WebCrypto API WG] Key discovery (Wednesday, 10 April)
• Re: WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. (Monday, 8 April)
• WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. (Monday, 8 April)
• Re: [W3C WebCrypto API WG] Key discovery (Monday, 8 April)
• Re: [W3C WebCrypto API WG] Key discovery (Monday, 8 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)

David Dahl

• Re: Socializing the high level API during our F2F meeting in April (Wednesday, 3 April)
• Re: On Crypto API Safety in the Hands of Unskilled Developers (Tuesday, 2 April)

GALINDO Virginie

• W3C Web Crypto WG - discussing the web security model (Tuesday, 30 April)
• W3C Web Crypto WG - Take away from San Jose F2F meeting - april 2012 (Tuesday, 30 April)
• W3C Web Crypto WG - regular call (WG participants only) (Friday, 26 April)
• W3C Web Crypto WG - Our next conference calls - correct dates, forget previous mail (Friday, 26 April)
• W3C Web Crypto WG - Our next conference calls (Friday, 26 April)
• W3C Web Crypto F2F April meeting - minutes (Wednesday, 24 April)
• W3C Web Crypto WG - Wednesday afternoon agenda (Wednesday, 24 April)
• W3C Web Crypto WG - wednesday 25th of April agenda update - starting at 8:30 (Wednesday, 24 April)
• RE: W3C Web Crypto WG - wednesday 25th of April agenda update (Wednesday, 24 April)
• W3C Web Crypto WG - wednesday 25th of April agenda update (Wednesday, 24 April)
• RE: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week (Monday, 22 April)
• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week (Sunday, 21 April)
• W3C Web Crypto WG - location and agenda of our F2F meeting next week (Saturday, 20 April)
• W3C Web Crypto WG - reception on wednesday 24th of April in Paypal from 5 to 7 PM (Saturday, 20 April)
• W3C Web Crypto WG - agenda for our F2F meeting (Sunday, 14 April)
• W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC (Friday, 12 April)
• [W3C Web Crypto WG] testing activities (Friday, 12 April)
• TPAC2013 in Shenzhen, China, 11-15 November 2013 - book your week ! (Friday, 12 April)
• RE: Session with WebAppSec WG in San Jose ? (Friday, 12 April)
• RE: Socializing the high level API during our F2F meeting in April (Friday, 12 April)
• RE: Socializing the high level API during our F2F meeting in April (Monday, 8 April)
• [W3C Web Crypto WG] About import/export (Thursday, 4 April)
• [W3C Web Crypto API] PROPOSAL : closing ISSUE-32 (API should mention the use of secure elements in the context of key security) (Thursday, 4 April)
• [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• [W3C Web Crypto WG] PROPOSAL: Close ISSUE-17 (Define the scope and API for custom key attributes) (Thursday, 4 April)
• [W3C Web Crypto WG] Proposal to close ISSUE-7 (Thursday, 4 April)
• Session with WebAppSec WG in San Jose ? (Thursday, 4 April)
• W3C Web Crypto WG - draft minutes of our call 1st of April 2013 (Tuesday, 2 April)
• Socializing the high level API during our F2F meeting in April (Tuesday, 2 April)
• W3C Web Crypto WG - regular meeting (Monday, 1 April)

Harry Halpin

• Testing infrastruture docs and links (Wednesday, 24 April)
• Minutes of our April 15th 2013 telecon (Monday, 15 April)
• Re: Socializing the high level API during our F2F meeting in April (Monday, 8 April)
• Re: Socializing the high level API during our F2F meeting in April (Thursday, 4 April)
• Re: [W3C Web Crypto WG] Proposal to close ISSUE-7 (Thursday, 4 April)
• Fwd: [jose] jose interim meeting planned (advance announcement) (Monday, 1 April)

Hutchinson Michael

• RE: Named key discovery questions (Thursday, 25 April)
• RE: UA interop (Thursday, 25 April)
• RE: UA interop (Thursday, 25 April)
• UA interop (Thursday, 25 April)
• RE: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• RE: Named key discovery questions (Thursday, 25 April)
• RE: [W3C WebCrypto API WG] Key discovery (Saturday, 6 April)
• RE: [W3C WebCrypto API WG] Key discovery (Friday, 5 April)

Ian Jacobs

• Call for Exclusions (Update): WebCrypto Key Discovery (Thursday, 11 April)

Israel Hilerio

• RE: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Saturday, 27 April)
• Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Tuesday, 23 April)

Jim Schaad

• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week (Saturday, 20 April)
• RE: GCM ciphertext + tag ambiguity (Thursday, 18 April)

Lu HongQian Karen

• [W3C WebCrypto API WG] Key discovery (Thursday, 4 April)

Mark Watson

• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Saturday, 27 April)
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Saturday, 27 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: Use case: Authenticate using eID (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Named key discovery questions (Thursday, 25 April)
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (Monday, 22 April)
• PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (Monday, 22 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Monday, 15 April)
• Re: [W3C WebCrypto API WG] Key discovery (Friday, 5 April)
• Re: [W3C Web Crypto WG] About import/export (Thursday, 4 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) (Thursday, 4 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• Re: [Moderator Action] Missing items in KeyUsage (Monday, 1 April)
• Re: Separate method for key agreement? (Monday, 1 April)
• Re: Defaults: Getting concrete (Monday, 1 April)
• Re: FW: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Monday, 1 April)

Mike Jones

• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)

Mountie Lee

• basic principle of key ownership (Sunday, 28 April)
• Re: Use case: Document signing (using legally binding signatures) (Thursday, 25 April)
• Re: Use case: Authenticate using eID (Thursday, 25 April)
• who own the key? (Thursday, 25 April)
• Re: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• Re: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• do we need secure removal function for keys in low level API? (Wednesday, 24 April)
• Web Certificate API latest draft (Wednesday, 24 April)
• Re: W3C Web Crypto WG - location and agenda of our F2F meeting next week (Sunday, 21 April)
• Re: [W3C WebCrypto API WG] Key discovery (Friday, 5 April)
• Re: Web Cryptography Use Cases For Review (Thursday, 4 April)
• Re: [Moderator Action] Missing items in KeyUsage (Monday, 1 April)
• Re: draft for certificate management (Monday, 1 April)
• Re: Web Cryptography Use Cases For Review (Monday, 1 April)

Nick Van den Bleeken

• Use case: Authenticate using eID (Wednesday, 24 April)
• Use case: Document signing (using legally binding signatures) (Wednesday, 24 April)
• Re: [W3C WebCrypto API WG] Key discovery (Thursday, 11 April)
• Re: [W3C WebCrypto API WG] Key discovery (Tuesday, 9 April)
• Re: [W3C WebCrypto API WG] Key discovery (Monday, 8 April)
• Re: [W3C WebCrypto API WG] Key discovery (Monday, 8 April)

Richard Barnes

• Re: ISSUE-35 - Use cases for Wrap/Unwrap (Friday, 26 April)
• Re: UA interop (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: On a Futures-style API (Tuesday, 23 April)
• On a Futures-style API (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: Defaults issues with AES-GCM (Thursday, 18 April)
• Re: crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] (Thursday, 18 April)
• GCM ciphertext + tag ambiguity (Thursday, 18 April)
• Defaults issues with AES-GCM (Thursday, 18 April)
• Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Friday, 5 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Friday, 5 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Thursday, 4 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• Re: Defaults: Getting concrete (Monday, 1 April)
• Re: [jose] jose interim meeting planned (advance announcement) (Monday, 1 April)
• Defaults: Getting concrete (Monday, 1 April)
• Separate method for key agreement? (Monday, 1 April)
• Potential contradiction in HKDF? (Monday, 1 April)

Ryan Sleevi

• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Tuesday, 30 April)
• Re: basic principle of key ownership (Monday, 29 April)
• Re: Updated spec examples with Futures (Saturday, 27 April)
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Saturday, 27 April)
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Saturday, 27 April)
• Re: Updated spec examples with Futures (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? (Friday, 26 April)
• ISSUE-35 - Wrap/Unwrap - Why JOSE? (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU (Friday, 26 April)
• Re: ISSUE-35 - Use cases for Wrap/Unwrap (Friday, 26 April)
• Re: UA interop (Thursday, 25 April)
• ISSUE-35 - Use cases for Wrap/Unwrap (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: who own the key? (Thursday, 25 April)
• Re: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• Re: UA interop (Thursday, 25 April)
• Re: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: Use case: Authenticate using eID (Thursday, 25 April)
• Re: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• Re: Named key discovery questions (Thursday, 25 April)
• Re: On a Futures-style API (Wednesday, 24 April)
• Re: W3C Web Crypto WG - wednesday 25th of April agenda update (Wednesday, 24 April)
• Re: On a Futures-style API (Tuesday, 23 April)
• Re: On a Futures-style API (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Tuesday, 23 April)
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams (Tuesday, 23 April)
• Re: Editorial: Empty list item in section '14.1.6. The generateKey method' (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (Monday, 22 April)
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Monday, 22 April)
• Re: Defaults: Getting concrete (round 2) (Friday, 19 April)
• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: Defaults issues with AES-GCM (Thursday, 18 April)
• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: GCM ciphertext + tag ambiguity (Thursday, 18 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Monday, 15 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Monday, 15 April)
• Re: WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. (Monday, 8 April)
• Re: [W3C WebCrypto API WG] Key discovery (Saturday, 6 April)
• Re: [W3C WebCrypto API WG] Key discovery (Friday, 5 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Friday, 5 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Friday, 5 April)
• Re: [W3C WebCrypto API WG] Key discovery (Friday, 5 April)
• Re: [W3C WebCrypto API WG] Key discovery (Thursday, 4 April)
• Re: Socializing the high level API during our F2F meeting in April (Thursday, 4 April)
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Wednesday, 3 April)
• Re: [jose] jose interim meeting planned (advance announcement) (Wednesday, 3 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: [Moderator Action] Missing items in KeyUsage (Tuesday, 2 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• Re: Defaults: Getting concrete (Monday, 1 April)
• Re: Separate method for key agreement? (Monday, 1 April)
• Re: FW: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Monday, 1 April)

Seetharama Rao Durbha

• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)

Vijay Bharadwaj

• RE: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• RE: Named key discovery questions (Thursday, 25 April)
• RE: do we need secure removal function for keys in low level API? (Thursday, 25 April)
• RE: Named key discovery questions (Thursday, 25 April)
• RE: Separate method for key agreement? (Tuesday, 2 April)
• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• RE: Separate method for key agreement? (Tuesday, 2 April)
• RE: [Moderator Action] Missing items in KeyUsage (Tuesday, 2 April)
• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations (Tuesday, 2 April)
• RE: On Crypto API Safety in the Hands of Unskilled Developers (Tuesday, 2 April)

Wan-Teh Chang

• Re: Defaults: Getting concrete (round 2) (Tuesday, 23 April)
• Re: Defaults: Getting concrete (round 2) (Friday, 19 April)
• WebCrypto Key Discovery: mark non-normative sections as such (Thursday, 18 April)
• Re: Defaults: Getting concrete (round 2) (Thursday, 18 April)
• Re: Defaults issues with AES-GCM (Thursday, 18 April)
• Re: GCM ciphertext + tag ambiguity (Thursday, 18 April)
• Re: Separate method for key agreement? (Tuesday, 2 April)
• Re: Separate method for key agreement? (Monday, 1 April)

Web Cryptography Working Group Issue Tracker

• crypto-ISSUE-44: Require creation of random IVs by default for CBC, CFB, GCM (Tuesday, 23 April)
• crypto-ISSUE-43: Separate method for key agreement [design for Web Crypto API] (Tuesday, 23 April)
• crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] (Thursday, 18 April)
• crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] (Monday, 1 April)

Wendy Seltzer

• Fwd: [Moderator Action] Missing items in KeyUsage (Monday, 1 April)

조상래

• RE: basic principle of key ownership (Monday, 29 April)
• RE: basic principle of key ownership (Monday, 29 April)

Last message date: Tuesday, 30 April 2013 20:21:02 UTC