W3C home > Mailing lists > Public > public-webcrypto@w3.org > June 2012

Re: using authenticated encryption in webcrypto

From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 18 Jun 2012 08:26:13 -0700
Message-ID: <CABcZeBPz4xZgN9qaw-Ln3Pzv_YjohFBbqgZJFJBiRid7w2Nn-Q@mail.gmail.com>
To: David McGrew <mcgrew@cisco.com>
Cc: Ryan Sleevi <sleevi@google.com>, public-webcrypto@w3.org, Kenny Paterson <Kenny.Paterson@rhul.ac.uk>
On Mon, Jun 18, 2012 at 3:40 AM, David McGrew <mcgrew@cisco.com> wrote:
> Hi Ryan,
>
> On Jun 15, 2012, at 2:27 PM, Ryan Sleevi wrote:
>
>
> David,
>
> +1 to supporting AEAD.
>
> However, I'm not sure I'd agree with the statement that simplifies the API
> any, so I was hoping you could explain.
>
>
> good question.   What I meant is that by using the same AEAD API for
> CBC-HMAC, we can provide the implementer with access to most of the
> encryption algorithms of interest through a uniform interface.  But you are
> right that as long as raw CBC is present the API is not smaller.

I'm totally in favor of supporting AEAD, but I also want to be able to
interface with systems which don't expect AEAD, so I think it's
important to support the raw primitives as well.

-Ekr
Received on Monday, 18 June 2012 15:27:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 June 2012 15:27:29 GMT