Path: ...!tr3.iad1.usenetexpress.com!feeder.usenetexpress.com!tr3.eu1.usenetexpress.com!news.uzoreto.com!weretis.net!feeder8.news.weretis.net!feeder5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Bernd Rose <b.rose.tmpbox@arcor.de>
Newsgroups: news.software.readers
Subject: Re: Newsreaders eh?
Date: Mon, 19 Apr 2021 06:16:40 +0200
Message-ID: <cfif0p18y6yk.dlg@b.rose.tmpbox.news.arcor.de>
References: <gkfgs5nfgug4$.1q24cwbv2tx3l.dlg@40tude.net> <17ztypxu0bb1p$.dlg@b.rose.tmpbox.news.arcor.de> <MPG.3ae611f563b51ec39897a1@news.virginmedia.com> <12pj6jxdq5dve.dlg@b.rose.tmpbox.news.arcor.de> <ev667nuh6zgb$.17zvfeooqr4kd$.dlg@40tude.net> <m3ngctbsucpk$.dlg@b.rose.tmpbox.news.arcor.de> <s5hpmk$1hts$1@gioia.aioe.org> <rob9n4k4fgv6$.dlg@b.rose.tmpbox.news.arcor.de> <s5hshq$uq5$1@gioia.aioe.org> <1ep0k5gqchbxx.dlg@b.rose.tmpbox.news.arcor.de> <s5ibja$1h1m$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Injection-Info: solani.org; logging-data="26401"; mail-complaints-to="abuse@news.solani.org"
User-Agent: 40tude_Dialog/2.0.15.41 (95df663f.139.345)
Cancel-Lock: sha1:PDgHvu0zfn3eLcCXTh7tNpbcES8=
X-User-ID: eJwFwYEBwDAEBMCV6HuRcRD2H6F3hKv3MacblytPMOx9jqnPRKqFBTxvV6rWXFBcjWW338qZZaSPbCIJXcgXqBuViMwfya8ZzA==
Bytes: 3026
Lines: 47

On Mon, 19th Apr 2021 00:24:51 +0200, bill wrote:

> On Sun, 18 Apr 2021 20:27:12 +0200, Bernd Rose wrote:
> 
>> As long as you assign each one a different dedicated port/socket for local
>> communication, there are no problems, whatsoever, in my experience.
> 
> I agree with Bernd stunnel with Dialog should work with multiple servers.
> 
> As an example you might want stunnel.conf for dizum & eternal september.
> You could set your newsreader to server:port 127.0.0.1:11111 for dizum.
> And you'd then set the newsreader server:port to 127.0.0.1:22222 for ET.
> 
> Then I'm guessing but the stunnel.conf file would probably look like this.
>  ; dizum
>  [nntp]
>  client = yes
>  accept = 127.0.0.1:11111
>  connect = news.dizum.net:563
>  verifyChain = yes
>  CAfile = ca-certs.pem
>  checkHost = news.dizum.net
>  OCSPaia = yes
>  ;
>  ; eternal september
>  [nntp]
>  client = yes
>  accept = 127.0.0.1:22222
>  connect = news.eternal-september.org:563
>  verifyChain = yes
>  CAfile = ca-certs.pem
>  checkHost = news.eternal-september.org
>  OCSPaia = yes

Small correction: The section names in stunnel.conf need to be different,
like [nntp_dizum] and [nntp_es] or [nntp1] and [nntp2]. The rest looks
fine to me, from a quick glance.

The port numbers can not be arbitrary high. But the examples are in the
range of 16 bit unsigned and therefore okay. No port numbers should be
used, that may be used by a different server on localhost. It is best to
check against a List of well-known port numbers:

https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

Again, the examples shown should be okay.

Bernd