From: "Paul Smedley" <ecs-isp@2rosenthals.com>
Message-ID: <a2d41b27-101b-45a2-9f23-1aed22ee8ca1@smedley.id.au>
Date: Sun, 8 Dec 2024 14:46:19 +1030
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [eCS-ISP] Getting started with Let's Encrypt
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>
References: <list-11321264@2rosenthals.com> <list-11322461@2rosenthals.com>
 <list-11322996@2rosenthals.com> <list-11323402@2rosenthals.com>
 <list-11330007@2rosenthals.com>
Content-Language: en-US
In-Reply-To: <list-11330007@2rosenthals.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Max,

On 7/12/24 19:42, Massimo S. wrote:
>
> there is a way with LE to create one certificate containing also 3rd 
> level domains e.g.
>
> mywebsite.it
> and
> www.mywebsite.it
>
> both with only one SSL cert.
>
No idea with uacme, but this can definitely be done with certbot. for eg 
I use a single certificate for vps.smedley.id.au and mail.smedley.id.au

Looks like this should be possible with uacme as well. Looking at: 
https://wasd.vsm.com.au/src/wucme/uacme1.pdf

uacme [OPTIONS …] issue DOMAIN [ALTNAME …] Issue a certificate for 
DOMAIN with zero or more ALTNAMEs. If a certificate is already available 
at CONFDIR/DOMAIN/cert.pem for the specified DOMAIN and ALTNAMEs, and is 
still valid for longer than DAYS, no action is taken unless -f, --force 
is specified. The new certificate is saved to CONFDIR/DOMAIN/cert.pem. 
If the certificate file already exists, it is hardlinked to 
CONFDIR/DOMAIN/cert-TIMESTAMP.pem before overwriting. The private key 
for the certificate is loaded from CONFDIR/private/DOMAIN/key.pem. If no 
such file exists, a new key is generated unless -n, --never-create is 
specified.