From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org, git@vger.kernel.org
Subject: TLS on news.public-inbox.org [was: may be unstable]
Date: Mon, 24 Jun 2019 19:03:51 +0000 [thread overview]
Message-ID: <20190624190351.GA12888@dcvr> (raw)
In-Reply-To: <20190621172120.kt2txjqbvsvdxidx@dcvr>
Eric Wong <e@80x24.org> wrote:
> Hopefully I didn't break anything, stress testing some stuff
> and my own Internet connection is intermittent :<
STARTTLS is now available on port 119, and NNTPS on 563.
I think it works... :x
No idea if it's actually secure or not; but it might help
get around firewalls or traffic filtering.
I'm using Let's Encrypt and IO::Socket::SSL defaults for
SSL_server=1. This is with the libiosocket-ssl-ssl-perl 2.044-1
package in Debian stable (9.x),
Anyways there's a boatload of changes and size reductions aimed
at C10K+ parallelism starting at:
https://public-inbox.org/meta/20190624025258.25592-1-e@80x24.org/
But OpenSSL/IO::Socket::SSL overhead remains disappointing,
even with SSL_MODE_RELEASE_BUFFERS :<
HTTPS work hasn't started, yet (but I figure most folks are
using nginx + varnish); and there's other bugs and stuff
I'd need to look at...
prev parent reply other threads:[~2019-06-24 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 17:21 nntp://news.public-inbox.org/ may be unstable Eric Wong
2019-06-24 19:03 ` Eric Wong [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190624190351.GA12888@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).