IETF Logo Mail Archive

Re: [Acme] Threat model for claiming domains

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 23 December 2014 12:54 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03761ACE2E for <acme@ietfa.amsl.com>; Tue, 23 Dec 2014 04:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 upA4LutIAFzO for <acme@ietfa.amsl.com>; Tue, 23 Dec 2014 04:54:30 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EC41ACE50 for <acme@ietf.org>; Tue, 23 Dec 2014 04:43:58 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id gq15so5467534lab.32 for <acme@ietf.org>; Tue, 23 Dec 2014 04:43:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9ucjKIRmNVg9TLrrlkfaAMAnrzegTBxXquoUDKNvZXs=; b=ENGYd2J4CdeozrZ3Er6tawws+zK71EDCrmMU3aA9wIAx9V5/W9WBVzTU3skARa8Pf+ 20dEot23DTqNsQiY+2+bp6mPpUSn3S6xvoeV+m/aUL2kIFhmjxL0WeZULlnOvAM2CjVs dkaeHm9oo9qma5+otX034/4CikEYItd4iw+nIgzxo/3NINEyUeFG6cSVPG49tddHwSJL OylBZT7WfUfDw+m95ycKKQSK+moWL7O/NsTuW0yAxzwNCsz9C1g6VnO+lDrysJIr1jaC z6anxb5u6R4On6iFmjR4dNveAQqf8aWVX29dGUpIIRxvOLGzPd0R2yxzrYLlygkspaX+ YHoQ==
MIME-Version: 1.0
X-Received: by 10.112.119.201 with SMTP id kw9mr27065264lbb.99.1419338637378; Tue, 23 Dec 2014 04:43:57 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.19.42 with HTTP; Tue, 23 Dec 2014 04:43:57 -0800 (PST)
In-Reply-To: <CAK6vND9_nPuv=iBu=qbu=MuutEWh_BQbjtZDisUy730kYn48dQ@mail.gmail.com>
References: <CAHOTMVJdf8mQ-8_-ocHpfUA+N9v-S5VsBWgOVp1aFwDaWp3d0Q@mail.gmail.com> <CAL02cgSvc1sO-iH3J_c4f=A2CspKwG686DaSUC1JKLD4GRy__w@mail.gmail.com> <5497F5BB.9030002@comodo.com> <CAL02cgSLtiN0Q-KEWZLcG_YjrW0gtdrwJHF9e6W_FdkHR92aig@mail.gmail.com> <CAK6vND9_nPuv=iBu=qbu=MuutEWh_BQbjtZDisUy730kYn48dQ@mail.gmail.com>
Date: Tue, 23 Dec 2014 12:43:57 +0000
X-Google-Sender-Auth: AMYY23bhJDXJtxgXUKBTQJSDqww
Message-ID: <CAMm+LwgARvMAP2L=r2Z8ccGbt7pdHhDNJjSPw+xPFqCLKEhsyA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Peter Bowen <pzbowen@gmail.com>
Content-Type: multipart/alternative; boundary="047d7bae49da4c0909050ae187a9"
Archived-At: http://mailarchive.ietf.org/arch/msg/acme/OuI2gL5s7XrKL114vpOBADBJP54
Cc: Richard Barnes <rlb@ipv.sx>, Rob Stradling <rob.stradling@comodo.com>, "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] Threat model for claiming domains
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 12:54:32 -0000

On Mon, Dec 22, 2014 at 6:36 PM, Peter Bowen <pzbowen@gmail.com> wrote:

> On Mon, Dec 22, 2014 at 6:29 AM, Richard Barnes <rlb@ipv.sx> wrote:
> >
> > I notice that there are mentions of an API in that document.  If you have
> > other API documentation you could share, that could be useful.  In
> > particular, it would make it easier to make ACME something that you guys
> > could transition to :)
>
> It appears that the other API documentation is in the same directory:
> https://secure.comodo.com/api/pdf/latest/
>
> https://secure.comodo.com/api/pdf/latest/AutoApplySSL.pdf is the primary
> API.


Yes, Robin sent me that link a while back but the conversation seemed to
have moved on to the signature discussion which seemed like better use of
time...

One of the things I want to do in the new year is to see whether I can
drive that API from a JSON frontend and what it looks like.

The only difference I can see is the introduction of an account concept..

v2.23.0 | Report a Bug | By Email