IETF Logo Mail Archive

Re: [openpgp] saltpack on OpenPGP message format problems

Peter Gutmann <pgut001@cs.auckland.ac.nz> Thu, 11 February 2016 03:42 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9DFB1A8A3A for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 19:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 3GcsnXqTAOXz for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 19:41:58 -0800 (PST)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C32761A8A39 for <openpgp@ietf.org>; Wed, 10 Feb 2016 19:41:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1455162118; x=1486698118; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hcP4+UqpDyg5Tr5ihZdJftfb2uFxwwcxP3WRBDBxtBI=; b=y3sM7UVZpLC9TYLDGFjh0lIAMvYaw4COwv+hAegR5ikgb46aVfY0lf9J ONg9EgFVIcqLWYjEWZ8hs4ZLdpG3STllPVmy3XOT+mPSsmXUcG3bboS5o BVeEhgbxLeo9c3rxNeubhuPJTaNHEDt3vGkwTOihls4kEhYWPxQB2li9H yZpvCE1NbYE2Kc6ZcJMd/3mHM2h3tL3IVzThaXBYyXFIrmnX1lko+q6Hr vqDr0KTaKo92eTWDTpZhcj1n2yl5a+u1opL2e9GoNpexLmCiu57cgpEsY jSeO+ZlgYJy+VrtTtRgFzdDYJSM+xAwBuxadGyQlBYy7euf1gCRwTEgZf Q==;
X-IronPort-AV: E=Sophos;i="5.22,429,1449486000"; d="scan'208";a="67332791"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.171 - Outgoing - Outgoing
Received: from exchangemx.uoa.auckland.ac.nz (HELO uxchange10-fe4.UoA.auckland.ac.nz) ([130.216.4.171]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 11 Feb 2016 16:41:54 +1300
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.153]) by uxchange10-fe4.UoA.auckland.ac.nz ([169.254.109.63]) with mapi id 14.03.0266.001; Thu, 11 Feb 2016 16:41:54 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Stephen Paul Weber <singpolyma@singpolyma.net>, ianG <iang@iang.org>
Thread-Topic: [openpgp] saltpack on OpenPGP message format problems
Thread-Index: AQHRY+WcrCMKgX/VlESZgKvALMTRbp8kmFWAgAGbgEQ=
Date: Thu, 11 Feb 2016 03:41:53 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4BED18C@uxcn10-5.UoA.auckland.ac.nz>
References: <56BB0308.8020504@iang.org>, <20160210160641.GA3090@singpolyma-liberty>
In-Reply-To: <20160210160641.GA3090@singpolyma-liberty>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/1lyIwacFhlmUqjkM2Zq5JFPvv8s>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
Subject: Re: [openpgp] saltpack on OpenPGP message format problems
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Feb 2016 03:42:01 -0000

Stephen Paul Weber <singpolyma@singpolyma.net> writes:

>Couldn't we just say "PGP is binary, encode however you like"?  In email we
>have transport encodings, and so do most other reasonable places.  The only
>real use for ASCII armor anymore is in "clearsign" context when posting
>a plain text file that contains the signature, etc.

The "ASCII armoring" was written in order to, among other things, allow PGP
to traverse Fidonet systems running on MSDOS with 2400bps modems.  That's 
what it dates back to.  It should have died a long, long time ago, we can 
send pretty much any other binary-only format over pretty much any medium in 
a manner that's totally invisible to the user, there's no need to still 
retain it.

Peter.

v2.23.0 | Report a Bug | By Email