Re: [TLS] padding

Russ Housley <> Sat, 22 August 2015 19:37 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 762561B2C9F for <>; Sat, 22 Aug 2015 12:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -99.2
X-Spam-Status: No, score=-99.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id C8_svWrOVaoI for <>; Sat, 22 Aug 2015 12:37:04 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 04B311ACD47 for <>; Sat, 22 Aug 2015 12:37:04 -0700 (PDT)
Received: from localhost (unknown []) by (Postfix) with ESMTP id E7AA5F24129; Sat, 22 Aug 2015 15:36:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3lCssatQ7xkE; Sat, 22 Aug 2015 15:35:35 -0400 (EDT)
Received: from [] ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTP id 323C4F24128; Sat, 22 Aug 2015 15:36:32 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <>
In-Reply-To: <>
Date: Sat, 22 Aug 2015 15:36:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: Dave Garrett <>
X-Mailer: Apple Mail (2.1085)
Archived-At: <>
Subject: Re: [TLS] padding
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 22 Aug 2015 19:37:05 -0000


> On Sunday, May 17, 2015 05:29:51 pm Tom Ritter wrote:
>> On 17 May 2015 at 14:32, Dave Garrett <> wrote:
>>> Is it really necessary to have a separate application_data_padded content type? It'd be simpler to just keep using existing types but amend it with a padding field and require it always be used at minimum to pad up to the nearest multiple of N-bytes. (something low for the default) Additional padding would be optional, but all data would get some minimum.
>> That was the first proposal, but the extra bytes on every message for
>> people who weren't using padding were deemed to be prohibitive.
> Wouldn't it be simpler to just have an optional padding vector that exists only if padding is negotiated? (we already have one optional field with extensions in the hello messages)
> A simple method to negotiate would be to add a new HandshakeType with a couple flags, one to indicate that the endpoint will be sending padded messages and another to indicate that it's willing to receive padded messages. Endpoints could declare padding with this message and use it until its peer sends a message requesting otherwise. This sort of scenario would have the additional benefit of not stating the existence of padding in the clear.

I like the idea that the presence or absence of padding in the ciphertext is hidden in your proposal.  Is there really an need to toggle it on and off?