- From: Mitch Zollinger <mzollinger@netflix.com>
- Date: Sat, 9 Jun 2012 14:06:22 -0700
- To: Eric Rescorla <ekr@rtfm.com>
- CC: Wan-Teh Chang <wtc@google.com>, David Dahl <ddahl@mozilla.com>, <public-webcrypto@w3.org>
On 6/8/2012 9:15 PM, Eric Rescorla wrote: > On Fri, Jun 8, 2012 at 5:48 PM, Wan-Teh Chang<wtc@google.com> wrote: >> On Thu, Jun 7, 2012 at 8:26 PM, David Dahl<ddahl@mozilla.com> wrote: >>> I think so. We do need to figure out just how flexible this mechanism should be. Perhaps the key handle object you get back has properties like: >>> >>> kh.mode >>> kh.padding >>> kh.algorithm >> An AES key can be used in different modes of operation and with >> different padding schemes, so 'mode' and 'padding' aren't properties >> of a key unless we artificially constrain the key. > It seems like they might be if the key was embedded in a piece of > hardware which had a limited mode set, e.g, one which supported > only CBC and not GCM. +1 We're working with hardware right now that supports ECB & CBC but no CTR, for example. Mitch > > -Ekr >
Received on Saturday, 9 June 2012 21:06:52 UTC