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

[Bug 25659] AES-CBC mode does not describe concretely how padding is added

From: <bugzilla@jessica.w3.org>
Date: Mon, 12 May 2014 16:12:47 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-25659-7213-bzq2yeyQnO@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25659

Mark Watson <watsonm@netflix.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |watsonm@netflix.com

--- Comment #1 from Mark Watson <watsonm@netflix.com> ---
First, the "behave as if ..." applies to all our algorithm descriptions.
Implementors are free to do whatever they want as long as the externally
visible behavior is the same as that which would result from following the
algorithm description to the letter. I think we say this somewhere explicitly.
Anyway, we should be able to take it as read for all algorithm descriptions.

Second, I thought that by the time we get to the algorithm descriptions we are
dealing with abstract types. 'plaintext' and 'padded plaintext' are just
strings of octets, not a language-specific concrete type that contains such a
string. HOw they are stored / manipulated in memory is implementation-specific.

At least, this was my intention when drafting this text. The method
descriptions which call into the operation descriptions should say '... passing
the contents of X as *plaintext*' where X is the ArrayBufferView and so
plaintext is just the octet string.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 12 May 2014 16:12:48 UTC

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