From dev-return-90857-archive-asf-public=cust-asf.ponee.io@httpd.apache.org Fri Jan 12 13:14:22 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 1DF86180621 for ; Fri, 12 Jan 2018 13:14:22 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0DA7D160C33; Fri, 12 Jan 2018 12:14:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 53E55160C30 for ; Fri, 12 Jan 2018 13:14:21 +0100 (CET) Received: (qmail 32338 invoked by uid 500); 12 Jan 2018 12:14:20 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 32328 invoked by uid 99); 12 Jan 2018 12:14:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jan 2018 12:14:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A4E3CC05CB for ; Fri, 12 Jan 2018 12:14:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.111 X-Spam-Level: X-Spam-Status: No, score=-0.111 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=greenbytes.de header.b=ZOujN9WL; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=ps4DwOi1 Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id RA3YV5r-X1Dy for ; Fri, 12 Jan 2018 12:14:19 +0000 (UTC) Received: from mail.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C99745F485 for ; Fri, 12 Jan 2018 12:14:18 +0000 (UTC) Received: by mail.greenbytes.de (Postfix, from userid 117) id 4A3CA15A3437; Fri, 12 Jan 2018 13:14:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=greenbytes.de; s=mail; t=1515759258; bh=nSRg3EXy9JuxGhTBmvXMUIWj64mOo0hwTlAeeaWtYF8=; h=From:Subject:Date:References:To:In-Reply-To:From; b=ZOujN9WLdvL6ZuViZdhCGl6QMt44LBzpcVJ/nlKR9QhDFmdvLHqs6zi7HknC8wxK6 dAO/aAhaj1kzXTOYU8vHdtVnSX0V/ejME1MA2w4SjJllX6TA5qpM1fKun24crIKKcx evIOSJbcPlEhR66dOEdoV2x4rnzL/yuUbAYabLfU= Received: from resistance.greenbytes.local (unknown [217.91.35.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id B1D1C15A035A for ; Fri, 12 Jan 2018 13:14:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=greenbytes.de; s=mail; t=1515759257; bh=nSRg3EXy9JuxGhTBmvXMUIWj64mOo0hwTlAeeaWtYF8=; h=From:Subject:Date:References:To:In-Reply-To:From; b=ps4DwOi1tlwgbnpbT55KwjdqI1Hma9Bof544J+Sdl0MQvMkSs2eFu9hEmZeWUp6C6 w1Z9P7tnQEvCNpAO1O4gEUR883WK4jN7/Mpx7OHwKDv+reBWVdsvYDDTdzxaCBd2lh xVlFRxEkzbHL5tqB+HAamaXELTyM1nuUhxztq8F8= From: Stefan Eissing Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: can we haz backports? Date: Fri, 12 Jan 2018 13:14:17 +0100 References: <6239F90D-AA3C-4E31-AE71-23CEA81EE4A8@greenbytes.de> To: dev@httpd.apache.org In-Reply-To: Message-Id: <9B40EC5A-4F1D-4CFD-96ED-E73DD5F1A2A1@greenbytes.de> X-Mailer: Apple Mail (2.3445.5.20) > Am 12.01.2018 um 13:07 schrieb Yann Ylavic : > > On Fri, Jan 12, 2018 at 12:14 PM, Stefan Eissing > wrote: >> >> Is anyone planning to review this in the next days? > > I plan to do so, is there a strong need to own a domain for tesing or > can I use a "standalone" thingy (if that's ever relevant)? If you go against the staging server at Let's Encrypt, any challenge for a domain name will need to be resolved to an IP address that you listen on. This will give you a certificate on success that has an untrusted root, but you can request that for the domain very often, as needed in testing. You can test locally. The LE ACME server is available as a docker instance, as described in https://github.com/letsencrypt/boulder That is the one the test suite in https://github.com/icing/mod_md uses. -Stefan