IETF Logo Mail Archive

Re: [openpgp] "OpenPGP Simple"

Peter Gutmann <pgut001@cs.auckland.ac.nz> Mon, 16 March 2015 01:51 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 59D081A1EFE for <openpgp@ietfa.amsl.com>; Sun, 15 Mar 2015 18:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 08FJ6BAsUYjB for <openpgp@ietfa.amsl.com>; Sun, 15 Mar 2015 18:51:21 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 684D81A1EF6 for <openpgp@ietf.org>; Sun, 15 Mar 2015 18:51:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1426470681; x=1458006681; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=Pfb9DbvYKU3N8Nw8nWEYQub6yEfVqYdloGIjSvKHdg4=; b=txRXG4hS9sZL0SvfVOwbAv3F/fpUPBauQYefb1achyaiSm+O3TSTpTiR HfjAR7wSGMqVCNElXwBd6bJ/aJfc98ZukIj6RVkVJdzi8PBTAzLDYzEk7 1Fp5WNp5zUSjDTquwcKC8xECx9eyJoBAEpPx8Ln6sj0GwpwDytZc6tabn 8=;
X-IronPort-AV: E=Sophos;i="5.11,407,1422874800"; d="scan'208";a="314023297"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.125 - Outgoing - Outgoing
Received: from uxchange10-fe3.uoa.auckland.ac.nz ([130.216.4.125]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 16 Mar 2015 14:51:20 +1300
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.82]) by uxchange10-fe3.UoA.auckland.ac.nz ([169.254.143.234]) with mapi id 14.03.0174.001; Mon, 16 Mar 2015 14:51:20 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: "openpgp@ietf.org" <openpgp@ietf.org>
Thread-Topic: [openpgp] "OpenPGP Simple"
Thread-Index: AdBfi7JjxreSmfp7SbOIMH9w+K4H0A==
Date: Mon, 16 Mar 2015 01:51:19 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73AAFB25D4@uxcn10-5.UoA.auckland.ac.nz>
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/flWnPEbNZ9WjXqiYuw0umN6Mylk>
Subject: Re: [openpgp] "OpenPGP Simple"
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Mar 2015 01:51:23 -0000

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

>Is there any prior art on IETF specs having a "full" and "simple" form where
>full implementations can read any output of simple ones, but not always vice-
>versa?  

Yes and no.  I've tried this with the great pile of spaghetti that is the SSH
protocol (see https://www.cs.auckland.ac.nz/~pgut001/pubs/simplessh.txt), but
SSH has the same problem as PGP does, there's a single dominant implementation
that defines what the protocol is, and everyone else codes to that rather than
the spec (for SSH it's somewhat worse in that the client-side implementation
is Putty, which has bug-workarounds for all manner of broken implementations,
as a result of which it'll accept any old rubbish while at the same time being
used as a validation suite by developers of further broken implementations).

So even if you define a simple-PGP profile, I'm not sure how much (if any)
traction it'll get.

Peter.

v2.23.0 | Report a Bug | By Email