-
Notifications
You must be signed in to change notification settings - Fork 63
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
Swiften won't connect to the XMPP server with TLS enabled, but without StartTLS #116
Comments
Hi. Direct TLS isn't something that Swiften can currently use. It is a thing it would be useful, but I don't think any of us will have time to work on it soon, I'm afraid. |
@Kev That's OK. In the meantime I managed to implement it myself. Are you interested in the pull request? |
Yes please. Contributions are under the BSD license, with a note to that effect in the commit message (e.g. 110eb87 ) - if you're happy with that, please open a PR and we can go from there. |
OK then, I've opened a PR: #117 |
We have an XMPP server hidden behind the balancer. The balancer itself provides the TLS encryption. However it does not support upgrading a plaintext connection to an encrypted connection (a.k.a. StartTLS or opportunistic TLS). I suppose for this reason Swiften cannot connect to our server. Is it possible to set up Swiften in such a way that the connection is encrypted from the very beginning (without StartTLS command)? It is possible, e.g. in Psi (the option is called "Legacy SSL").
The text was updated successfully, but these errors were encountered: