From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.5-pre1
X-Received: by 2002:a0c:e50a:: with SMTP id l10mr20167552qvm.55.1605610143081;
        Tue, 17 Nov 2020 02:49:03 -0800 (PST)
X-Received: by 2002:a05:6214:20e4:: with SMTP id 4mr10541381qvk.37.1605610142939;
 Tue, 17 Nov 2020 02:49:02 -0800 (PST)
Path: eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!peer01.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 17 Nov 2020 02:49:02 -0800 (PST)
In-Reply-To: <871rgsqtfv.fsf@gaheris.vdwege.eu>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=79.51.60.190; posting-account=JRF_-woAAABYlsAtkCl_CUxBuQy2SsaQ
NNTP-Posting-Host: 79.51.60.190
References: <46155ba8-785c-4503-81bc-a0a3cf3acd63n@googlegroups.com>
 <87h7ppowis.fsf@nosuchdomain.example.com> <85d6240f-6877-4883-958a-45eff606abe3n@googlegroups.com>
 <871rgsqtfv.fsf@gaheris.vdwege.eu>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <07d9e1d0-734f-47bf-87e8-33942173036cn@googlegroups.com>
Subject: Re: SweetAda 0.1g released
From: Gabriele Galeotti <gabriele.galeotti.xyz@gmail.com>
Injection-Date: Tue, 17 Nov 2020 10:49:03 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2374
X-Received-Body-CRC: 3557657612
Xref: reader02.eternal-september.org comp.lang.ada:60596
List-Id: <comp.lang.ada>

On Tuesday, November 17, 2020 at 9:30:05 AM UTC+1, Mart van de Wege wrote:

> That's because Let's Encrypt issued you a certificate for 
> www.sweetada.org, with www.sweetada.org as a Subject Alternative Name. 
> 
> Subject: CN = www.sweetada.org 
> 
> X509v3 Subject Alternative Name: 
> DNS:www.sweetada.org 
> 
> I'd say that's a broken certificate. I have no clue why they would issue 
> it that way, unless you made a mistake in your Certificate Signing 
> Request. Unfortunately, I do not use Letsencrypt, so no clue where it 
> went wrong. The norm is to have a cert with Subject (in this case) 
> sweetada.org with www.sweetada.org as the SAN. 
> 
> Mart 
> 
> -- 
> "We will need a longer wall when the revolution comes." 
> --- AJS, quoting an uncertain source.

Many thanks for your hints.
If an error exists, it's obviously mine.
I'll take into account what you say e maybe one of next weekends I'll try to correct everything.
In the meantime, use only the (apparent) secure https://www.sweetada.org connection.
Best regards
G