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

Thursday, 28 February 2013

• Re: ISSUE: Define MGF AlgorithmIdentifiers Richard Barnes
• Re: ISSUE: Define MGF AlgorithmIdentifiers Ryan Sleevi
• ISSUE: Define MGF AlgorithmIdentifiers Richard Barnes
• Missing InvalidStateError when calling the CryptoOperation methods in an 'incorrect' order? Nick Van den Bleeken
• Editorial: Empty list item in section '14.1.6. The generateKey method' Nick Van den Bleeken
• Question about step 1 of section '12.4.1. process(ArrayBufferView data)' Nick Van den Bleeken

Wednesday, 27 February 2013

• Re: ISSUE-19 is expecting proposal or will be postponed Richard Barnes
• Re: ISSUE-26 is expecting proposal or will be postponed Richard Barnes
• Re: DOM Dependency Richard Barnes

Tuesday, 26 February 2013

• Re: DOM Dependency Richard Barnes
• RE: DOM Dependency Anthony Nadalin
• Re: DOM Dependency David Dahl
• Re: DOM Dependency Ryan Sleevi
• RE: DOM Dependency Anthony Nadalin
• Re: DOM Dependency Ryan Sleevi
• RE: DOM Dependency GALINDO Virginie
• Re: DOM Dependency Ryan Sleevi
• RE: DOM Dependency GALINDO Virginie
• RE: ISSUE 22 - Re: Incomplete blocks GALINDO Virginie
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access Mountie Lee
• Re: ISSUE-30: Key import/export? Ryan Sleevi
• Re: ISSUE-30: Key import/export? Mountie Lee

Monday, 25 February 2013

• Re: Proposal for key wrap/unwrap (ISSUE-35) Ryan Sleevi
• RE: Proposal for key wrap/unwrap (ISSUE-35) Mark Watson
• Re: ISSUE-30: Key import/export? Ryan Sleevi
• ISSUE-30: Key import/export? Harry Halpin
• Re: ISSUE 22 - Re: Incomplete blocks Ryan Sleevi
• Proposal to close ISSUE-7 GALINDO Virginie
• ISSUE-19 is expecting proposal or will be postponed GALINDO Virginie
• ISSUE-26 is expecting proposal or will be postponed GALINDO Virginie
• W3C Web Crypto WG - take away of our 18th of Feb conf call GALINDO Virginie
• RE: ISSUE 22 - Re: Incomplete blocks GALINDO Virginie

Wednesday, 20 February 2013

• Re: An initial editor's draft: high-level API Alex Russell
• Re: DOM Dependency David Dahl
• RE: DOM Dependency Anthony Nadalin

Tuesday, 19 February 2013

• Re: DOM Dependency Ryan Sleevi
• Re: DOM Dependency Nadim Kobeissi
• Re: DOM Dependency Ryan Sleevi
• Re: DOM Dependency Ryan Sleevi
• RE: DOM Dependency Anthony Nadalin
• Re: DOM Dependency Nadim Kobeissi
• Re: DOM Dependency Ryan Sleevi
• DOM Dependency Anthony Nadalin
• Re: Registries and Interoperability Ryan Sleevi
• ACTION-66 Mark Watson

Monday, 18 February 2013

• W3C Web Crypto WG - classifying issues GALINDO Virginie
• Re: W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC Harry Halpin
• Re: Registries and Interoperability Harry Halpin

Sunday, 17 February 2013

• W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC GALINDO Virginie

Friday, 15 February 2013

• Re: Making choices for developers (Re: Incomplete blocks) Ryan Sleevi

Thursday, 14 February 2013

• Making choices for developers (Re: Incomplete blocks) Richard Barnes
• Re: Incomplete blocks Ryan Sleevi
• Re: Incomplete blocks Richard Barnes
• Re: Incomplete blocks Ryan Sleevi
• Incomplete blocks Richard Barnes
• Re: Registries and Interoperability Ryan Sleevi

Tuesday, 12 February 2013

• Re: Registries and Interoperability Harry Halpin

Monday, 11 February 2013

• PROPOSAL: CLOSE ISSUE-40: How should we define key discovery, noting asynchronicity GALINDO Virginie
• Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) Mark Watson

Friday, 8 February 2013

• Re: Registries and Interoperability Ryan Sleevi
• Re: Registries and Interoperability Richard Barnes
• Re: Registries and Interoperability Ryan Sleevi
• Re: Registries and Interoperability Ryan Sleevi
• Re: Registries and Interoperability Richard Barnes
• Re: Registries and Interoperability Seetharama Rao Durbha
• Re: Registries and Interoperability Richard Barnes
• Re: Registries and Interoperability Richard Barnes
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Richard Barnes
• Re: Registries and Interoperability Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Richard Barnes
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes Richard Barnes
• Re: Registries and Interoperability Harry Halpin
• Re: Registries and Interoperability Ryan Sleevi
• Re: Registries and Interoperability Harry Halpin

Thursday, 7 February 2013

• Re: Registries and Interoperability Arun Ranganathan
• Re: 3GPP liaison request - possible answer Ryan Sleevi
• Re: 3GPP liaison request - possible answer Arun Ranganathan
• Re: W3C Web Crypto WG - classifying issues Ryan Sleevi
• Re: PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) Ryan Sleevi
• Re: PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Ryan Sleevi
• PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• PROPOSAL: Postpone ISSUE-26: Should key generation be allowed to specify multi-origin access (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• PROPOSAL: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• PROPOSAL: Postpone ISSUE-34: Representation of Certificates (was Re: W3C Web Crypto WG - classifying issues) Ryan Sleevi
• PROPOSAL: Move ISSUE-40: How should we define key discovery, noting asynchronicity ( was Re: W3C Web Crypto WG - classifying issues ) Ryan Sleevi
• Re: Registries and Interoperability Harry Halpin
• Re: Registries and Interoperability Harry Halpin
• RE: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? GALINDO Virginie
• RE: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access GALINDO Virginie
• RE: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys GALINDO Virginie
• RE: Registries and Interoperability GALINDO Virginie
• W3C Web Crypto WG - classifying issues GALINDO Virginie
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Ryan Sleevi
• Algorithm attribute (was Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes ) Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes Ryan Sleevi
• Re: Registries and Interoperability Ryan Sleevi

Wednesday, 6 February 2013

• 3GPP liaison request - possible answer GALINDO Virginie
• [info] WASH13, a workshop on web application and secure hardware GALINDO Virginie
• Re: Registries and Interoperability Harry Halpin

Tuesday, 5 February 2013

• W3C Web Crypto WG - regular meeting GALINDO Virginie
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Richard Barnes
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes Richard Barnes
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Richard Barnes

Monday, 4 February 2013

• Re: Registries and Interoperability Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Ryan Sleevi
• Registries and Interoperability Harry Halpin
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Richard Barnes
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Ryan Sleevi
• Re: PROPOSAL: Close ISSUE-24 - Defining a Synchronous API Richard Barnes
• Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys Richard Barnes
• Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? Richard Barnes
• Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes Richard Barnes
• Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC Mark Watson
• RE: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC Ali Asad
• Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC Seetharama Rao Durbha
• trackbot can now associate ACTIONs and ISSUEs with products GALINDO Virginie
• W3C Web Crypto WG - agenda for our call today @ 20:00 UTC GALINDO Virginie
• Re: W3C Web Crypto WG - focus on issue management during our next call Harry Halpin
• Introduction Nick Van den Bleeken
• Re: W3C Web Crypto WG - focus on issue management during our next call Mountie Lee
• RE: W3C Web Crypto WG - focus on issue management during our next call GALINDO Virginie

Sunday, 3 February 2013

• Re: W3C Web Crypto WG - focus on issue management during our next call Mountie Lee

Saturday, 2 February 2013

• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access Mountie Lee

Friday, 1 February 2013

• W3C Web Crypto WG - focus on issue management during our next call GALINDO Virginie
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access Mountie Lee
• Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access Ryan Sleevi

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