This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
clients [2015/09/10 11:40] jomat |
clients [2016/04/28 21:59] jomat |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Note: this collection is work in progress, please let us know if you had trouble with your client and how you fixed it. | ||
- | |||
==== Quassel ==== | ==== Quassel ==== | ||
- | Quasselcore <0.10 usse a manual selection for the SSL protocol, and this defaulted to SSLv3. | + | Quasselcore <0.10 usse a manual selection for the SSL protocol, and this defaulted to SSLv3.\\ |
- | In version 0.10, the selector was removed and auto negotiation was used. | + | In version 0.10, the selector was removed and auto negotiation was used.\\ |
- | However, a >=0.10 client is connected to a <0.10 core, you can't change that SSL protocol. | + | However, a >=0.10 client is connected to a <0.10 core, you can't change that SSL protocol.\\ |
- | The first option is to upgrade the core to 0.10 or later. | + | The first option is to upgrade the core to 0.10 or later.\\ |
You can also either use an old client (<0.10) to change the SSL protocol to TLSv1 for that connection (once you change it, you can go back to using whichever client version you want) or update the client to 0.12-rc1, which restores the SSL protocol selector for connections to old cores. | You can also either use an old client (<0.10) to change the SSL protocol to TLSv1 for that connection (once you change it, you can go back to using whichever client version you want) or update the client to 0.12-rc1, which restores the SSL protocol selector for connections to old cores. | ||