From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] distribution tcp110 specifies cert.pem in directory I don't have
Date: Mon, 11 Nov 2002 16:26:15 -0500 [thread overview]
Message-ID: <3b24e6a61a56d6647544bbca54159269@plan9.bell-labs.com> (raw)
> As Sam said, we finally got to upgrading to 4e. We are the Internet provider
> for a handful of folks who just use Plan 9 to support their pop accounts.
> Tcp110 referenced a non-existent cert.pem file, in a non-existent ssl directory.
> What is recommented that I do. (Currently I have turn on -p to use passwords
> in the clear. Not a reall problem since all these users dial directly into
> Borf.)
>
> What's a good reading list for figuring all this out?
see tlssrv(8) for the procedure to create a certificate.
(requires a unix machine with openssl, at the moment.)
next reply other threads:[~2002-11-11 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 21:26 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 13:35 Eric Grosse
2002-11-11 15:50 bwc
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=3b24e6a61a56d6647544bbca54159269@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).