Sujet : Re: test tcpreset news on onion 119
De : info (at) *nospam* tcpreset.invalid (Gabx)
Groupes : misc.testDate : 02. Apr 2025, 06:37:22
Autres entêtes
Organisation : Victor Usenet Postings
Message-ID : <vsiiej$suiq$1@news.tcpreset.net>
References : 1 2 3 4
User-Agent : flnews/1.2.1 (for GNU/Linux)
Stefan Claas wrote:
No, but why not announce your news server in a way that it
only can be used via your new web interface, which explains
how it works, and via my m2n? That way it works, like before
heheheh no it was not a monopoly attempt
with your onion address and port 119, and client users can
configure their news client for onion and 119, because it
is then encrypted and not advertising 563 for clearnet,
because which a.p.a-s users (and others) would use that?
It was all like this from the beginning. At the beginning innd also
managed nnrpd port 563 (ssl with letsencrypt) which has always
been there. Port 119 has never been completely clear and for onion
as you say.
I really wanted to avoid this.
on the official documentation it is written to separate the two
processes with different init files. my mistake was to launch
a killall nnrpd.
This is what brought me to the point of no return where we are now.
It is also through mistakes that we understand things.
Port 563 with TLS is only useful for non-anonymous users
who register with a news server, so that their credentials
can not been seen by third parties.
Not just for credentials mate ;)
Gabx