public-webcrypto@w3.org from February 2014 by date

Friday, 28 February 2014

• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Ryan Sleevi
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Alexey Proskuryakov
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Mark Watson
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Alexey Proskuryakov
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Eric Roman
• RE: Bug 24457 - AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Jim Schaad
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Alexey Proskuryakov
• Re: Bug 24806 - Should the spec mandate a minimum key length for HMAC? Mark Watson
• RE: Bug 24813 - Decide whether methods should return DOMError or null on failure Jim Schaad
• RE: Bug 24806 - Should the spec mandate a minimum key length for HMAC? Ryan Sleevi
• RE: Bug 24806 - Should the spec mandate a minimum key length for HMAC? Jim Schaad
• Reminder : next monday @ 20:00 UTC, Q&A session to the editors GALINDO Virginie
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Mark Watson
• Re: Bug 24813 - Decide whether methods should return DOMError or null on failure Ryan Sleevi
• Bug 24813 - Decide whether methods should return DOMError or null on failure Mark Watson
• Re: Bug 23833 - Remove sequence IDL keyword from parameters that take CryptoOperationData Mark Watson
• Bug 24457 - AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mark Watson
• Re: Bug 23833 - Remove sequence IDL keyword from parameters that take CryptoOperationData Ryan Sleevi
• Bug 24806 - Should the spec mandate a minimum key length for HMAC? Mark Watson
• Bug 23833 - Remove sequence IDL keyword from parameters that take CryptoOperationData Mark Watson
• Re: Bug 24410 - AES-CBC description Mark Watson
• Re: Consider whether the others Public Value input to (EC)DH deriveKey should be a Key object Ryan Sleevi
• Re: Consider whether the others Public Value input to (EC)DH deriveKey should be a Key object Mark Watson
• Re: inconsistent references for HKDF-CTR Mark Watson
• RE: What happended to SecretAgreee? Ryan Sleevi
• RE: What happended to SecretAgreee? Jim Schaad
• Specification updates Mark Watson
• RE: What happended to SecretAgreee? Ryan Sleevi
• RE: What happended to SecretAgreee? Jim Schaad
• Re: What happended to SecretAgreee? Mark Watson

Thursday, 27 February 2014

• Re: What happended to SecretAgreee? Ryan Sleevi
• RE: What happended to SecretAgreee? Jim Schaad
• RE: What happended to SecretAgreee? Jim Schaad
• Re: What happended to SecretAgreee? Ryan Sleevi
• Re: What happended to SecretAgreee? Mark Watson
• RE: inconsistent references for HKDF-CTR Jim Schaad
• Re: What happended to SecretAgreee? Ryan Sleevi
• Re: inconsistent references for HKDF-CTR Mark Watson
• RE: What happended to SecretAgreee? Jim Schaad
• RE: Consider whether the others Public Value input to (EC)DH deriveKey should be a Key object Vijay Bharadwaj
• RE: inconsistent references for HKDF-CTR Vijay Bharadwaj
• RE: Consider whether the others Public Value input to (EC)DH deriveKey should be a Key object Jim Schaad
• Re: What happended to SecretAgreee? Ryan Sleevi
• RE: What happended to SecretAgreee? Jim Schaad
• Re: What happended to SecretAgreee? Ryan Sleevi
• What happended to SecretAgreee? Jim Schaad
• RE: inconsistent references for HKDF-CTR Jim Schaad
• RE: Bug 24410 - AES-CBC description Jim Schaad
• inconsistent references for HKDF-CTR Mark Watson

Wednesday, 26 February 2014

• Re: Why is the derivedKeyType parameter to deriveKey nullable ? Ryan Sleevi
• Re: Define how keys are derived from secret values for deriveKey Mark Watson
• Re: Define how keys are derived from secret values for deriveKey Mark Watson
• Consider whether the others Public Value input to (EC)DH deriveKey should be a Key object Mark Watson
• Why is the derivedKeyType parameter to deriveKey nullable ? Mark Watson
• Re: Bug 24410 - AES-CBC description Ryan Sleevi
• Re: Bug 24410 - AES-CBC description Mark Watson
• Re: Define how keys are derived from secret values for deriveKey Ryan Sleevi
• Re: Define how keys are derived from secret values for deriveKey Mark Watson
• Re: Define how keys are derived from secret values for deriveKey Ryan Sleevi
• RE: Define how keys are derived from secret values for deriveKey Vijay Bharadwaj
• Re: Define how keys are derived from secret values for deriveKey Mark Watson

Tuesday, 25 February 2014

• Re: Define how keys are derived from secret values for deriveKey Ryan Sleevi
• Re: Define how keys are derived from secret values for deriveKey Mark Watson
• Re: SPKI export needs additional parameter Ryan Sleevi
• RE: SPKI export needs additional parameter Jim Schaad
• Re: Define how keys are derived from secret values for deriveKey Ryan Sleevi
• Define how keys are derived from secret values for deriveKey Mark Watson
• Re: Copying bugs to the mailing list Harry Halpin
• Re: Copying bugs to the mailing list Ryan Sleevi
• Re: Copying bugs to the mailing list Harry Halpin
• Re: SPKI export needs additional parameter Ryan Sleevi
• RE: SPKI export needs additional parameter Vijay Bharadwaj
• SPKI export needs additional parameter Jim Schaad
• WorkerCrypto interface concerns from Microsoft Israel Hilerio
• RE: Support optional private value length for DH PKCS#3 ? Ryan Sleevi
• RE: Support optional private value length for DH PKCS#3 ? Vijay Bharadwaj
• Re: Support optional private value length for DH PKCS#3 ? Mark Watson
• RE: Support optional private value length for DH PKCS#3 ? Vijay Bharadwaj
• Support optional private value length for DH PKCS#3 ? Mark Watson

Monday, 24 February 2014

• Copying bugs to the mailing list Ryan Sleevi
• Meeting minutes for Feb 24th telecon Harry Halpin
• Re: Bug # 24410 - AES CTR descriptions Ryan Sleevi
• RE: Bug # 24410 - AES CTR descriptions Vijay Bharadwaj
• RE: WebCrypto @ Korea WWW2014 - need help/talks 조상래
• Re: Bug # 24410 - AES CTR descriptions Ryan Sleevi
• Mail list archives & formatting of messages Ryan Sleevi
• RE: Bug # 24410 - AES CTR descriptions Vijay Bharadwaj
• Re: Diffie-Hellman question Mark Watson
• RE: Diffie-Hellman question Jim Schaad
• Re: Diffie-Hellman question Ryan Sleevi
• Re: Diffie-Hellman question Mark Watson
• Re: Diffie-Hellman question Ryan Sleevi
• Re: Bug # 24410 - AES CTR descriptions Ryan Sleevi
• Re: Diffie-Hellman question Mark Watson
• RE: AES CFB input parameter "s" Ryan Sleevi
• RE: Bug # 24410 - AES CTR descriptions Vijay Bharadwaj
• RE: W3C Web Crypto WG - progressing on ISSUE-36 Vijay Bharadwaj
• RE: AES CFB input parameter "s" Vijay Bharadwaj
• Re: WebCrypto @ Korea WWW2014 - need help/talks Harry Halpin
• Re: WebCrypto @ Korea WWW2014 - need help/talks Mountie Lee
• WebCrypto @ Korea WWW2014 - need help/talks Harry Halpin

Sunday, 23 February 2014

• RE: Bug 20611 - specify JWK encoding as UTF-8 Mike Jones
• RE: Bug 20611 - specify JWK encoding as UTF-8 Jim Schaad

Friday, 21 February 2014

• RE: Diffie-Hellman question Jim Schaad
• RE: Diffie-Hellman question Jim Schaad
• RE: Bug 20611 - specify JWK encoding as UTF-8 Mike Jones
• Re: Diffie-Hellman question Ryan Sleevi
• Re: Importing self-identifying JWKs Ryan Sleevi
• Diffie-Hellman question Mark Watson
• Re: Importing self-identifying JWKs Mark Watson
• Re: Bug # 24410 - AES CTR descriptions Mark Watson
• Re: Bug 24410 - AES-GCM Mark Watson
• Re: AES-CMAC - MAC lengths other than 128 Mark Watson
• Re: AES-CMAC - MAC lengths other than 128 Richard Barnes
• Re: AES-CMAC - MAC lengths other than 128 Ryan Sleevi
• Re: AES-CMAC - MAC lengths other than 128 Richard Barnes
• W3C Web Crypto WG - reminder : calls on the 24th of February @ 09:00 UTC *and* 20:00 UTC GALINDO Virginie
• Re: Importing self-identifying JWKs Mark Watson
• RE: Bug 24410 - AES-GCM Jim Schaad
• RE: Importing self-identifying JWKs Jim Schaad
• AES-CMAC - MAC lengths other than 128 Jim Schaad
• Re: Importing self-identifying JWKs Richard Barnes
• Re: Importing self-identifying JWKs Ryan Sleevi
• Bug 20611 - specify JWK encoding as UTF-8 Jim Schaad
• Re: Importing self-identifying JWKs Richard Barnes
• Bug 24410 - AES-GCM Jim Schaad
• Re: Bug 24410 - AES-CBC description Mark Watson
• Re: Bug 24755 - Decide which AES-CFB shift sizes to support Mark Watson
• Importing self-identifying JWKs Mark Watson
• RE: Bug 24755 - Decide which AES-CFB shift sizes to support Jim Schaad
• RE: Bug 24755 - Decide which AES-CFB shift sizes to support Jim Schaad
• Bug 24410 - AES-CBC description Jim Schaad
• Re: Bug # 24410 - AES CTR descriptions Mark Watson
• RE: Bug # 24410 - AES CTR descriptions Jim Schaad

Thursday, 20 February 2014

• Re: Bug 24457 - AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Richard Barnes
• Re: Bug # 24410 - AES CTR descriptions Mark Watson
• Bug # 24410 - AES CTR descriptions Jim Schaad
• Bug 24755 - Decide which AES-CFB shift sizes to support Mark Watson
• RE: Bug 24457 - AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Jim Schaad
• RE: Bug #23500 - Raw AES Access Jim Schaad
• Re: Bug #23500 - Raw AES Access Mark Watson
• Bug 24457 - AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mark Watson
• RE: Bug #23500 - Raw AES Access Mike Jones
• Re: Bug #23500 - Raw AES Access Richard Barnes
• Re: Bug #23500 - Raw AES Access Mark Watson
• Editors' Draft update Mark Watson

Wednesday, 19 February 2014

• Bug #23500 - Raw AES Access Jim Schaad

Monday, 17 February 2014

• W3C Web Crypto WG - regular conf call (WG participants only) GALINDO Virginie
• W3C Web Crypto WG - regular conf call (WG participants only) GALINDO Virginie
• W3C Web Crypto WG - regular conf call (WG participants only) GALINDO Virginie

Saturday, 15 February 2014

• Re: AES CFB input parameter "s" Mark Watson
• Re: AES CFB input parameter "s" Ryan Sleevi
• Re: AES CFB input parameter "s" Mark Watson
• Re: AES CFB input parameter "s" Ryan Sleevi
• Re: AES CFB input parameter "s" Mark Watson

Friday, 14 February 2014

• Re: AES CFB input parameter "s" Ryan Sleevi
• AES CFB input parameter "s" Mark Watson
• W3C Web Crypto WG - Future work : straw man proposal for a workshop on hardware token and secure services GALINDO Virginie
• Re: W3C Web Crypto WG - cancelling London F2F meeting on 27th of Feb Harry Halpin
• W3C Web Crypto WG - cancelling London F2F meeting on 27th of Feb GALINDO Virginie

Thursday, 13 February 2014

• RE: Removing SHA-224 GALINDO Virginie
• Re: Removing SHA-224 Bruno Oliveira
• Re: Removing SHA-224 Ryan Sleevi
• Re: Removing SHA-224 Ryan Sleevi
• Re: W3C Web Crypto WG - moving to github in the future ? Ryan Sleevi
• Re: W3C Web Crypto WG - moving to github in the future ? Harry Halpin
• W3C Web Crypto WG - moving to github in the future ? GALINDO Virginie
• W3C Web Crypto WG - take away from 10th of Feb call GALINDO Virginie
• Re: Removing SHA-224 Harry Halpin
• Re: Removing SHA-224 Bruno Oliveira
• Removing SHA-224 Ryan Sleevi
• Re: Algorithm aliasing and JWK algorithm names Ryan Sleevi
• Re: EC Point Representations Ryan Sleevi
• Re: ISSUE-44 and ISSUE-46 Ryan Sleevi
• ISSUE-44 and ISSUE-46 Richard Barnes

Wednesday, 12 February 2014

• Re: will the key reference available sent via postMessage? Ryan Sleevi
• will the key reference available sent via postMessage? Mountie Lee

Tuesday, 11 February 2014

• Minutes for WebCrypto Feb 10th meeting Harry Halpin
• W3C Web Crypto WG - F2F meeting in London on 27th of Feb - please register GALINDO Virginie
• RE: Key Ownership and SOP exception GALINDO Virginie
• Re: Key Ownership and SOP exception Ryan Sleevi

Monday, 10 February 2014

• Key Ownership and SOP exception Mountie Lee
• Workshop around hardware tokens/FIDO - suggested dates and times Harry Halpin
• Re: W3C Web Crypto WG - agenda for our next call Harry Halpin
• W3C Web Crypto WG - Reminder : we have our regular call today @ 20:00 GALINDO Virginie
• W3C Web Crypto WG - asian call take awayo 10th of february GALINDO Virginie
• Fwd: Update on Streams API Status Aymeric Vitte
• W3C Web Crypto WG - alternative details for the asia call GALINDO Virginie
• W3C Web Crypto WG - Reminder : call with asia today @9:00 UTC GALINDO Virginie

Saturday, 8 February 2014

• Re: Current status of pre-Last Call bugs Mark Watson
• Re: Current status of pre-Last Call bugs Ryan Sleevi
• Re: Current status of pre-Last Call bugs Mark Watson

Friday, 7 February 2014

• W3C DOM4 is in Last Call GALINDO Virginie
• Re: Current status of pre-Last Call bugs Mark Watson
• Current status of pre-Last Call bugs Mark Watson

Thursday, 6 February 2014

• Copying bugs to mailing list Mark Watson
• Bug 24427 - make all errors asynchronous Mark Watson

Wednesday, 5 February 2014

• RE: To wrap or to wrapKey ?? Mike Jones
• W3C Web Crypto WG - agenda for our next call GALINDO Virginie
• W3C Web Crypto WG - Conceal : a high level API for android (by Facebook) GALINDO Virginie
• Re: To wrap or to wrapKey ?? Ryan Sleevi
• To wrap or to wrapKey ?? Mark Watson

Monday, 3 February 2014

• W3C Web Crypto WG - London 27th of February informal F2F meeting : please register GALINDO Virginie
• Re: W3C Web Crypto WG - Asian call delay to 10th of Feb @ 09:00 UTC Harry Halpin
• W3C Web Crypto WG - Asian call delay to 10th of Feb @ 09:00 UTC GALINDO Virginie
• Re: W3C Web Crypto WG - Asian call next monday 3rd of Feb @ 09:00 UTC Harry Halpin
• Re: W3C Web Crypto WG - Asian call next monday 3rd of Feb @ 09:00 UTC Mountie Lee

Saturday, 1 February 2014

• RE: Registered algorithm vs supported algorithm Jim Schaad
• Re: Algorithm aliasing and JWK algorithm names Alexey Proskuryakov
• EC Point Representations Jim Schaad
• Re: Registered algorithm vs supported algorithm Ryan Sleevi
• Registered algorithm vs supported algorithm Jim Schaad
• Algorithm aliasing and JWK algorithm names Jim Schaad
• Re: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Ryan Sleevi
• RE: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mike Jones
• Re: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Ryan Sleevi
• RE: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mike Jones
• Re: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Ryan Sleevi
• RE: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mike Jones
• Re: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mark Watson
• RE: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mike Jones
• Re: AES-KW can only wrap a JWK key if its serialization happens to be 8*n bytes long Mark Watson

Last message date: Friday, 28 February 2014 20:26:28 UTC