On Monday, September 21, 2015 03:02:47 am Daniel Kahn Gillmor wrote:
> encrypted content type:
> ---
>
> https://github.com/tlswg/tls13-spec/pull/51
Basing the padding PR(s) on top of this might be a good idea, seeing as it's
desired to do this correctly.
One thought about d
On Mon 2015-09-21 04:43:27 -0700, Watson Ladd wrote:
> Is this actually true in the second pull request? No: a moment of
> actually reading reveals that the string is inside an AEAD encrypted
> packet. There is no way in which this padding could be modified for
> use in a side-channel attack.
In
On Mon, Sep 21, 2015 at 3:19 AM, Jeffrey Walton wrote:
> On Mon, Sep 21, 2015 at 3:02 AM, Daniel Kahn Gillmor
> wrote:
>> Hey TLS folks--
>>
>> apologies for the delay in sending these pull requests.
>>
>> encrypted content type:
>> ---
>>
>> https://github.com/tlswg/tls13-spe
Hey TLS folks--
apologies for the delay in sending these pull requests.
encrypted content type:
---
https://github.com/tlswg/tls13-spec/pull/51
This should be uncontroversial, and just needed freshening against the
current draft.
padding:
We're now proposing that
