if this passes tls options should have been removed

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

vado a dormire chi vivr? vedr?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

despite there being no tls option in both my python script
and news/inn.conf ....

:~$ openssl s_client news.tcpreset.net:119
Connecting to 2a01:4f8:c0c:2f94::1
CONNECTED(00000003)
depth=2 C=US, O=Internet Security Research Group, CN=ISRG Root X1
verify return:1
depth=1 C=US, O=Let's Encrypt, CN=R11
verify return:1
depth=0 CN=news.tcpreset.net
verify return:1

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Gabx wrote:

Stefan Claas wrote:

Gabx wrote:

vado a dormire chi vivr? vedr?

My m2n is now working again, via your onion and port 119.

?a fait plaisir
I listened to your advice

And now it is not working. :-(

When you started it first it was all so cool, until D
came and could not use Omnixmix with your server.

Well, just saying.

Regards
Stefan

--
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Stefan Claas wrote:

Gabx wrote:

vado a dormire chi vivr? vedr?

My m2n is now working again, via your onion and port 119.

?a fait plaisir
I listened to your advice

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Stefan Claas wrote:

When you started it first it was all so cool, until D
came and could not use Omnixmix with your server.

Well, just saying.

everything will be better, have I ever disappointed you?

Gabx

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Gabx wrote:

vado a dormire chi vivr? vedr?

My m2n is now working again, via your onion and port 119.

Best regards
Stefan

--
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

when it works randomly and certainties are met with absurdity

$ openssl s_client news.tcpreset.net:119
Connecting to 2a01:4f8:c0c:2f94::1
CONNECTED(00000003)
depth=2 C=US, O=Internet Security Research Group, CN=ISRG Root X1
verify return:1
depth=1 C=US, O=Let's Encrypt, CN=R11
verify return:1
depth=0 CN=news.tcpreset.net
verify return:1

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Gabx wrote:

Stefan Claas wrote:

When you started it first it was all so cool, until D
came and could not use Omnixmix with your server.

Well, just saying.

everything will be better, have I ever disappointed you?

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
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?

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.

And your server worked perfectly without TLS! :-)

Regards
Stefan

--
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

nnrpd is dead ! :)
i'm kiding

Gabx

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)