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

3GPP liaison request - possible answer

[info] WASH13, a workshop on web application and secure hardware

ACTION-66

Algorithm attribute (was Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes )

An initial editor's draft: high-level API

DOM Dependency

Editorial: Empty list item in section '14.1.6. The generateKey method'

Incomplete blocks

Introduction

ISSUE 22 - Re: Incomplete blocks

ISSUE-19 is expecting proposal or will be postponed

ISSUE-26 is expecting proposal or will be postponed

ISSUE-30: Key import/export?

ISSUE: Define MGF AlgorithmIdentifiers

Making choices for developers (Re: Incomplete blocks)

Missing InvalidStateError when calling the CryptoOperation methods in an 'incorrect' order?

Proposal for key wrap/unwrap (ISSUE-35)

Proposal to close ISSUE-7

PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues)

PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys

PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes

PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?

PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys

PROPOSAL: Close ISSUE-24 - Defining a Synchronous API

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

PROPOSAL: CLOSE ISSUE-40: How should we define key discovery, noting asynchronicity

PROPOSAL: Move Issue-25: How do we provision a globally unique ID (was Re: W3C Web Crypto WG - classifying issues)

PROPOSAL: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues)

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

PROPOSAL: Postpone ISSUE-26: Should key generation be allowed to specify multi-origin access (was Re: W3C Web Crypto WG - classifying issues)

PROPOSAL: Postpone ISSUE-34: Representation of Certificates (was Re: W3C Web Crypto WG - classifying issues)

Question about step 1 of section '12.4.1. process(ArrayBufferView data)'

Registries and Interoperability

trackbot can now associate ACTIONs and ISSUEs with products

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

W3C Web Crypto WG - agenda for our call today @ 20:00 UTC

W3C Web Crypto WG - classifying issues

W3C Web Crypto WG - focus on issue management during our next call

W3C Web Crypto WG - regular meeting

W3C Web Crypto WG - take away of our 18th of Feb conf call

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