Re: [openpgp] Message padding in OpenPGP

Derek Atkins <derek@ihtfp.com> Wed, 25 September 2019 14:32 UTC

Return-Path: <derek@ihtfp.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 260D61200C5 for <openpgp@ietfa.amsl.com>; Wed, 25 Sep 2019 07:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CX61eriVTITC for <openpgp@ietfa.amsl.com>; Wed, 25 Sep 2019 07:32:44 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 313321200C4 for <openpgp@ietf.org>; Wed, 25 Sep 2019 07:32:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id E03A5E2042; Wed, 25 Sep 2019 10:32:42 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 12376-02; Wed, 25 Sep 2019 10:32:41 -0400 (EDT)
Received: from securerf.ihtfp.org (99-46-190-172.lightspeed.tukrga.sbcglobal.net [99.46.190.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (not verified)) by mail2.ihtfp.org (Postfix) with ESMTPS id 937A7E2040; Wed, 25 Sep 2019 10:32:41 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1569421961; bh=L7BtDwF1ZFppka35PCvDoa+p6zKvIItDKmh4oRVOfZ0=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=DAMTIOCVSKH+ljJhskrTvmi0R+AJCa0hxdFZBIA4eIATBQYUHkghrRsjr5JtAw5iM UPBT+lq0RjY30obwCSrQPn5XOEur4qIx7h2u79bfeOnWQ4J8nXR3U5QGusjk8+X9tg FlkmqAQkPm/xLQrUMT+rS4jWMVyPbiRJYnUonpOA=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.15.2/8.15.2/Submit) id x8PEWZ9J030268; Wed, 25 Sep 2019 10:32:35 -0400
From: Derek Atkins <derek@ihtfp.com>
To: Justus Winter <justuswinter@gmail.com>
Cc: Jon Callas <joncallas@icloud.com>, openpgp@ietf.org
References: <CA+t5QVsZoWEuDWEzGn+mWNsx+giJsq+9pYptt3TfffASBVoGsw@mail.gmail.com> <8994782B-12D6-4B91-BA7A-1BF6BF4E7951@icloud.com> <CA+t5QVs7aoyBotbApmGQBGO9otLeB9knccAV8w9MacjrcE_51w@mail.gmail.com>
Date: Wed, 25 Sep 2019 10:32:33 -0400
In-Reply-To: <CA+t5QVs7aoyBotbApmGQBGO9otLeB9knccAV8w9MacjrcE_51w@mail.gmail.com> (Justus Winter's message of "Wed, 25 Sep 2019 11:03:24 +0200")
Message-ID: <sjmblv8igzi.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/-93H_N_tq2LP51F0yNGZXR8-8H8>
Subject: Re: [openpgp] Message padding in OpenPGP
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 14:32:46 -0000

Justus Winter <justuswinter@gmail.com> writes:

> On Tue, Sep 24, 2019 at 11:00 PM Jon Callas <joncallas@icloud.com> wrote:
>> Am I correct in understanding that you're proposing adding in decoy
>> traffic to pad out compressed data to its uncompressed length?
>
> No.  I'm proposing not to compress the data at all, and then add some
> padding data according to some policy.  The compression container is
> only a means to add the padding within the constraints of the current
> ecosystem.
>
>> If I'm missing something, what problem are you trying to solve with this?
>
> There is a correlation between the size of the encrypted message and
> the size of the plaintext.  On first sight, compression helps with
> that, but that makes the size dependent on the entropy of the
> plaintext, which also leads to problems as discussed previously.
> Padding alleviates this problem, the tradeoff being an increased
> message size.

Why not just have multiple literal packets inside the encryption?  I.e.:

  ENC{ Lit1{realData} | Lit2{pad} }

Note, of course, that this could provide a covert channel which could
leak other data, theoretically.

> Cheers,
> Justus

-derek
-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant