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

Re: Bug 23159 - Inconsistent "length" property when generating keys (bits vs bytes)

From: Mark Watson <watsonm@netflix.com>
Date: Mon, 3 Mar 2014 16:13:55 -0800
Message-ID: <-3102196288215447094@unknownmsgid>
To: Richard Barnes <rlb@ipv.sx>
Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Yes, well, since HMAC is the odd one out, it seemed changing that might be
simpler from the point of view of all the existing implementations, test
suites etc. Also, it's more common to refer to the number of bits in a key
(e.g AES-128) than bytes. In those cases you have to check for specific
values 128, 192, 256, not just for byte alignment.

So, I still prefer bits.

...Mark



Sent from my iPhone

On Mar 3, 2014, at 3:59 PM, Richard Barnes <rlb@ipv.sx> wrote:

Agree we should be uniform.  Typed arrays are all byte oriented, so it
seems like aligning on BYTES (literally) would result in less ambiguity.
Otherwise you have to say how you pack left over bits.



On Monday, March 3, 2014, Mark Watson <watsonm@netflix.com> wrote:

> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23159
>
> The length property of an algorithm is everywhere specified as the length
> in BITS, except HMAC which defines it as the length in BYTES.
>
> The proposal is to align on BITS.
>
> Any objections ?
>
> ...Mark
>
Received on Tuesday, 4 March 2014 00:14:23 UTC

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