New strange error message when connecting to a TurboVNC session

26 views
Skip to first unread message

Torsten Kupke

unread,
Apr 23, 2019, 11:37:32 AM4/23/19
to turbovn...@googlegroups.com

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


TVNC_Restart_Reboot.png

Torsten Kupke

unread,
Apr 23, 2019, 11:39:21 AM4/23/19
to turbovn...@googlegroups.com

Sorry, the appended screenshot isn't for this question. Please ignore it!

Am 23.04.19 um 17:37 schrieb Torsten Kupke:

DRC

unread,
Apr 23, 2019, 11:52:25 AM4/23/19
to turbovn...@googlegroups.com

This issue is fixed in the 2.2.x pre-release:

https://turbovnc.org/DeveloperInfo/PreReleases

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.

Torsten Kupke

unread,
Apr 23, 2019, 12:54:02 PM4/23/19
to turbovn...@googlegroups.com

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!


Am 23.04.19 um 17:52 schrieb DRC:

DRC

unread,
Apr 23, 2019, 1:58:24 PM4/23/19
to turbovn...@googlegroups.com
This issue is in the viewer, so you don't need to install anything on
the host. Just install the pre-release on your client machine.

On 4/23/19 11:53 AM, Torsten Kupke wrote:
> 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!
>
>
> Am 23.04.19 um 17:52 schrieb DRC:
>>
>> This issue is fixed in the 2.2.x pre-release:
>>
>> https://turbovnc.org/DeveloperInfo/PreReleases
>>
>> 2.2.2 will be released soon.  I'm working on a high-priority bug fix
>> for it right now.
>>
>>
>> On 4/23/19 10:37 AM, Torsten Kupke wrote:
>>>
>>> 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
>>>
>>>
>>> --
>>> 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
>>> <mailto:turbovnc-user...@googlegroups.com>.
>>> <https://groups.google.com/d/msgid/turbovnc-users/d02f9ff9-5b5b-a770-4e50-cb7c172af05b%40hacon.de?utm_medium=email&utm_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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
>> <mailto:turbovnc-user...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/turbovnc-users/26b9786c-8de0-c804-1a71-a19819ff532d%40virtualgl.org
>> <https://groups.google.com/d/msgid/turbovnc-users/26b9786c-8de0-c804-1a71-a19819ff532d%40virtualgl.org?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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
> <mailto:turbovnc-user...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/turbovnc-users/713c0dd8-6d11-c7e8-cc31-95dac1648e4d%40hacon.de
> <https://groups.google.com/d/msgid/turbovnc-users/713c0dd8-6d11-c7e8-cc31-95dac1648e4d%40hacon.de?utm_medium=email&utm_source=footer>.

Torsten Kupke

unread,
Apr 24, 2019, 6:26:56 AM4/24/19
to turbovn...@googlegroups.com
Sent this today morning already. Don't know, why it was ignored by
Google. Have removed some old mail texts here.

Hi DRC,


in my case the client and the host are the same machine. This way I
locally can work with the same session as from remote. My remote client
is Windows, where I don't use the Java client but the vncviewer.exe.

Best regards

Torsten

Torsten Kupke

unread,
Apr 26, 2019, 10:27:28 AM4/26/19
to turbovn...@googlegroups.com
Hi DRC,

in my case the client and the host are the same machine. This way I
locally can work with the same session as from remote. My remote client
is Windows, where I don't use the Java client but the vncviewer.exe.

Best regards

Torsten


DRC

unread,
Apr 26, 2019, 10:30:20 AM4/26/19
to turbovn...@googlegroups.com

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.

Reply all
Reply to author
Forward
0 new messages