IETF Logo Mail Archive

Re: [pkix] Clarification on "zero" hash value in SigPolicyHash (CAdES)

Peter Gutmann <pgut001@cs.auckland.ac.nz> Wed, 17 July 2019 03:28 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6F74120088 for <pkix@ietfa.amsl.com>; Tue, 16 Jul 2019 20:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 HzYUcXaXrXzI for <pkix@ietfa.amsl.com>; Tue, 16 Jul 2019 20:28:15 -0700 (PDT)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (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 4248B1200DB for <pkix@ietf.org>; Tue, 16 Jul 2019 20:28:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1563334095; x=1594870095; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=8pWrIHEAj7U3zBiehZZ9WHShD5uZXwMPfuSdqXZ4xFU=; b=LYXqQWf0qt1Omihu8h4nffbL/YxL3pGCApGPGC3LkN10rLtIydfw7eXb 0N0iLrvhPAOi2fxsW1q70iLBXm3jfMUZ5mNS45H5kK/UdrxXtbSxOXsXV jicIMtNtzRrpwA7GN1Hogw/qgyCYgC2kbULe94gXvkXW/gl++KCxC3ksM 7LOm/fq649GktsVIvmYZWDa1sbyTE/Lk42pkhhjeX+DKytgrAGpLSKpjk oKLVu+A+/S9ZF4sGvykCv9nKHgyXtZiKvflTbVf8O82ktNf7ANzMFgxiN K+U+qnrZq6E6kpknVyZ/KuJX9mO1lc2fbE/0mnIxxRuD024qMEUsGrnyI A==;
X-IronPort-AV: E=Sophos;i="5.64,272,1559476800"; d="scan'208";a="71083721"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.3.5 - Outgoing - Outgoing
Received: from exchangemx.uoa.auckland.ac.nz (HELO uxcn13-tdc-d.UoA.auckland.ac.nz) ([10.6.3.5]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 17 Jul 2019 15:28:12 +1200
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz (10.6.2.5) by uxcn13-tdc-d.UoA.auckland.ac.nz (10.6.3.5) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 17 Jul 2019 15:28:11 +1200
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) by uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) with mapi id 15.00.1395.000; Wed, 17 Jul 2019 15:28:11 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Stefan Santesson <stefan@aaa-sec.com>, Niklas Matthies <pkix@nmhq.net>, "pkix@ietf.org" <pkix@ietf.org>
Thread-Topic: [pkix] Clarification on "zero" hash value in SigPolicyHash (CAdES)
Thread-Index: AQHVOO1wcGGXPXcfd0KYugWNDx4HUabMKg4AgADWgxj//3mBgIABs0VG
Date: Wed, 17 Jul 2019 03:28:10 +0000
Message-ID: <1563334087967.97714@cs.auckland.ac.nz>
References: <20190712200549.2kgzjqodj5afnxlt@nmhq.net> <0FDBEEC9-0FBA-4C47-BD04-EE7F6053426D@aaa-sec.com> <1563269533626.58560@cs.auckland.ac.nz>, <218E69B7-036E-45FF-AD3B-9F017FCAF40E@aaa-sec.com>
In-Reply-To: <218E69B7-036E-45FF-AD3B-9F017FCAF40E@aaa-sec.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/5DW0KraOfN_Yq8-7XNwAhGu5vE8>
Subject: Re: [pkix] Clarification on "zero" hash value in SigPolicyHash (CAdES)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2019 03:28:17 -0000

Stefan Santesson <stefan@aaa-sec.com> writes:

>To assign a specific meaning to one out of all possible but syntactically
>valid hash values, is exactly the type of specification work that leads to
>implementation errors and security vulnerabilities.

How would it lead to implementation errors and security vulns?  It's a value
that's guaranteed to not match anything while requiring zero changes to
existing code, what sort of implementation error would it lead to?

Peter.

v2.23.0 | Report a Bug | By Email