- From: Manger, James <James.H.Manger@team.telstra.com>
- Date: Sun, 12 Feb 2017 23:41:35 +0000
- To: Martin Thomson <martin.thomson@gmail.com>, Julian Reschke <julian.reschke@gmx.de>
- CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
The padding scheme has also been updated (from <padlen><data><0..> to <data><1|2><0...>). So you need new code, Julian. -----Original Message----- From: Martin Thomson [mailto:martin.thomson@gmail.com] Sent: Monday, 13 February 2017 10:32 AM To: Julian Reschke <julian.reschke@gmx.de> Cc: 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 06:47, Julian Reschke <julian.reschke@gmx.de> wrote: > FWIW, I was able to reproduce the examples with the updated code in > <https://gist.github.com/reschke/46659c912b426dffeac41d9a21421c95>, modulo > the change Martin mentioned (but which I don't see in Git). 'twas on a branch. I've merged that now. > WRT > <https://greenbytes.de/tech/webdav/draft-ietf-httpbis-encryption-encoding-06.html#rfc.section.3.2>: > it would be good if the prose mentioned that this specifies a keyid of "a1" > in the header. Also on said branch :)
Received on Sunday, 12 February 2017 23:42:17 UTC