On 27/05/2021 20.20, Maximilian Trummer wrote:
And failure because they scan my router and say it is insecure and say I need to use SSL first. That's what happened on freenode. I know you don't want to hear this but it sounds like your router is a
Am Donnerstag, 27. Mai 2021, 13:30:31 CEST schrieb Carlos E. R.: liability and you should complain to your ISP about this.
I did, and they ignored me. Yes, they answered, and more or less replied they were not going to do anything. Maybe I can find out the post, if you read Spanish and you are interested... Here, I found it: <https://comunidad.movistar.es/t5/Soporte-Fibra-y-ADSL/Me-dicen-que-el-router-es-vulnerable-y-lo-pueden-usar-como-proxy/td-p/3547168> It was the ssh port on the router, which runs an ancient version of ssh. They simply told me to close that port in the router firewall (it can not be disabled, AFAIR). If you are curious: Telcontar:~ # nmap -p22 -sV router ... PORT STATE SERVICE VERSION 22/tcp open ssh Dropbear sshd 0.46 (protocol 2.0) MAC Address: .... (Comtrend) Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel ... or the old IRC logs if you read the link above.
The instructions doesn't even say the ports to use, which were not the standard of the protocol... for SSL it is 6697. But it does. https://libera.chat/guides/connect
ports 6697, 7000 and 7070 for TLS-encrypted connections. TLS and SSL mean the same here. People only say "SSL" these days out of inertia, nobody uses these insecure protocols anymore (SSLv2/3).
Well, I did not find it. Anyway, I got the setup done and connected. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telconta