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

Not connecting in ubuntu 20.04 #285

Open
the-loudspeaker opened this issue Aug 19, 2020 · 5 comments
Open

Not connecting in ubuntu 20.04 #285

the-loudspeaker opened this issue Aug 19, 2020 · 5 comments

Comments

@the-loudspeaker
Copy link

Used to work fine in Ubuntu 18.04 but does not work in 20.04. The client connects and disconnects immediately.
There seems to be some tls error. Here are the error logs from quasselcore: https://p.ip.fi/HYvY

@digitalcircuit
Copy link
Contributor

digitalcircuit commented Jan 25, 2021

As a workaround, when connecting, expand more options and disable SSL core connection. Not ideal, but if your Quassel core is localhost, it's not the end of the world.

My current guess is there's an issue with node-libquassel with newer (TLSv1.3) setups. Instead of secureProtocol in createSecureContext() options, libquassel should use minVersion… but I'm still figuring out how to test these changes.

Edit: After other edit attempts failed, manually editing the compiled libquassel.js doesn't seem to work, either - setting minVersion still fails.

Edit 2: I've not been able to figure out the SSL/TLS bug, so I've set up securecore: false by default on Ubuntu 20.04+ since it's localhost anyways. Again, not ideal, but ah well.

digitalcircuit added a commit to digitalcircuit/salt-box-quassel that referenced this issue Jan 26, 2021
Work around SSL/TLS bug on Ubuntu 20.04+ by disabling the "securecore"
setting.  As the core connection is via 'localhost', the potential
impact is reduced.
See magne4000/quassel-webserver#285

Also work around a Quassel Webserver bug where the "securecore"
setting does not get applied by default if set to false.  This can be
dropped once the upstream pull request is merged.
See magne4000/quassel-webserver#290
@the-loudspeaker
Copy link
Author

As a workaround, when connecting, expand more options and disable SSL core connection. Not ideal, but if your Quassel core is localhost, it's not the end of the world.

My current guess is there's an issue with node-libquassel with newer (TLSv1.3) setups. Instead of secureProtocol in createSecureContext() options, libquassel should use minVersion… but I'm still figuring out how to test these changes.

Edit: After other edit attempts failed, manually editing the compiled libquassel.js doesn't seem to work, either - setting minVersion still fails.

Edit 2: I've not been able to figure out the SSL/TLS bug, so I've set up securecore: false by default on Ubuntu 20.04+ since it's localhost anyways. Again, not ideal, but ah well.

Yes i had it localhost and it worked. But now my quasselcore shifted to another machine so now I cannot use this workaround. Seems it is referenced in a commit. Will check that out and see how it works.

@the-loudspeaker
Copy link
Author

I have just tried it in ubuntu 20.04, my quasselcore is in ubuntu 18.04. Doesn't directly work with ssl core connection enabled in quassel-webserver. I have to disable it once, connect to my core. then logout and then from next time onwards it works with ssl core connection ticked.

after that it works like normal.

@magne4000
Copy link
Owner

This comment can be of interest magne4000/node-libquassel#25 (comment)

@mtrolley
Copy link

mtrolley commented Aug 2, 2023

The suggestion above about disabling "SSL core connection" doesn't work for me. The core log still shows even with that option unchecked:

2023-08-02 18:11:42 [Info ] Client connected from 172.18.0.6
2023-08-02 18:11:42 [Warn ] "Socket error 13: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm"
2023-08-02 18:11:42 [Info ] Non-authed client disconnected: 172.18.0.6

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

4 participants