Re: [openpgp] Padding packets

Werner Koch <wk@gnupg.org> Thu, 16 June 2022 07:00 UTC

Return-Path: <wk@gnupg.org>
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 7945AC15AAE3 for <openpgp@ietfa.amsl.com>; Thu, 16 Jun 2022 00:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gnupg.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAVOQmAQ3apg for <openpgp@ietfa.amsl.com>; Thu, 16 Jun 2022 00:00:13 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E7E6C14792F for <openpgp@ietf.org>; Thu, 16 Jun 2022 00:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnupg.org; s=20181017; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=geNEotg/h+lcfqKPxh+jrrz1id6vSY/S7Aw8cSHeIR4=; b=MwvC41/dOLcZroCKFSsQWcyypo YX0Yg0niWbQp7Qremt+Nivcy47ORBdV9fG3UFoJ8DVHWJarMr61Zu5La/oADmzVfW4fktj1DGgYdr 67yCvduG6j1OCTMB74cUtQfdn7uh8N2zBOx4XMNOpoRuwT6QTr2acqA0l28++mWIPvw0=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1o1jU7-0004e7-FW for <openpgp@ietf.org>; Thu, 16 Jun 2022 09:00:07 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1o1jSD-0004zg-1p; Thu, 16 Jun 2022 08:58:09 +0200
From: Werner Koch <wk@gnupg.org>
To: Ángel <angel@16bits.net>
Cc: openpgp@ietf.org
References: <87wndi88ri.fsf@wheatstone.g10code.de> <83cce07c67f67c19b06c0c4239b6f335512a9a6f.camel@16bits.net>
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Jabber-ID: wk@jabber.gnupg.org
Mail-Followup-To: Ángel <angel@16bits.net>, openpgp@ietf.org
Date: Thu, 16 Jun 2022 08:58:02 +0200
In-Reply-To: <83cce07c67f67c19b06c0c4239b6f335512a9a6f.camel@16bits.net> ("Ángel"'s message of "Thu, 16 Jun 2022 01:43:00 +0200")
Message-ID: <875yl1858l.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=Screening_Beyond_Hope_pink_noise_VLSI_BLU-114/B_ISN_Port_Authority=s"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/RRD9EnQPPWtuTzvxLo5yR94iFXA>
Subject: Re: [openpgp] Padding packets
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 16 Jun 2022 07:00:17 -0000

On Thu, 16 Jun 2022 01:43, Ángel said:

>> A better mechanism to add padding is by handling
>> this at the MIME layer.
>
> How do you expect to handle this at the MIME layer? Or even if it's not
> use in the context of an email message?

You can use MIME for almost everything.  It is an universal extension to
text based protocols.  But I also live with any deterninistic padding as
long as this does not delay rfc4880bis any further.  I think it is
better to put this in a separate RFC, though.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein