From: Mojca Miklavec via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: The certificate of the mailman site has expired
Date: Mon, 25 Oct 2021 10:51:40 +0200 [thread overview]
Message-ID: <CALBOmsYKN79L-x-2uRtwFUj1yTX0NxgV0dSD500dm0u9wEX9Zw@mail.gmail.com> (raw)
In-Reply-To: <CAMD5SRMstPQS949ybP097mxVfzi3ehFwwAUe_+WLodrKh-CB=w@mail.gmail.com>
On Mon, 25 Oct 2021 at 00:46, Ramkumar KB via ntg-context wrote:
>
> Taco,
>
> Chrome browser says R3 (in the certificate chain) has expired.
>
> See attached screenshot.
Are you using macOS <= 10.14?
I see Let's Encrypt mentioned and that one has been causing some
issues lately, partially due to a not-well-defined algorithm for
treating multiple certificates in the chain.
A bit more about the issue (very macOS-centric) can be read here:
https://trac.macports.org/wiki/ProblemHotlist#letsencrypt
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-25 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 0:21 Gerben Wierda via ntg-context
2021-10-22 7:15 ` Taco Hoekwater via ntg-context
2021-10-22 8:11 ` Gerben Wierda via ntg-context
2021-10-24 3:26 ` Ramkumar KB via ntg-context
2021-10-25 8:51 ` Mojca Miklavec via ntg-context [this message]
[not found] <CAMD5SRP_R9o57wEBPgjoN93VZrzuev1P_g=FBZBkvNEoypMF5Q@mail.gmail.com>
2021-10-24 9:04 ` Gerben Wierda via ntg-context
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=CALBOmsYKN79L-x-2uRtwFUj1yTX0NxgV0dSD500dm0u9wEX9Zw@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=mojca.miklavec.lists@gmail.com \
/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).