TLS 1.3 support for hublist pinger [ FIXED - Hades ]

[Delion]

The subject says it all.

[Admin]

I see no reason to encript ping connections.
It doesnt get any info that needs encoding.
Usercount, date, time thats all.

As far as adc hubs i belive it does connect via ssl if addres is adcs.

[Delion]

to encrypt ping connections

The hublist pinger connects to encrypted hubs as a regular user, right? So it utilizes an encrypted connection.

What I mean is that right now that pinger won't be able to make a connection to pure TLS 1.3 encrypted hub(s).

Also, IMO TLS 1.3 has some good improvements worth using it

it does connect via ssl

Well, no...

[Admin]

Pinger pings all verlihubs via nmdcs:// with supposely tls 1.3.
I don't have any hubs (public) that run adcs with tls 1.3 to test.
All adcs hubs with tls 1.0 1.1 and 1.2 ping just fine.


Maybe u should add yours just to test for a while.

[Delion]

verlihubs via nmdcs:// with supposely tls 1.3

That verlihubs are running with_TLS_1.3_support, not via_TLS_1.3.

TLS 1.0 also can be used there (with a bunch of known problems coming with).

any hubs (public) that run adcs with tls 1.3 to test

Yepp, you are right.

But I intentionally did that test in the past and assure you: pinger won't be able to get any info.

Once again: dchublist.org pinger has no TLS 1.3 support. I think it is worth to add and use it.

[Admin]

I think i remember that.
If i have some time i will try to setup a tls 1.3 uhub for testing to check what's the deal.

[akruk]

The deal is that Delions uhub config doesn't support tls 1.2 anymore.
Drops this connections and requires strict. tls 1.3

From a php coding side we are in deep shit now as hublist wasnt converted to anything that runs on modern php versions. With that being set we are currently stuck on tls 1.2 max for s. streams.

It will take complete code rewrite (classes, functions) to work with php 7.2+ thats too much for a hobby project.

What i can do is convert just the pinger side to be php 7.2 + compatible its def less work that the whole script. That way we can ping it from modern php enviroment (can be still on same server it doesn't matter). Then it will by default use tls 1.3 if supported on the other side.

[Admin]

Pinger can be converted indeed. If u can do it and attache to mail.
I think will require to move to linux too.

Just read that xampp doesnt officially support tls1.3 on socket streams in php just yet.
Its the cURL that would need to be build against specirfc php bin with openssl 1.1.1 .

Well i can't do that.

[Admin]

This was solved long time ago.
Im closing this.