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

Tuesday, 30 April 2013

• W3C Web Crypto WG - discussing the web security model GALINDO Virginie
• W3C Web Crypto WG - Take away from San Jose F2F meeting - april 2012 GALINDO Virginie
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Ryan Sleevi

Monday, 29 April 2013

• Re: basic principle of key ownership Ryan Sleevi
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Aymeric Vitte
• RE: basic principle of key ownership 조상래
• RE: basic principle of key ownership 조상래

Sunday, 28 April 2013

• basic principle of key ownership Mountie Lee

Saturday, 27 April 2013

• Re: Updated spec examples with Futures Ryan Sleevi
• Re: Updated spec examples with Futures Aymeric Vitte
• Re: Updated spec examples with Futures Aymeric Vitte
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Mark Watson
• Re: Updated spec examples with Futures Alex Russell
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Ryan Sleevi
• RE: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Israel Hilerio
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Ryan Sleevi
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Mark Watson

Friday, 26 April 2013

• Re: Updated spec examples with Futures Ryan Sleevi
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Ryan Sleevi
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Ryan Sleevi
• Re: Updated spec examples with Futures Aymeric Vitte
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Mark Watson
• Re: ISSUE-35 - Wrap/Unwrap - Why JOSE? Mark Watson
• ISSUE-35 - Wrap/Unwrap - Why JOSE? Ryan Sleevi
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Ryan Sleevi
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Mark Watson
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Ryan Sleevi
• Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU Mark Watson
• W3C Web Crypto WG - regular call (WG participants only) GALINDO Virginie
• W3C Web Crypto WG - Our next conference calls - correct dates, forget previous mail GALINDO Virginie
• W3C Web Crypto WG - Our next conference calls GALINDO Virginie
• Re: ISSUE-35 - Use cases for Wrap/Unwrap Ryan Sleevi
• Re: ISSUE-35 - Use cases for Wrap/Unwrap Richard Barnes

Thursday, 25 April 2013

• RE: Named key discovery questions Hutchinson Michael
• Re: UA interop Ryan Sleevi
• RE: UA interop Hutchinson Michael
• RE: UA interop Hutchinson Michael
• ISSUE-35 - Use cases for Wrap/Unwrap Ryan Sleevi
• Re: Named key discovery questions Mark Watson
• Re: Named key discovery questions Ryan Sleevi
• Re: Named key discovery questions Mark Watson
• Re: Use case: Document signing (using legally binding signatures) Mountie Lee
• Re: UA interop Richard Barnes
• Re: Named key discovery questions Richard Barnes
• RE: do we need secure removal function for keys in low level API? Vijay Bharadwaj
• Re: Use case: Authenticate using eID Mountie Lee
• Re: who own the key? Ryan Sleevi
• who own the key? Mountie Lee
• Re: do we need secure removal function for keys in low level API? Mountie Lee
• Re: do we need secure removal function for keys in low level API? Ryan Sleevi
• Re: Use case: Authenticate using eID Mark Watson
• Re: do we need secure removal function for keys in low level API? Mountie Lee
• Re: Named key discovery questions Mark Watson
• RE: Named key discovery questions Acar, Tolga
• Re: UA interop Ryan Sleevi
• UA interop Hutchinson Michael
• Re: do we need secure removal function for keys in low level API? Ryan Sleevi
• RE: do we need secure removal function for keys in low level API? Hutchinson Michael
• Re: Named key discovery questions Mark Watson
• RE: Named key discovery questions Vijay Bharadwaj
• RE: do we need secure removal function for keys in low level API? Vijay Bharadwaj
• RE: Named key discovery questions Hutchinson Michael
• Re: Named key discovery questions Ryan Sleevi
• Re: Use case: Authenticate using eID Ryan Sleevi
• Re: do we need secure removal function for keys in low level API? Ryan Sleevi
• RE: Named key discovery questions Vijay Bharadwaj
• Re: Named key discovery questions Ryan Sleevi
• Named key discovery questions Mark Watson
• Re: Updated spec examples with Futures Aymeric Vitte
• Updated spec examples with Futures Alex Russell

Wednesday, 24 April 2013

• W3C Web Crypto F2F April meeting - minutes GALINDO Virginie
• W3C Web Crypto WG - Wednesday afternoon agenda GALINDO Virginie
• do we need secure removal function for keys in low level API? Mountie Lee
• Use case: Authenticate using eID Nick Van den Bleeken
• Use case: Document signing (using legally binding signatures) Nick Van den Bleeken
• Re: On a Futures-style API Ryan Sleevi
• Re: On a Futures-style API Aymeric Vitte
• Web Certificate API latest draft Mountie Lee
• W3C Web Crypto WG - wednesday 25th of April agenda update - starting at 8:30 GALINDO Virginie
• Re: On a Futures-style API Alex Russell
• RE: W3C Web Crypto WG - wednesday 25th of April agenda update GALINDO Virginie
• Re: W3C Web Crypto WG - wednesday 25th of April agenda update Ryan Sleevi
• Testing infrastruture docs and links Harry Halpin
• W3C Web Crypto WG - wednesday 25th of April agenda update GALINDO Virginie

Tuesday, 23 April 2013

• Re: On a Futures-style API Ryan Sleevi
• Re: On a Futures-style API Aymeric Vitte
• crypto-ISSUE-44: Require creation of random IVs by default for CBC, CFB, GCM Web Cryptography Working Group Issue Tracker
• crypto-ISSUE-43: Separate method for key agreement [design for Web Crypto API] Web Cryptography Working Group Issue Tracker
• Re: Defaults: Getting concrete (round 2) Wan-Teh Chang
• Re: On a Futures-style API Richard Barnes
• Re: On a Futures-style API Ryan Sleevi
• On a Futures-style API Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Aymeric Vitte
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• RE: Defaults: Getting concrete (round 2) GALINDO Virginie
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Ryan Sleevi
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Aymeric Vitte
• Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Ryan Sleevi
• Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams Israel Hilerio
• Re: Editorial: Empty list item in section '14.1.6. The generateKey method' Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Richard Barnes

Monday, 22 April 2013

• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? Ryan Sleevi
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? Mark Watson
• Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? Ryan Sleevi
• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week GALINDO Virginie
• PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? Mark Watson
• RE: Defaults: Getting concrete (round 2) Acar, Tolga
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Richard Barnes

Sunday, 21 April 2013

• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week GALINDO Virginie
• Re: W3C Web Crypto WG - location and agenda of our F2F meeting next week Mountie Lee

Saturday, 20 April 2013

• RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week Jim Schaad
• W3C Web Crypto WG - location and agenda of our F2F meeting next week GALINDO Virginie
• W3C Web Crypto WG - reception on wednesday 24th of April in Paypal from 5 to 7 PM GALINDO Virginie

Friday, 19 April 2013

• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Wan-Teh Chang

Thursday, 18 April 2013

• Re: Defaults: Getting concrete (round 2) Seetharama Rao Durbha
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• Re: Defaults: Getting concrete (round 2) Richard Barnes
• RE: GCM ciphertext + tag ambiguity Jim Schaad
• WebCrypto Key Discovery: mark non-normative sections as such Wan-Teh Chang
• Re: Defaults issues with AES-GCM Richard Barnes
• Re: Defaults: Getting concrete (round 2) Wan-Teh Chang
• Re: Defaults issues with AES-GCM Wan-Teh Chang
• Re: GCM ciphertext + tag ambiguity Wan-Teh Chang
• Re: Defaults issues with AES-GCM Ryan Sleevi
• Re: Defaults: Getting concrete (round 2) Ryan Sleevi
• Re: GCM ciphertext + tag ambiguity Ryan Sleevi
• Re: crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] Richard Barnes
• crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] Web Cryptography Working Group Issue Tracker
• GCM ciphertext + tag ambiguity Richard Barnes
• Defaults issues with AES-GCM Richard Barnes
• Defaults: Getting concrete (round 2) Richard Barnes

Monday, 15 April 2013

• Minutes of our April 15th 2013 telecon Harry Halpin
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Ryan Sleevi
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Mark Watson
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Ryan Sleevi

Sunday, 14 April 2013

• W3C Web Crypto WG - agenda for our F2F meeting GALINDO Virginie

Saturday, 13 April 2013

• Fwd: some input on API Arun Ranganathan

Friday, 12 April 2013

• W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC GALINDO Virginie
• [W3C Web Crypto WG] testing activities GALINDO Virginie
• TPAC2013 in Shenzhen, China, 11-15 November 2013 - book your week ! GALINDO Virginie
• RE: Session with WebAppSec WG in San Jose ? GALINDO Virginie
• RE: Socializing the high level API during our F2F meeting in April GALINDO Virginie

Thursday, 11 April 2013

• Re: [W3C WebCrypto API WG] Key discovery Nick Van den Bleeken
• Call for Exclusions (Update): WebCrypto Key Discovery Ian Jacobs

Wednesday, 10 April 2013

• Re: [W3C WebCrypto API WG] Key discovery Aymeric Vitte

Tuesday, 9 April 2013

• Re: [W3C WebCrypto API WG] Key discovery Nick Van den Bleeken

Monday, 8 April 2013

• Re: WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. Aymeric Vitte
• Re: WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. Ryan Sleevi
• WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal. Aymeric Vitte
• Re: [W3C WebCrypto API WG] Key discovery Aymeric Vitte
• Re: [W3C WebCrypto API WG] Key discovery Nick Van den Bleeken
• Re: [W3C WebCrypto API WG] Key discovery Aymeric Vitte
• Re: [W3C WebCrypto API WG] Key discovery Nick Van den Bleeken
• Re: Socializing the high level API during our F2F meeting in April Harry Halpin
• RE: Socializing the high level API during our F2F meeting in April GALINDO Virginie

Saturday, 6 April 2013

• Re: [W3C WebCrypto API WG] Key discovery Ryan Sleevi
• RE: [W3C WebCrypto API WG] Key discovery Hutchinson Michael

Friday, 5 April 2013

• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Richard Barnes
• Re: [W3C WebCrypto API WG] Key discovery Ryan Sleevi
• RE: [W3C WebCrypto API WG] Key discovery Hutchinson Michael
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Ryan Sleevi
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Richard Barnes
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Ryan Sleevi
• Re: [W3C WebCrypto API WG] Key discovery Ryan Sleevi
• Re: [W3C WebCrypto API WG] Key discovery Mountie Lee
• Re: [W3C WebCrypto API WG] Key discovery Mark Watson

Thursday, 4 April 2013

• Re: [W3C WebCrypto API WG] Key discovery Ryan Sleevi
• [W3C WebCrypto API WG] Key discovery Lu HongQian Karen
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Aymeric Vitte
• Re: [W3C Web Crypto WG] About import/export Mark Watson
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Mark Watson
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Aymeric Vitte
• Re: Socializing the high level API during our F2F meeting in April Ryan Sleevi
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Aymeric Vitte
• [W3C Web Crypto WG] About import/export GALINDO Virginie
• [W3C Web Crypto API] PROPOSAL : closing ISSUE-32 (API should mention the use of secure elements in the context of key security) GALINDO Virginie
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Mark Watson
• Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) Aymeric Vitte
• Re: Socializing the high level API during our F2F meeting in April Harry Halpin
• Re: [W3C Web Crypto WG] Proposal to close ISSUE-7 Harry Halpin
• [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable) GALINDO Virginie
• [W3C Web Crypto WG] PROPOSAL: Close ISSUE-17 (Define the scope and API for custom key attributes) GALINDO Virginie
• [W3C Web Crypto WG] Proposal to close ISSUE-7 GALINDO Virginie
• Session with WebAppSec WG in San Jose ? GALINDO Virginie
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Richard Barnes
• Re: Web Cryptography Use Cases For Review Mountie Lee

Wednesday, 3 April 2013

• Re: Web Cryptography Use Cases For Review Arun Ranganathan
• Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Ryan Sleevi
• Re: Socializing the high level API during our F2F meeting in April David Dahl
• Re: On Crypto API Safety in the Hands of Unskilled Developers Arun Ranganathan
• Re: Socializing the high level API during our F2F meeting in April Arun Ranganathan
• Re: [jose] jose interim meeting planned (advance announcement) Ryan Sleevi

Tuesday, 2 April 2013

• Re: Separate method for key agreement? Richard Barnes
• RE: Separate method for key agreement? Vijay Bharadwaj
• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Vijay Bharadwaj
• Re: Separate method for key agreement? Ryan Sleevi
• Re: Separate method for key agreement? Richard Barnes
• Re: [Moderator Action] Missing items in KeyUsage Ryan Sleevi
• Re: Separate method for key agreement? Ryan Sleevi
• Re: Separate method for key agreement? Ryan Sleevi
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Ryan Sleevi
• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Mike Jones
• RE: Separate method for key agreement? Acar, Tolga
• Re: Separate method for key agreement? Richard Barnes
• W3C Web Crypto WG - draft minutes of our call 1st of April 2013 GALINDO Virginie
• Re: On Crypto API Safety in the Hands of Unskilled Developers David Dahl
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Mark Watson
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Richard Barnes
• Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Mark Watson
• Socializing the high level API during our F2F meeting in April GALINDO Virginie
• RE: Separate method for key agreement? Vijay Bharadwaj
• RE: [Moderator Action] Missing items in KeyUsage Vijay Bharadwaj
• RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Vijay Bharadwaj
• RE: On Crypto API Safety in the Hands of Unskilled Developers Vijay Bharadwaj
• Re: Separate method for key agreement? Wan-Teh Chang

Monday, 1 April 2013

• Re: [Moderator Action] Missing items in KeyUsage Mountie Lee
• Re: [Moderator Action] Missing items in KeyUsage Mark Watson
• Fwd: [Moderator Action] Missing items in KeyUsage Wendy Seltzer
• Re: Defaults: Getting concrete Ryan Sleevi
• Re: Separate method for key agreement? Ryan Sleevi
• Re: Separate method for key agreement? Mark Watson
• Re: Separate method for key agreement? Wan-Teh Chang
• W3C Web Crypto WG - regular meeting GALINDO Virginie
• Re: Defaults: Getting concrete Richard Barnes
• Re: Defaults: Getting concrete Mark Watson
• RE: Potential contradiction in HKDF? Acar, Tolga
• Re: FW: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Mark Watson
• Re: [jose] jose interim meeting planned (advance announcement) Richard Barnes
• Defaults: Getting concrete Richard Barnes
• Separate method for key agreement? Richard Barnes
• Potential contradiction in HKDF? Richard Barnes
• crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API] Web Cryptography Working Group Issue Tracker
• Fwd: [jose] jose interim meeting planned (advance announcement) Harry Halpin
• Re: draft for certificate management Mountie Lee
• Re: FW: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations Ryan Sleevi
• Re: Web Cryptography Use Cases For Review Mountie Lee

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