Sunday, 30 September 2012
Friday, 28 September 2012
- RE: [event] Internet Identity Workshop XV in Mountain View - CA on 23/25 Oct
- [event] Internet Identity Workshop XV in Mountain View - CA on 23/25 Oct
- Re: Suggestions on high-level API - perhaps a meeting next week?
Thursday, 27 September 2012
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Re: Suggestions on high-level API - perhaps a meeting next week?
- Suggestions on high-level API - perhaps a meeting next week?
Wednesday, 26 September 2012
- Re: Support for ECB - proposal for a decision
- Re: Support for ECB - proposal for a decision
- Re: Support for ECB - proposal for a decision
Monday, 24 September 2012
- Re: Support for ECB - proposal for a decision
- Re: Suggestions on high-level API - perhaps a meeting next week?
- W3C WebCrypto meeting minutes
- Suggestions on high-level API - perhaps a meeting next week?
- Re: Privacy Interest Group to review Web Crypto API - a draft
- Re: W3C Web Crypto WG - agenda for 24th of september call - today
- Re: On specifying algorithms
- Re: On specifying algorithms
- RE: Support for ECB - proposal for a decision
- W3C Web Crypto WG - agenda for 24th of september call - today
- [W3C Web Crypto WG] a post on our API
- RE: On specifying algorithms
- RE: feedback from CFRG
- Support for ECB - proposal for a decision
Saturday, 22 September 2012
Friday, 21 September 2012
- Re: W3C Web Crypto - classifying issues - a new proposal
- RE: W3C Web Crypto - classifying issues - a new proposal
- Re: W3C Web Crypto - classifying issues - a new proposal
- On specifying algorithms
Thursday, 20 September 2012
- Re: feedback from CFRG
- Re: feedback from CFRG
- Re: Privacy Interest Group to review Web Crypto API - a draft
- feedback from CFRG
- Privacy Interest Group to review Web Crypto API - a draft
Wednesday, 19 September 2012
- W3C Web Crypto WG - 3GPP & Usage of GBA from the browser
- RE: W3C Web Crypto WG - Is our deliverable doomed ?
Tuesday, 18 September 2012
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- W3C - TPAC 2012 Plenary Schedule (and other reminders)
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: Non Repudiation via WebCrypto API
- Re: W3C Web Crypto WG - blog post
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- Re: Non Repudiation via WebCrypto API
- W3C Web Crypto WG - blog post
- Re: W3C Web Crypto WG - Is our deliverable doomed ?
- W3C Web Crypto - classifying issues - a new proposal
- W3C Web Crypto WG - Is our deliverable doomed ?
- W3C Web Crypto WG - Take Away from 17th of september call
- RE: suggest to move weekly concall time from UTC 19:00 to different time.
- RE: suggest to move weekly concall time from UTC 19:00 to different time.
- Re: Non Repudiation via WebCrypto API
- Non Repudiation via WebCrypto API
Monday, 17 September 2012
- [minutes] Re: W3C Web Crypto WG - agenda for 17th of september call - today
- ISSUE-40: How should we define key discovery, noting asynchronicity
- Re: Support for ECB
- Re: Quotes for blogpost over WebCrypto
- RE: Quotes for blogpost over WebCrypto
- Re: Quotes for blogpost over WebCrypto
- Quotes for blogpost over WebCrypto
- W3C Web Crypto WG - agenda for 17th of september call - today
Saturday, 15 September 2012
Friday, 14 September 2012
- Re: Support for ECB
- Re: Support for ECB
- Re: Support for ECB
- Re: Support for ECB
- RE: Support for ECB
- Re: Support for ECB
- RE: Support for ECB
- Call for Exclusions: Web Cryptography API (from: ij@w3.org)
Thursday, 13 September 2012
- Re: Support for ECB
- RE: Support for ECB
- Re: Support for ECB
- Re: Support for ECB
- Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
- Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
- Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
- Re: Support for ECB
- Re: Support for ECB
- RE: Support for ECB
- Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
- Re: Support for ECB
- Re: Support for ECB
- RE: [W3C Web Crypto WG] FPWD Web Crypto API - available
- [W3C Web Crypto WG] FPWD Web Crypto API - available
- W3C Web Crypto WG - Take Away from the 10th of Sept conference call
- [W3C Web Crypto WG] Request transition for FPWD on Web Crypto API - approved
Wednesday, 12 September 2012
Tuesday, 11 September 2012
Monday, 10 September 2012
- [minutes] Re: W3C Web Crypto WG - 10th of september call -
- Re: JS code examples for ACTION 43
- Fwd: [therightkey] Certificate Transparency WG
- Re: Support for ECB
- Re: Support for ECB
- Re: W3C Web Crypto - status on pending ISSUE-3 related to algo discovery ?
- Re: W3C Web Crypto - status on pending ISSUE-3 related to algo discovery ?
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: Support for ECB
- Re: W3C Web Crypto WG - closing actions 13/38/44/39/43 - proposal
- W3C Web Crypto WG - agenda for 10th of september call - today
- Re: W3C Web Crypto WG - closing actions 13/38/44/39/43 - proposal
- W3C Web Crypto WG - closing actions 13/38/44/39/43 - proposal
- W3C Web Crypto - status on pending ISSUE-3 related to algo discovery ?
- W3C Web Crypto WG - Support for ECB
Saturday, 8 September 2012
Friday, 7 September 2012
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- RE: [+SPAM+]: Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: Use Cases | ACTION-13 Revisited
- Re: Use Cases | ACTION-13 Revisited
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
- Re: Use Cases | ACTION-13 Revisited
- Re: crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
- Re: Use Cases | ACTION-13 Revisited
- RE: Use Cases | ACTION-13 Revisited
- RE: Use Cases | ACTION-13 Revisited
- Re: Use Cases | ACTION-13 Revisited
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: JS code examples for ACTION 43
- RE: JS code examples for ACTION 43
- RE: JS code examples for ACTION 43
- RE: Use Cases | ACTION-13 Revisited
- RE: Support for ECB
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
- Re: Key id
- Re: JS code examples for ACTION 43
Thursday, 6 September 2012
- crypto-ISSUE-39: Add abort() to the KeyOperation interface [Web Cryptography API]
- W3C Web Crypto WG - Take Away from the 4th of Sept conference call
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: Inclusion of rsaes-pkcs1
- ArrayBuffer v ArrayBufferView (was JS examples)
- Re: JS code examples for ACTION 43
- Re: Inclusion of rsaes-pkcs1
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
Wednesday, 5 September 2012
Thursday, 6 September 2012
- Re: ISSUE-17: Key Attributes - Proposed resolution
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: ISSUE-17: Key Attributes - Proposed resolution
- Re: JS code examples for ACTION 43
Wednesday, 5 September 2012
- Re: JS code examples for ACTION 43
- Re: JS code examples for ACTION 43
- Re: ISSUE-17: Key Attributes - Proposed resolution
- Re: Use Cases | ACTION-13 Revisited
- Re: JS code examples for ACTION 43
- JS code examples for ACTION 43
- Re: Use Cases | ACTION-13 Revisited
- Re: Support for ECB
- Re: Inclusion of rsaes-pkcs1
- Re: Inclusion of rsaes-pkcs1
- Inclusion of rsaes-pkcs1
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Re: adding SEED cryptography algorithm
- Re: ISSUE-17: Key Attributes - Proposed resolution
- Re: adding SEED cryptography algorithm
- Re: Key id
- Re: Use Cases | ACTION-13 Revisited
- Re: Use Cases | ACTION-13 Revisited
Tuesday, 4 September 2012
- Re: Use Cases | ACTION-13 Revisited
- Re: [W3C Web Crypto WG] comment on API draft section 5.4
- Re: Use Cases | ACTION-13 Revisited
- Re: crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
- Re: Key id
- Draft minutes, 9/4 call
- Re: Use Cases | ACTION-13 Revisited
- Re: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- Key id
- Re: New Editor's Draft Published
- Code: 83263 / Re: W3C Web Crypto WG - agenda for 4th of sept call - today
- RE: New Editor's Draft Published
- [W3C Web Crypto WG] comment on API draft section 5.4
- Re: ISSUE-17: Key Attributes - Proposed resolution
- Re: ISSUE-17: Key Attributes - Proposed resolution
- W3C Web Crypto WG - agenda for 4th of sept call - today
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- RE: crypto-ISSUE-37: Method naming [Web Cryptography API]
- RE: crypto-ISSUE-21: Requiring Content-Security-Policy [Web Cryptography API]
- RE: crypto-ISSUE-38: Key initialization and "finalization" [Web Cryptography API]
- RE: crypto-ISSUE-31: Problems with keys attribute of the Crypto interface [Web Cryptography API]
- RE: (Minor) New version published
- RE: ISSUE-17: Key Attributes - Proposed resolution
- RE: Support for ECB
- RE: Use Cases | ACTION-13 Revisited
- RE: ISSUE-17: Key Attributes - Proposed resolution
- RE: crypto-ISSUE-27 (aes ctr): Specification of AES-CTR mode counter bits [Web Cryptography API]
- RE: crypto-ISSUE-30 (where is the key ?): How does the application know where the key is stored ? [Web Cryptography API]
- Regrets for today's meeting
Monday, 3 September 2012
Saturday, 1 September 2012
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]
- Re: adding SEED cryptography algorithm
- Re: crypto-ISSUE-17: Define the scope and API for custom key attributes [Web Cryptography API]