-
Notifications
You must be signed in to change notification settings - Fork 274
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
Missing support for TLSv1.3 #1370
Comments
|
tl;dr : TLS 1.3 is not supported by the application. HTTPS support is provided by the Ararat Synapse library. The last stable release was in April 2012, and last commits in August 2018. I wouldn't hold my breath to see TLS 1.3 implemented upstream. This project has its own copy of the library in the |
|
Commeting to subscribe |
Why? It's not like 1.x is going anywhere. |
https://github.com/transmission-remote-gui/transgui/releases/download/v5.18.0/transgui-5.18.0-x86_64-win64.zip |
|
what about changing the library ? |
|
@nono723, there is an option. transgui-5.18.0-i386-win32.zip + OpenSSL 1.0.2zb VC9 (nasm 2.13.03) x86.zip |
|
If you still need TLS 1.3 support, my fork switched to OpenSSL 3 as the Synapse library has been updated by the author in the meantime to support newer OpenSSL versions. The provided releases include packaged OpenSSL libraries. |

Also pertinent, reverse proxy: nginx/1.18.0
Hello,
I have an issue with my current setup: I'm using nginx as a reverse-proxy for my Transmission instance which seems to work fine in the browser (Firefox 86), however when I installed transgui and attempted to connect I received this error:
I managed to connect succesfully after changing the
ssl_protocolsconfig option in Nginx from TLSv1.3 to TLSv1.2.I'm unsure if this is an OpenSSL issue or an Nginx issue, or I might have made a mistake in my Nginx configuration but I do suspect it's a client issue.
With thanks,
Graham
The text was updated successfully, but these errors were encountered: