ISSUE: Define MGF AlgorithmIdentifiers
Missing InvalidStateError when calling the CryptoOperation methods in an 'incorrect' order?
Editorial: Empty list item in section '14.1.6. The generateKey method'
Question about step 1 of section '12.4.1. process(ArrayBufferView data)'
RE: Proposal for key wrap/unwrap (ISSUE-35)
ISSUE-30: Key import/export?
Proposal to close ISSUE-7
ISSUE-19 is expecting proposal or will be postponed
ISSUE-26 is expecting proposal or will be postponed
W3C Web Crypto WG - take away of our 18th of Feb conf call
RE: ISSUE 22 - Re: Incomplete blocks
Re: An initial editor's draft: high-level API
DOM Dependency
ACTION-66
W3C Web Crypto WG - classifying issues
Incomplete blocks
Re: PROPOSAL: Close ISSUE-15: Discovering certificates associated with (private) keys
PROPOSAL: ??? ISSUE-24: Defining a synchronous API (was Re: W3C Web Crypto WG - classifying issues)
PROPOSAL: Move Issue-25: How do we provision a globally unique ID (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: Move ISSUE-30: How does the application know where the key is stored? (was Re: W3C Web Crypto WG - classifying issues)
PROPOSAL: Postpone ISSUE-34: Representation of Certificates (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 )
W3C Web Crypto WG - classifying issues
Algorithm attribute (was Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes )
3GPP liaison request - possible answer
[info] WASH13, a workshop on web application and secure hardware
W3C Web Crypto WG - regular meeting
Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- RE: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
- Re: Registries and Interoperability
Re: PROPOSAL: Close ISSUE-24 - Defining a Synchronous API
Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys
- Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys
- Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys
- Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys
- Re: PROPOSAL: Close ISSUE-19 - Does it make sense to have authorized-origin and specific-origin keys
Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?
- Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?
- Re: PROPOSAL: Close ISSUE-18: Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?
Re: PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes
trackbot can now associate ACTIONs and ISSUEs with products
W3C Web Crypto WG - agenda for our call today @ 20:00 UTC
- Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC
- Re: W3C Web Crypto WG - agenda for our call today @ 20:00 UTC
- W3C Web Crypto WG - agenda for our call on monday 18th of Feb @ 20:00 UTC
Introduction
W3C Web Crypto WG - focus on issue management during our next call
Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access
- Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access
- Re: PROPOSAL: Close ISSUE-26 - Should key generation be allowed to specify multi-origin shared access