From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: 9front@9front.org
Subject: Re: [9front] https with tcp80 in 2023?
Date: Wed, 10 May 2023 17:16:31 -0500 [thread overview]
Message-ID: <af46354f-c98c-f851-baad-90a824be32de@tcp80.org> (raw)
In-Reply-To: <240B4438BC9A174FF3E9015A701C8D86@smtp.pobox.com>
I'm willing to bet your hostowner factotum has lost the private key at
some point. That's usually what precipitates this problem for me.
next prev parent reply other threads:[~2023-05-10 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:35 sirjofri
2023-05-10 21:41 ` Yury Chumak
2023-05-10 22:11 ` unobe
2023-05-10 22:16 ` B. Atticus Grobe [this message]
2023-05-11 16:30 ` Julien Blanchard
2023-05-11 19:45 ` sirjofri
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=af46354f-c98c-f851-baad-90a824be32de@tcp80.org \
--to=grobe0ba@tcp80.org \
--cc=9front@9front.org \
/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).