W3C Web Crypto WG - discussing the web security model
W3C Web Crypto WG - Take away from San Jose F2F meeting - april 2012
basic principle of key ownership
- RE: basic principle of key ownership
- RE: basic principle of key ownership
- Re: basic principle of key ownership
RE: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams
ISSUE-35 - Wrap/Unwrap - Why JOSE?
Re: ISSUE-35 - Use cases for Wrap/Unwrap - TOFU
W3C Web Crypto WG - regular call (WG participants only)
W3C Web Crypto WG - Our next conference calls
ISSUE-35 - Use cases for Wrap/Unwrap
who own the key?
Named key discovery questions
Updated spec examples with Futures
W3C Web Crypto F2F April meeting - minutes
W3C Web Crypto WG - Wednesday afternoon agenda
do we need secure removal function for keys in low level API?
- Re: do we need secure removal function for keys in low level API?
Use case: Authenticate using eID
Use case: Document signing (using legally binding signatures)
Web Certificate API latest draft
W3C Web Crypto WG - wednesday 25th of April agenda update - starting at 8:30
Testing infrastruture docs and links
W3C Web Crypto WG - wednesday 25th of April agenda update
crypto-ISSUE-44: Require creation of random IVs by default for CBC, CFB, GCM
crypto-ISSUE-43: Separate method for key agreement [design for Web Crypto API]
On a Futures-style API
Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams
Re: Editorial: Empty list item in section '14.1.6. The generateKey method'
PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters?
W3C Web Crypto WG - location and agenda of our F2F meeting next week
- RE: W3C Web Crypto WG - location and agenda of our F2F meeting next week
- Re: W3C Web Crypto WG - location and agenda of our F2F meeting next week
W3C Web Crypto WG - reception on wednesday 24th of April in Paypal from 5 to 7 PM
WebCrypto Key Discovery: mark non-normative sections as such
crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API]
GCM ciphertext + tag ambiguity
- Re: GCM ciphertext + tag ambiguity
- Re: GCM ciphertext + tag ambiguity
- RE: GCM ciphertext + tag ambiguity
Defaults issues with AES-GCM
Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- RE: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
- Re: Defaults: Getting concrete (round 2)
Minutes of our April 15th 2013 telecon
W3C Web Crypto WG - agenda for our F2F meeting
Fwd: some input on API
W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC
[W3C Web Crypto WG] testing activities
TPAC2013 in Shenzhen, China, 11-15 November 2013 - book your week !
Call for Exclusions (Update): WebCrypto Key Discovery
WebCrypto API TLS/SSL Use Case + start of a TLS/SSL proposal.
[W3C WebCrypto API WG] Key discovery
- Re: [W3C WebCrypto API WG] Key discovery
[W3C Web Crypto WG] About import/export
[W3C Web Crypto API] PROPOSAL : closing ISSUE-32 (API should mention the use of secure elements in the context of key security)
[W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable)
- Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable)
- Re: [W3C Web Crypto WG] PROPOSAL to close ISSUE-22 (Should CryptoOperations be clonable)
[W3C Web Crypto WG] PROPOSAL: Close ISSUE-17 (Define the scope and API for custom key attributes)
[W3C Web Crypto WG] Proposal to close ISSUE-7
Session with WebAppSec WG in San Jose ?
W3C Web Crypto WG - draft minutes of our call 1st of April 2013
Re: On Crypto API Safety in the Hands of Unskilled Developers
Socializing the high level API during our F2F meeting in April
- Re: Socializing the high level API during our F2F meeting in April
- Re: Socializing the high level API during our F2F meeting in April
RE: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations
- Re: AlgorithmIdentifier in encrypt/decrypt/sign/verify operations
RE: On Crypto API Safety in the Hands of Unskilled Developers
Fwd: [Moderator Action] Missing items in KeyUsage
- Re: [Moderator Action] Missing items in KeyUsage
- Re: [Moderator Action] Missing items in KeyUsage
- RE: [Moderator Action] Missing items in KeyUsage
W3C Web Crypto WG - regular meeting
Defaults: Getting concrete
Separate method for key agreement?
- Re: Separate method for key agreement?
Potential contradiction in HKDF?
crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API]
- Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API]
- Re: crypto-ISSUE-41: Clean up algorithm normalization and support checks [design for Web Crypto API]
Fwd: [jose] jose interim meeting planned (advance announcement)
- Re: [jose] jose interim meeting planned (advance announcement)
- Re: [jose] jose interim meeting planned (advance announcement)