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

Alex Russell

• Re: An initial editor's draft: high-level API (Wednesday, 20 February)

Ali Asad

• RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (Monday, 4 February)

Anthony Nadalin

• RE: DOM Dependency (Tuesday, 26 February)
• RE: DOM Dependency (Tuesday, 26 February)
• RE: DOM Dependency (Wednesday, 20 February)
• RE: DOM Dependency (Tuesday, 19 February)
• DOM Dependency (Tuesday, 19 February)

Arun Ranganathan

• Re: Registries and Interoperability (Thursday, 7 February)
• Re: 3GPP liaison request - possible answer (Thursday, 7 February)

David Dahl

• Re: DOM Dependency (Tuesday, 26 February)
• Re: DOM Dependency (Wednesday, 20 February)

GALINDO Virginie

• RE: DOM Dependency (Tuesday, 26 February)
• RE: DOM Dependency (Tuesday, 26 February)
• RE: ISSUE 22 - Re: Incomplete blocks (Tuesday, 26 February)
• Proposal to close ISSUE-7 (Monday, 25 February)
• ISSUE-19 is expecting proposal or will be postponed (Monday, 25 February)
• ISSUE-26 is expecting proposal or will be postponed (Monday, 25 February)
• W3C Web Crypto WG - take away of our 18th of Feb conf call (Monday, 25 February)
• RE: ISSUE 22 - Re: Incomplete blocks (Monday, 25 February)
• W3C Web Crypto WG - classifying issues (Monday, 18 February)
• W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC (Sunday, 17 February)
• PROPOSAL: CLOSE ISSUE-40: How should we define key discovery, noting asynchronicity (Monday, 11 February)
• RE: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Thursday, 7 February)
• RE: Registries and Interoperability (Thursday, 7 February)
• RE: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Thursday, 7 February)
• RE: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Thursday, 7 February)
• W3C Web Crypto WG - classifying issues (Thursday, 7 February)
• 3GPP liaison request - possible answer (Wednesday, 6 February)
• [info] WASH13, a workshop on web application and secure hardware (Wednesday, 6 February)
• W3C Web Crypto WG - regular meeting (Tuesday, 5 February)
• trackbot can now associate ACTIONs and ISSUEs with products (Monday, 4 February)
• W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (Monday, 4 February)
• RE: W3C Web Crypto WG - focus on issue management during our next call (Monday, 4 February)
• W3C Web Crypto WG - focus on issue management during our next call (Friday, 1 February)

Harry Halpin

• ISSUE-30: Key import/export? (Monday, 25 February)
• Re: W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC (Monday, 18 February)
• Re: Registries and Interoperability (Monday, 18 February)
• Re: Registries and Interoperability (Tuesday, 12 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Thursday, 7 February)
• Re: Registries and Interoperability (Thursday, 7 February)
• Re: Registries and Interoperability (Wednesday, 6 February)
• Registries and Interoperability (Monday, 4 February)
• Re: W3C Web Crypto WG - focus on issue management during our next call (Monday, 4 February)

Mark Watson

• RE: Proposal for key wrap/unwrap (ISSUE-35) (Monday, 25 February)
• ACTION-66 (Tuesday, 19 February)
• Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (Monday, 11 February)
• Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (Monday, 4 February)

Mountie Lee

• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Tuesday, 26 February)
• Re: ISSUE-30: Key import/export? (Tuesday, 26 February)
• Re: W3C Web Crypto WG - focus on issue management during our next call (Monday, 4 February)
• Re: W3C Web Crypto WG - focus on issue management during our next call (Sunday, 3 February)
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Saturday, 2 February)
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Friday, 1 February)

Nadim Kobeissi

• Re: DOM Dependency (Tuesday, 19 February)
• Re: DOM Dependency (Tuesday, 19 February)

Nick Van den Bleeken

• Missing InvalidStateError when calling the CryptoOperation methods in an 'incorrect' order? (Thursday, 28 February)
• Editorial: Empty list item in section '14.1.6. The generateKey method' (Thursday, 28 February)
• Question about step 1 of section '12.4.1. process(ArrayBufferView data)' (Thursday, 28 February)
• Introduction (Monday, 4 February)

Richard Barnes

• Re: ISSUE: Define MGF AlgorithmIdentifiers (Thursday, 28 February)
• ISSUE: Define MGF AlgorithmIdentifiers (Thursday, 28 February)
• Re: ISSUE-19 is expecting proposal or will be postponed (Wednesday, 27 February)
• Re: ISSUE-26 is expecting proposal or will be postponed (Wednesday, 27 February)
• Re: DOM Dependency (Wednesday, 27 February)
• Re: DOM Dependency (Tuesday, 26 February)
• Making choices for developers (Re: Incomplete blocks) (Thursday, 14 February)
• Re: Incomplete blocks (Thursday, 14 February)
• Incomplete blocks (Thursday, 14 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Friday, 8 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Friday, 8 February)
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Friday, 8 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Tuesday, 5 February)
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Tuesday, 5 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Tuesday, 5 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-24 - Defining a Synchronous API (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Monday, 4 February)

Ryan Sleevi

• Re: ISSUE: Define MGF AlgorithmIdentifiers (Thursday, 28 February)
• Re: DOM Dependency (Tuesday, 26 February)
• Re: DOM Dependency (Tuesday, 26 February)
• Re: DOM Dependency (Tuesday, 26 February)
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Tuesday, 26 February)
• Re: ISSUE-30: Key import/export? (Tuesday, 26 February)
• Re: Proposal for key wrap/unwrap (ISSUE-35) (Monday, 25 February)
• Re: ISSUE-30: Key import/export? (Monday, 25 February)
• Re: ISSUE 22 - Re: Incomplete blocks (Monday, 25 February)
• Re: DOM Dependency (Tuesday, 19 February)
• Re: DOM Dependency (Tuesday, 19 February)
• Re: DOM Dependency (Tuesday, 19 February)
• Re: DOM Dependency (Tuesday, 19 February)
• Re: Registries and Interoperability (Tuesday, 19 February)
• Re: Making choices for developers (Re: Incomplete blocks) (Friday, 15 February)
• Re: Incomplete blocks (Thursday, 14 February)
• Re: Incomplete blocks (Thursday, 14 February)
• Re: Registries and Interoperability (Thursday, 14 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: Registries and Interoperability (Friday, 8 February)
• Re: 3GPP liaison request - possible answer (Thursday, 7 February)
• Re: W3C Web Crypto WG - classifying issues (Thursday, 7 February)
• Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (Thursday, 7 February)
• Re: PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• Re: PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys (Thursday, 7 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Thursday, 7 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Thursday, 7 February)
• PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• PROPOSAL: Postpone ISSUE-26: Should key generation be allowed to specify multi-origin access (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• PROPOSAL: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• PROPOSAL: Postpone ISSUE-34: Representation of Certificates (was Re: W3C Web Crypto WG - classifying issues) (Thursday, 7 February)
• PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) (Thursday, 7 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Thursday, 7 February)
• Algorithm attribute (was Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes ) (Thursday, 7 February)
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Thursday, 7 February)
• Re: Registries and Interoperability (Thursday, 7 February)
• Re: Registries and Interoperability (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Monday, 4 February)
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Friday, 1 February)

Seetharama Rao Durbha

• Re: Registries and Interoperability (Friday, 8 February)
• Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC (Monday, 4 February)

Last message date: Thursday, 28 February 2013 21:53:18 UTC