- DC++ since version 0.868
ApexDC++ since version 1.6.5
AirDC++ since version 3.53
EiskaltDC++ since version 2.2.10 (openssl version 1.1.1+ needed).
FlylinkDC++ since build 21972.
Some 'DC over TLS' explanations
Moderator: Demona
4 posts
• Page 1 of 1
TLS 1.3 ready clients are:
ApexDC++ since version 1.6.5
AirDC++ since version 3.53
EiskaltDC++ since version 2.2.10 (openssl version 1.1.1+ needed).
FlylinkDC++ since build 21972.
Last edited by Delion on Fri Jan 01, 2021 6:45 pm, edited 2 times in total.
- Delion
- Posts: 141
- Joined: Thu Nov 15, 2018 12:37 pm
TLS 1.2 ready clients are:
N.B. Up to build 21972 FlylinkDC++ has secure С2С connections disabled and forbidden by default.
- DC++ since version 0.850
ApexDC++ since version 1.5.14
AirDC++ since version 3.00
FlylinkDC++ since build 19482.
N.B. Up to build 21972 FlylinkDC++ has secure С2С connections disabled and forbidden by default.
Last edited by Delion on Fri Jan 08, 2021 3:38 am, edited 10 times in total.
- Delion
- Posts: 141
- Joined: Thu Nov 15, 2018 12:37 pm
We (me and cologic) did some digging in StrongDC++ code and its field TLS support.
The fact is: StrongDC++ has TLS connections broken. It could connect modern DC clients due to some common ciphers, but just can't do it because of who-knows-why.
The fact is: StrongDC++ has TLS connections broken. It could connect modern DC clients due to some common ciphers, but just can't do it because of who-knows-why.
- Delion
- Posts: 141
- Joined: Thu Nov 15, 2018 12:37 pm
4 posts
• Page 1 of 1