- From: Manger, James <James.H.Manger@team.telstra.com>
- Date: Mon, 30 Jan 2017 05:44:56 +0000
- To: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Random access to content via a range request is almost supported by aes128gcm, but as the draft says it "could be confounded by the presence of padding". You can decrypt, say, the 100th 1KB record, but that gives you no clue how many of the earlier 99,693 bytes are content vs padding — unless you are told. How about a flag in the padding delimiter byte that, if set, means there is no padding in earlier records? An encryptor that wants to enable random access can easily flag this in an authentic manner. A decryptor that doesn't care can easily ignore the flag. Typo in PR #283: ✗ "all other octets have a padding delimiter with the value 1" ✓ "all other records have a padding delimiter with the value 1" -- James Manger -----Original Message----- From: Martin Thomson [mailto:martin.thomson@gmail.com] Sent: Monday, 30 January 2017 3:59 PM To: HTTP Working Group <ietf-http-wg@w3.org> Subject: Change to padding in encryption Based on the discussion thus far, I've put together a PR that changes how padding works. https://github.com/httpwg/http-extensions/pull/283
Received on Monday, 30 January 2017 05:45:45 UTC