W3C home > Mailing lists > Public > public-webcrypto@w3.org > May 2014

Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug

From: Ryan Sleevi <sleevi@google.com>
Date: Sun, 11 May 2014 18:36:42 -0700
Message-ID: <CACvaWvaFnvuDFH0P=5wKdNRBOvQ_B=iA28VNGWrDarDUe52rFg@mail.gmail.com>
To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Harry Halpin <hhalpin@w3.org>
Virginie,

Can you please comment on what you mean by "Blocking Bug"? That has a very
specific connotation within the W3C process.


On Fri, May 9, 2014 at 6:12 AM, GALINDO Virginie <
Virginie.GALINDO@gemalto.com> wrote:

>  Hi all,
>
> This is just to bring your attention on the fact that we received a
> “blocking bug” from Rich Salz and Kenny Patterson about the need to improve
> our security considerations in *Bug 25607* [1]
>
> Ryan is working on it, but views/support from all implementers would be
> helpful …
>
> Regards,
>
> Virginie
>
>
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25607
>
>
>
>
>
> ------------------------------
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus
>
Received on Monday, 12 May 2014 01:37:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:22 UTC