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

Alex Russell

• Re: PROPOSAL: Close ISSUE-24 - Defining a Synchronous API (Thursday, 31 January)
• Re: Test Suite on Github - need your GitHub IDs (Wednesday, 23 January)

Arun Ranganathan

• Re: Web Cryptography Use Cases For Review (Monday, 14 January)

Christopher Kula

• Re: Test Suite on Github - need your GitHub IDs (Wednesday, 23 January)

David Dahl

• Re: An initial editor's draft: high-level API (Tuesday, 29 January)
• Re: An initial editor's draft: high-level API (Monday, 28 January)
• An initial editor's draft: high-level API (Monday, 28 January)

GALINDO Virginie

• RE: Face-to-face meeting dates in Silcon Valley April (Wednesday, 30 January)
• [info] OASIS PKCS#11 WG creation (Wednesday, 30 January)
• [Pubrules] Copyright update with new W3C Host (Tuesday, 29 January)
• W3C Web Crypto WG - our last call minutes of 21st of Jan (Friday, 25 January)
• W3C Web Crypto WG - take away of our 21st of Jan conf call (Friday, 25 January)
• RE: W3C Web Crypto WG - bridge for our call today @ 15:00 UTC (Monday, 21 January)
• W3C Web Crypto WG - bridge for our call today @ 15:00 UTC (Monday, 21 January)
• W3C Web Crypto WG - agenda for our call today @ 15:00 UTC (Monday, 21 January)
• W3C Web Crypto WG - agenda for our call today (Monday, 21 January)
• RE: Proposal for key wrap/unwrap (ISSUE-35) (Wednesday, 16 January)
• W3C Web Crypto WG - no call today, but next week :) (Monday, 14 January)
• next F2F Web Crypto WG - extending dates of the doodle to april - please survey again ! (Wednesday, 9 January)
• W3C Web Crypto WG - take away from the 7th of Jan conf call (Tuesday, 8 January)
• W3C Web Crypto WG - reminder about our call tomorrow @20:00 UTC and agenda (Sunday, 6 January)

Harry Halpin

• Re: Face-to-face meeting dates in Silcon Valley April (Wednesday, 30 January)
• Face-to-face meeting dates in Silcon Valley April (Wednesday, 30 January)
• Korea Fwd: TPAC2013 in Shenzhen, China (18-22 November) (Wednesday, 30 January)
• Fwd: W3Conf 2013 Update and Discount for W3C Members (Thursday, 24 January)
• Re: Test Suite on Github - need your GitHub IDs (Wednesday, 23 January)
• Test Suite on Github - need your GitHub IDs (Tuesday, 22 January)
• Re: IANA registry for WebCrypto? (Saturday, 19 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• IANA registry for WebCrypto? (Friday, 18 January)
• Discussion of WebCrypto API in HTML WG (Friday, 18 January)
• Another use-case re authentication (Monday, 7 January)
• Re: Harry's talk at CCC (Monday, 7 January)

Håvard Molland

• Re: Opera Random Numbers (Monday, 28 January)

Ian Jacobs

• Call for Exclusions: WebCrypto Key Discovery (Tuesday, 8 January)

JoAnne Yates

• Introducing myself to WebCrypto Working Group (Tuesday, 8 January)

Mark Watson

• Re: Proposal for key wrap/unwrap (ISSUE-35) (Thursday, 17 January)
• Re: Proposal for key wrap/unwrap (ISSUE-35) (Wednesday, 16 January)

Mike Jones

• RE: Face-to-face meeting dates in Silcon Valley April (Wednesday, 30 January)
• RE: IANA registry for WebCrypto? (Friday, 18 January)
• RE: Get rid of "params"? (Friday, 18 January)

Mountie Lee

• Prioritization of secondary features (Thursday, 31 January)
• Re: Web Cryptography Use Cases For Review (Thursday, 31 January)
• Re: Korea Fwd: TPAC2013 in Shenzhen, China (18-22 November) (Thursday, 31 January)
• Re: Web Cryptography Use Cases For Review (Monday, 14 January)
• Password Policy and Account Lockout Policy for KeyStorage (Monday, 14 January)
• Re: Another use-case re authentication (Monday, 14 January)
• Re: Another use-case re authentication (Wednesday, 9 January)

Nadim Kobeissi

• Opera Random Numbers (Saturday, 26 January)
• Re: Test Suite on Github - need your GitHub IDs (Wednesday, 23 January)

Richard Barnes

• Re: [info] OASIS PKCS#11 WG creation (Wednesday, 30 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Wednesday, 23 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Get rid of "params"? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: W3C Web Crypto WG - take away from the 7th of Jan conf call (Tuesday, 8 January)
• PolyCrypt (Monday, 7 January)

Ryan Sleevi

• PROPOSAL: Close ISSUE-40 - How should we define key discovery, noting asynchronicity (Thursday, 31 January)
• PROPOSAL: Close ISSUE-37 - Method Naming (Thursday, 31 January)
• PROPOSAL: Close ISSUE-34 - Representation of certificates (Thursday, 31 January)
• PROPOSAL: Close ISSUE-33 - Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario (Thursday, 31 January)
• PROPOSAL: Close ISSUE-32 - API should mention the use of secure elements in the context of key security (Thursday, 31 January)
• PROPOSAL: Close ISSUE-31 - Problems with keys attribute of the Crypto interface (Thursday, 31 January)
• PROPOSAL: Close ISSUE-30 - How does the application know where the key is stored ? (Thursday, 31 January)
• PROPOSAL: Close ISSUE-29 - Handling of block encryption modes and padding (Thursday, 31 January)
• PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access (Thursday, 31 January)
• PROPOSAL: Close ISSUE-25 - How do we provision Global Unique ID for pre-provisioned symmetric keys (Thursday, 31 January)
• PROPOSAL: Close ISSUE-24 - Defining a Synchronous API (Thursday, 31 January)
• PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys (Thursday, 31 January)
• PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? (Thursday, 31 January)
• PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes (Thursday, 31 January)
• PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys (Thursday, 31 January)
• PROPOSAL: Close ISSUE-10: Making sure our API is usable with pure js environement (Thursday, 31 January)
• PROPOSAL: Close ISSUE-9 (Thursday, 31 January)
• Re: An initial editor's draft: high-level API (Tuesday, 29 January)
• Re: An initial editor's draft: high-level API (Monday, 28 January)
• Re: An initial editor's draft: high-level API (Monday, 28 January)
• Re: An initial editor's draft: high-level API (Monday, 28 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Thursday, 24 January)
• Re: IANA registry for WebCrypto? (Saturday, 19 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: IANA registry for WebCrypto? (Friday, 18 January)
• Re: Proposal for key wrap/unwrap (ISSUE-35) (Thursday, 17 January)
• Re: Password Policy and Account Lockout Policy for KeyStorage (Monday, 14 January)
• Re: Another use-case re authentication (Wednesday, 9 January)

Seetharama Rao Durbha

• Re: Another use-case re authentication (Wednesday, 9 January)

Zooko Wilcox-OHearn

• Re: W3C Web Crypto WG - no call today, but next week :) (Wednesday, 16 January)

Last message date: Thursday, 31 January 2013 19:33:09 UTC