Re: [pkix] Validating Certs w/out reliable source of Time

"Dr. Pala" <director@openca.org> Mon, 08 October 2018 15:45 UTC

Return-Path: <director@openca.org>
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 4C404130E27 for <pkix@ietfa.amsl.com>; Mon, 8 Oct 2018 08:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.486
X-Spam-Level:
X-Spam-Status: No, score=-0.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_HK_NAME_DR=0.01] autolearn=no 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 plMEGvDduQ-T for <pkix@ietfa.amsl.com>; Mon, 8 Oct 2018 08:45:25 -0700 (PDT)
Received: from mail.katezarealty.com (mail.katezarealty.com [104.168.158.213]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8E0130E22 for <pkix@ietf.org>; Mon, 8 Oct 2018 08:45:25 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mail.katezarealty.com (Postfix) with ESMTP id 8AFCC3741038; Mon, 8 Oct 2018 15:45:24 +0000 (UTC)
X-Virus-Scanned: amavisd-new at katezarealty.com
Received: from mail.katezarealty.com ([127.0.0.1]) by localhost (mail.katezarealty.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SIlZf86IByuF; Mon, 8 Oct 2018 11:45:23 -0400 (EDT)
Received: from Maxs-MBP.cablelabs.com (unknown [192.160.73.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.katezarealty.com (Postfix) with ESMTPSA id 060483740FC1; Mon, 8 Oct 2018 11:45:22 -0400 (EDT)
To: Tom Ritter <tom@ritter.vg>
Cc: pkampana@cisco.com, IETF PKIX <pkix@ietf.org>
References: <f1d0a721-96e4-5d1b-4dd3-7b041e3c4379@openca.org> <47b70e1c4d214e9297e29b9ee1450c59@XCH-ALN-010.cisco.com> <a16d45ac-b48e-6cee-40c1-84b065df2d4c@openca.org> <CA+cU71mPq0qKWQ7XQRfZOfPZQ+NWuW6PTy+948LCqoaw_HiSuA@mail.gmail.com>
From: "Dr. Pala" <director@openca.org>
Organization: OpenCA Labs
Message-ID: <c8d0dc3d-ef5b-deaf-fe7f-8111fc8721a6@openca.org>
Date: Mon, 08 Oct 2018 09:45:22 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CA+cU71mPq0qKWQ7XQRfZOfPZQ+NWuW6PTy+948LCqoaw_HiSuA@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070905050503020509070403"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/-d4EY2OEUwcNRVHI8_mAEU2XsMI>
Subject: Re: [pkix] Validating Certs w/out reliable source of Time
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: Mon, 08 Oct 2018 15:45:28 -0000

Hi Tom,


On 10/8/18 9:00 AM, Tom Ritter wrote:
> On Mon, 8 Oct 2018 at 14:13, Dr. Pala <director@openca.org 
> <mailto:director@openca.org>> wrote:
>
>     Hi Panos, all,
>
>     [...]
>
>
> If you use OCSP in a challenge-response mode with nonces - you could 
> get this within established TLS/PKIX standards. Although OCSP 
> challenge/response (as opposed to stapling) is falling out favor; and 
> OCSP nonces stopped being used over a decade ago. But I don't think 
> the code is removed from tools; just uncommonly used.
>
> Caveats being; of course, the uptime of your time/OCSP server; 
> difficulty of rotating that server's certificate, what to do when you 
> don't get a response....

For our specific case, we considered using the OCSP responses since our 
servers do support NONCEs and do not have ridiculously long 
validity/caching period (as it seems current practices from many CAs), 
however that might not be a good path for a generic solution (beacuse of 
current practices). I am also considering other protocols (e.g., SCVP) 
and cross-protocols options (e.g., DNS entries/extensions, etc.) - 
however the constraints on network access might make these approaches 
also difficult...

Thanks again,

Cheers,

-- 
Best Regards,
Massimiliano Pala, Ph.D.
OpenCA Labs Director
OpenCA Logo