Re: SweetAda 0.1g released

[Gabriele Galeotti <gabriele.galeotti.xyz@gmail.com>]

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