Re: [Trans] [trans] #73 (rfc6962-bis): Section 3 text re log cert validation is ambiguous

Ben Laurie <benl@google.com> Mon, 06 July 2015 15:42 UTC

Return-Path: <benl@google.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702311B2D33 for <trans@ietfa.amsl.com>; Mon, 6 Jul 2015 08:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level:
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 xTq5_mRVGneg for <trans@ietfa.amsl.com>; Mon, 6 Jul 2015 08:42:35 -0700 (PDT)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35EBE1B2D2B for <trans@ietf.org>; Mon, 6 Jul 2015 08:42:35 -0700 (PDT)
Received: by ykfy125 with SMTP id y125so152139955ykf.1 for <trans@ietf.org>; Mon, 06 Jul 2015 08:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SoohgTUVqz02ryv367P4g7/jX6AEZsmOSz55eaMupE8=; b=IY0JJZXPv70wP2a+H+jQNVwXtmLSh/gUxyMByaVOHnq6+pn6+KKmvWY65FBpkjFYbL XP33FSH3dl6uIAixmt3wtH9NIa1e6gVz6WoGreFqLNmjSYOeRwqU3NJJw2Ew8AWT3qaR eBWlKQDazi7PGu7UkT+/OV+eD9zWls5vvegoYWy9dn0x7Cy7L8izjXoYNNQqMumWKvxB p71dkXlurOxdx9/Pf1CQruFfA3ODpgL+raC7wNK3/+2PKd3wuuj0CupZknwSWU+Aa/HR bqcpcksSC8SDsYI0qD3fu7g84RNurFE38nd0MmQxtvY0pGGp+e6gRYz4w9yXF73fcU2o aXyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SoohgTUVqz02ryv367P4g7/jX6AEZsmOSz55eaMupE8=; b=jpTI6+QcoDbjeDg51jI/bXRq0dyndC/5nKat5lBdnpIpQxC2BEQ7MSWrHyILcHZhXX 0K3vDJdQOypFS3brPXRFg8qE/LfRrsBZaKswOya1rZb2uRQTc5maNRRf9Y7pmYTx/TtR uDCByUVK2ZiEwNVpdmebCEk3syS3xLoZ2jBOJ+wcbgEfRKGXb3AZ+hZgGR1VcmurGdPI pcmI3iZY4157lGa4b6O5RFWClvuIC9VDsh4mEBsbk7NW1id7gI/o4HBb7PDcvEXDrDO6 7Cn+D8/Lo/8l6n9ToPk1P/ORMUQUY6PFRBrupKg8bQmOyTxyqUXSMv/EXXXAcSS7K2jZ E2Ng==
X-Gm-Message-State: ALoCoQmcfrKfloMQIgu3Z1/F3LiCR1RiuoLeVJxnp94NzziymOn4gKAo+og3c218cXRPT8M+a9vS
MIME-Version: 1.0
X-Received: by 10.170.45.78 with SMTP id 75mr28289671ykn.53.1436197354472; Mon, 06 Jul 2015 08:42:34 -0700 (PDT)
Received: by 10.37.8.201 with HTTP; Mon, 6 Jul 2015 08:42:34 -0700 (PDT)
In-Reply-To: <559A9977.1040808@bbn.com>
References: <052.b3ecc6ca8b28cc47e13443079611ce86@tools.ietf.org> <067.7becba46c4f8b854834f9bb0c27374ce@tools.ietf.org> <559A9977.1040808@bbn.com>
Date: Mon, 06 Jul 2015 16:42:34 +0100
Message-ID: <CABrd9SRPESqxWhCbKK4asgVY4zM3i_3REYuua=ZEwVTe76rMOQ@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/5JxW0iRARev5_Tpvkl6HBblrnd0>
Cc: "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] [trans] #73 (rfc6962-bis): Section 3 text re log cert validation is ambiguous
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2015 15:42:36 -0000

On 6 July 2015 at 16:06, Stephen Kent <kent@bbn.com> wrote:
> If there is no standard for the validation checks logs perform, because of a
> desire to accept malformed certs from (sloppy) CAs, then a CA cannot know
> whether
> its submission will be rejected by a log.

If a CA wants to be sure in advance (why?) that a log will accept its
certs, then it should conform with the relevant standards.

> The alternative is to specify a
> way for
> each log to specify what checks it performs, and to publish that the same
> way other
> log info is advertised.
>
> Steve
>
>
>> #73: Section 3 text re log cert validation is ambiguous
>>
>>
>> Comment (by benl@google.com):
>>
>>   On the issue of specifying deviations, I am not sure how that could
>>   realistically be done. For example, our logs will permit whatever
>>   deviations OpenSSL permits. I don't think anyone knows precisely what
>>   those are, and I'm prepared to bet they vary between versions.
>>
>>   Even leaving that aside, experience suggests we have to permit
>> deviations
>>   in order to admit incorrect certificates that are accepted by browsers.
>> I
>>   don't think we can anticipate what all of those are.
>>
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans