- From: Manger, James <James.H.Manger@team.telstra.com>
- Date: Thu, 16 Feb 2017 01:11:43 +0000
- To: Daurnimator <quae@daurnimator.com>
- CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
8bit data is perfectly fine. All zeros *from the end back to the padding delimiter byte* are padding. Bytes before the padding delimiter byte can be anything (including zero). -----Original Message----- From: Daurnimator [mailto:quae@daurnimator.com] Sent: Thursday, 16 February 2017 12:07 PM To: Martin Thomson <martin.thomson@gmail.com> Cc: Julian Reschke <julian.reschke@gmx.de>; Manger, James <James.H.Manger@team.telstra.com>; ietf-http-wg@w3.org Subject: Re: aes128gcm: is the 1st example wrong? On 13 February 2017 at 19:53, Martin Thomson <martin.thomson@gmail.com> wrote: > On 13 February 2017 at 19:09, Julian Reschke <julian.reschke@gmx.de> wrote: >> So... where do I get the padding length from under the new format? > > > You count from the end of the plaintext. All the zeros are padding. > The first non-zero octet (starting from the end) is the end of the > padding and should be 0x01 (regular) or 0x02 (last record). Disallowing 8bit data seems undesireable.
Received on Thursday, 16 February 2017 01:12:29 UTC