You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've spent some time digging into why my quassel-webserver will no longer connect to my quassel core. According to quassel and quasseldroid, my core uses TLS 1.3, but I have found the following:
Which appears to set libquassel to only use TLS 1.2.
According to the node TLS documentation, this is now deprecated, and we should be using minversion when creating an SSL context.
Suggest changing this line to:
minVersion: 'TLSv1.2'
Though i may be barking entirely up the wrong tree here, as i'm not a node developer. It looks like someone else tried this previously in quassel-webserver: magne4000/quassel-webserver#285
The text was updated successfully, but these errors were encountered:
That's not actually webquassel (the node process) that initiates TLS connection to the server, but directly the browser thanks to forge.
So to support TLS1.3 this repo either need an updated version of forge that supports TLS1.3 (still no implemented), or find another method or lib.
Sadly is not an easy thing to do if it's even possible, and I'm not actively keeping this repo updated, so for now it's not on the list of things that will be implemented by me (PR or suggestions welcome though)
I've spent some time digging into why my quassel-webserver will no longer connect to my quassel core. According to quassel and quasseldroid, my core uses TLS 1.3, but I have found the following:
node-libquassel/src/request.js
Line 160 in 0cf9737
Which appears to set libquassel to only use TLS 1.2.
According to the node TLS documentation, this is now deprecated, and we should be using minversion when creating an SSL context.
Suggest changing this line to:
Though i may be barking entirely up the wrong tree here, as i'm not a node developer. It looks like someone else tried this previously in quassel-webserver: magne4000/quassel-webserver#285
The text was updated successfully, but these errors were encountered: