From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] man.cat-v.org tls cert
Date: Sun, 30 Oct 2022 22:52:12 -0700 [thread overview]
Message-ID: <8bda79e39a0a65e3@orthanc.ca> (raw)
Duckduckgo isn't happy with the above site's tls cert. Did it
expire? Or is something more nefarious happening ...
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2e78a247283470f3-Mbf8b7ba6235d7be1557ceb04
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2022-10-31 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 5:52 Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2022-10-31 6:36 ` Kim Shrier
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=8bda79e39a0a65e3@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
/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).