From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 7ECEB72715 for ; Tue, 13 Apr 2021 07:07:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6F59025B22 for ; Tue, 13 Apr 2021 07:07:03 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id AEB7625B12 for ; Tue, 13 Apr 2021 07:07:01 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6D58C41F83 for ; Tue, 13 Apr 2021 07:07:01 +0200 (CEST) Message-ID: Date: Tue, 13 Apr 2021 07:07:00 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Thunderbird/88.0 Content-Language: en-US To: Stoiko Ivanov , pmg-devel@lists.proxmox.com References: <20210412192833.21988-1-s.ivanov@proxmox.com> <20210412192833.21988-4-s.ivanov@proxmox.com> From: Thomas Lamprecht In-Reply-To: <20210412192833.21988-4-s.ivanov@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.042 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [letsencrypt.org] Subject: Re: [pmg-devel] [PATCH pmg-docs v2 1/1] certs: add wildcard certificate support X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2021 05:07:03 -0000 On 12.04.21 21:28, Stoiko Ivanov wrote: > Signed-off-by: Stoiko Ivanov > --- > pmg-ssl-certificate.adoc | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/pmg-ssl-certificate.adoc b/pmg-ssl-certificate.adoc > index 6cd44b1..24e8d71 100644 > --- a/pmg-ssl-certificate.adoc > +++ b/pmg-ssl-certificate.adoc > @@ -187,6 +187,23 @@ and set the `alias` property in the {pmg} node configuration file > `/etc/pmg/node.conf` to `domain2.example` to allow the DNS server of > `domain2.example` to validate all challenges for `domain1.example`. > > +[[sysadmin_certs_acme_dns_wildcard]] > +Wildcard Certificates > +^^^^^^^^^^^^^^^^^^^^^ > +You can create a certificate for a 'wildcard DNS name' as described in why the single quotes? I'd rather go for something like "You can create wildcard certificates with the DNS challenge type." > +https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578[ACME v2 Production Environment & Wildcards]. Maybe rather link: https://letsencrypt.org/docs/challenge-types/#dns-01-challenge > + > +Wildcard DNS names start with a `*.` prefix and are considered valid for all > +(one-level) subdomain names of the verified domain. So a certificate for > +`*.domain.example` is valid for example for `foo.domain.example` and > +`bar.domain.example`. above paragraph should come first, as it's the actual introduction to wildcards. A example for not being valid for deeper level would also help, something like: "is valid for example for `foo.domain.example` and `bar.domain.example`, but not for `baz.foo.domain.example`." > + > +Verification for wildcard DNS names only works with the `dns-01` validation > +method. > + We should probably check above in the frontend and backend for better UX. > +You need to configure both the base domain (`domain.example`) as well as the > +wildcard equivalent (`*.domain.example`) under `Certificates` with a DNS plugin. > + above paragraph is wrong. > > Combination of Plugins > ^^^^^^^^^^^^^^^^^^^^^^ >