Re: [Acme] Enrollment of Wildcard certificates with ACME?

yan <yan@eff.org> Tue, 28 July 2015 18:11 UTC

Return-Path: <yan@eff.org>
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 D40AD1B2D2F for <acme@ietfa.amsl.com>; Tue, 28 Jul 2015 11:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 8W_KSjoOFewG for <acme@ietfa.amsl.com>; Tue, 28 Jul 2015 11:11:35 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC8671B2CF9 for <acme@ietf.org>; Tue, 28 Jul 2015 11:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=jZycDJQwfMC7DbgpnE5ewcNaqUn1lNyzszp0sJrIOQE=; b=TQD1mIdDlpvUInKEE6/t78a+40uPaRaErQ9lyiVdXQH5MeZ1D9BTaPeqZMv5F+sbi7VsawYL7Juma6lwIhLcvHbghDhyG8jZJMvK7YBZaMvzM7BKSNmUUEFv93BI9iIBI4iZ+eHFCJLqAu/2U9oftgKYfSVpoK1CXXnQsUWPNes=;
Received: ; Tue, 28 Jul 2015 11:11:06 -0700
Message-ID: <55B7C5B9.4030508@eff.org>
Date: Tue, 28 Jul 2015 11:11:05 -0700
From: yan <yan@eff.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Fabio Pietrosanti (naif) - lists" <lists@infosecurity.ch>, acme@ietf.org
References: <55B75C58.6080106@infosecurity.ch>
In-Reply-To: <55B75C58.6080106@infosecurity.ch>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/jGKy-sz2veHSE0L6TsuKggfA0Og>
Subject: Re: [Acme] Enrollment of Wildcard certificates with ACME?
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Jul 2015 18:11:41 -0000

https://github.com/letsencrypt/acme-spec/pull/97

On 7/28/15 3:41 AM, Fabio Pietrosanti (naif) - lists wrote:
> Hi all,
>
> within the ACME specification, has been the Enrollment of Wildcard
> certificate been taken in consideration?
>
> At Tor2web software project, that require wildcard certificate to be
> used, we'd really love to integrate automation of certificate setup with
> ACME/LetsEncrypt.
>
>