Re: ECC in OpenPGP

Peter Gutmann <pgut001@cs.auckland.ac.nz> Sat, 04 September 2010 13:50 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o84DoFHL084287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 4 Sep 2010 06:50:15 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o84DoF0e084286; Sat, 4 Sep 2010 06:50:15 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from mx2-int.auckland.ac.nz (mx2-int.auckland.ac.nz [130.216.12.41]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o84DoBDC084277 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <ietf-openpgp@imc.org>; Sat, 4 Sep 2010 06:50:13 -0700 (MST) (envelope-from pgut001@cs.auckland.ac.nz)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=pgut001@cs.auckland.ac.nz; q=dns/txt; s=uoa; t=1283608213; x=1315144213; h=from:to:subject:cc:in-reply-to:message-id:date; z=From:=20Peter=20Gutmann=20<pgut001@cs.auckland.ac.nz> |To:=20openpgp@brainhub.org,=20simon@josefsson.org |Subject:=20Re:=20ECC=20in=20OpenPGP|Cc:=20ietf-openpgp@i mc.org|In-Reply-To:=20<8762ym8s3g.fsf@mocca.josefsson.org >|Message-Id:=20<E1Ort8E-0007FE-9Y@wintermute02.cs.auckla nd.ac.nz>|Date:=20Sun,=2005=20Sep=202010=2001:50:10=20+12 00; bh=15eqD1jvGD5jEkannyWwPdh8Ck2X/gYqdVzqRfigGJ0=; b=aHrMu6+KJdm1OKS0ar09+BndCBX/+v9gZ0/vaOB75pb8X4HWauW2IEcA o5SnEzK8+KLHQX74jVgVtnuGvCST/6AJktSb+XfOAkHry1x2MhI7O6kTc tMFcRp09wG0gm5/ahm1iTHiIqV7XEYw6N2RtFdVUt9INDEArCkDtFrZwB g=;
X-IronPort-AV: E=Sophos;i="4.56,317,1280664000"; d="scan'208";a="24427499"
X-Ironport-HAT: UNIVERSITY - $RELAY-THROTTLE
X-Ironport-Source: 130.216.207.92 - Outgoing - Outgoing
Received: from wintermute02.cs.auckland.ac.nz ([130.216.207.92]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 05 Sep 2010 01:50:10 +1200
Received: from pgut001 by wintermute02.cs.auckland.ac.nz with local (Exim 4.69) (envelope-from <pgut001@cs.auckland.ac.nz>) id 1Ort8E-0007FE-9Y; Sun, 05 Sep 2010 01:50:10 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: openpgp@brainhub.org, simon@josefsson.org
Subject: Re: ECC in OpenPGP
Cc: ietf-openpgp@imc.org
In-Reply-To: <8762ym8s3g.fsf@mocca.josefsson.org>
Message-Id: <E1Ort8E-0007FE-9Y@wintermute02.cs.auckland.ac.nz>
Date: Sun, 05 Sep 2010 01:50:10 +1200
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>

Simon Josefsson <simon@josefsson.org> writes:

>Supporting PKCS#1 v2.0 padding sounds like a separate effort though.  Is
>anyone interested in that?

I think you need to phrase the question slightly differently:

  Supporting a mechanism that's supported by nothing and that breaks
  compatibility with all existing implementations, and that has no obvious
  advantages over the existing mechanism, sounds like a separate effort
  though.  Is anyone interested in that?

Then the answer becomes self-evident.

Peter.