Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libquassel won't connect to quassel core that only supports TLS 1.3 #25

Open
thinkl33t opened this issue Dec 7, 2021 · 1 comment
Open

Comments

@thinkl33t
Copy link

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:

secureProtocol: 'TLSv1_2_client_method'

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

@magne4000
Copy link
Owner

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants