From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: [secure site not available]
Date: Thu, 15 Sep 2022 12:41:07 +0200 [thread overview]
Message-ID: <20220915124107.5fc77f9e@homerow> (raw)
In-Reply-To: <f422f34e-9cc4-179e-0f89-c0515b546652@gmx.es>
On Wed, 14 Sep 2022 19:19:05 +0200
Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
> https://lmtx.pragma-ade.nl, https://pragma-ade.nl and
> https://pragma-ade.com seem to use a certificate that is only valid
> for https://lmtx.pragma-ade.com (according to Firefox).
Correct. This is a misconfigured webserver, so the error is valid.
> Each domain (and subdomain) requires its own certificate.
That's not quite correct AFAIK. Let's encrypt supports wildcard
certificates, so
lmtx.pragma-ade.nl and
pragma-ade.nl
could be covered by the same certificate. And each certificate can
also cover multiple domains (SAN). So one certificate should be
enough for all abovementioned (sub)domains.
> (And non-automatic certificate renewal is a real pain [I have to
> add].)
I totally agree on that one.
Certbot definitely supports wildcard certificates and AFAIK you can
just specify multiple domains with the “-d” option.
Marco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-09-15 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 14:43 Floris van Manen via ntg-context
2022-09-14 17:19 ` Pablo Rodriguez via ntg-context
2022-09-15 10:41 ` Marco Patzer via ntg-context [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220915124107.5fc77f9e@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).