IETF Logo Mail Archive

Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?

Werner Koch <wk@gnupg.org> Thu, 07 July 2016 15:32 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 5286C12D0AF for <openpgp@ietfa.amsl.com>; Thu, 7 Jul 2016 08:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
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 9IQ1A2z7vRWC for <openpgp@ietfa.amsl.com>; Thu, 7 Jul 2016 08:32:06 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDF5712B069 for <openpgp@ietf.org>; Thu, 7 Jul 2016 08:32:04 -0700 (PDT)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.80 #2 (Debian)) id 1bLBHW-0000zN-N2 for <openpgp@ietf.org>; Thu, 07 Jul 2016 17:32:02 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.84 #3 (Debian)) id 1bLBDy-0008SL-5t; Thu, 07 Jul 2016 17:28:22 +0200
From: Werner Koch <wk@gnupg.org>
To: Derek Atkins <derek@ihtfp.com>
References: <20160701153304.332d2c95@pc1> <874m86xq04.fsf@alice.fifthhorseman.net> <9A043F3CF02CD34C8E74AC1594475C73F4CB97D2@uxcn10-5.UoA.auckland.ac.nz> <5779E086.9000506@brainhub.org> <BAB41369-E007-4342-8E89-1F023EA851E1@icloud.com> <CAMm+Lwj5F3x4pqGQ2DjDxAqGxsoiBSqK5ToFi-A-nouNDPeH_A@mail.gmail.com> <sjmwpkyq0bd.fsf@securerf.ihtfp.org> <CAMm+Lwg1nsWXPo3VzDs-nLo0ChYSr0RiTyZUR4JvL_yd88ZWsQ@mail.gmail.com> <sjminwhpkw2.fsf@securerf.ihtfp.org>
Organisation: g10 Code GmbH
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
OpenPGP: url=https://k.gnupg.net/80615870F5BAD690333686D0F2AD85AC1E42B367
Mail-Followup-To: Derek Atkins <derek@ihtfp.com>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF OpenPGP <openpgp@ietf.org>, Jon Callas <joncallas@icloud.com>
Date: Thu, 07 Jul 2016 17:28:22 +0200
In-Reply-To: <sjminwhpkw2.fsf@securerf.ihtfp.org> (Derek Atkins's message of "Thu, 07 Jul 2016 10:45:17 -0400")
Message-ID: <87mvltmprd.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/Hr-dBf0bAnZy__ZReC7zsIjtGBc>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Jon Callas <joncallas@icloud.com>, IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Jul 2016 15:32:08 -0000

On Thu,  7 Jul 2016 16:45, derek@ihtfp.com said:

> I guess X.509v3 does, theoretically, allow multiple signatures on a
> certificate, but I was under the impression that zero implementations
> actually supported that?

I can't see how this is possible within an X.509 certificate:

   Certificate  ::=  SEQUENCE  {
        tbsCertificate       TBSCertificate,
        signatureAlgorithm   AlgorithmIdentifier,
        signatureValue       BIT STRING  }

There is only one signature for the to-be-signed-Certificate.


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
 /* Join us at OpenPGP.conf  <https://openpgp-conf.org> */

v2.23.0 | Report a Bug | By Email