Hi all,
today I got a new error message when connecting to a TurboVNC
session locally running on the local host:
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
I found an old issue in the closed sourceforge mailing list. One workaround there was to specify "-securitytypes none" in /etc/sysconfig/tvncservers. But this disables the password retrieval for all connections to the session (also from remote), which is not so good in my case. DRC mentioned two other workarounds there. But actually I don't know, how to do this under Ubuntu 18.04. The file /etc/crypto-policies/back-ends/java.config doesn't exist. And I cannot find such a file somewhere on the host. Is there any solution for this issue (under Ubuntu 18.04)?
Best regards
Torsten
Sorry, the appended screenshot isn't for this question. Please
ignore it!
This issue is fixed in the 2.2.x pre-release:
2.2.2 will be released soon. I'm working on a high-priority bug fix for it right now.--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/d02f9ff9-5b5b-a770-4e50-cb7c172af05b%40hacon.de.
For more options, visit https://groups.google.com/d/optout.
Very good news! I try to wait for the official release of 2.2.2,
since I don't want to install a pre-release on a host of my
employer.
Many thanks for your work!
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/26b9786c-8de0-c804-1a71-a19819ff532d%40virtualgl.org.
For some reason, Google flagged it as spam, so I had to approve the message. :/
Anyway, if you are connecting to the same machine, you would
have to be using the Linux TurboVNC Viewer, which is based on
the Java code that is susceptible to the bug in question.
Upgrade your TurboVNC package on that machine to 2.2.2, and all
should be good.