DRC <dcomman...@users.sourceforge.net>
writes:

> I'll look into it.  I just installed Fedora 25 yesterday.  It is not
> unusual for Fedora and other bleeding-edge distros to break things,
> because most commercial TurboVNC users are using RHEL or SLES or Ubuntu
> LTS.  Thus the majority of users won't notice issues like this until
> they make it into the enterprise/long-term distros.

This helps on the server:
VNCSERVERARGS[2]="-geometry 1024x768 -securitytypes none"

Which is of course not very good if you are not encrypting by other
means.


>
>
> On 11/30/16 5:30 AM, joa...@verona.se wrote:
>> Hello,
>> 
>> I recently upgraded my fedora25 server running a turbovnc server.
>> 
>> On a fedora 25 client I get:
>> 
>> /opt/TurboVNC/bin/vncviewer 192.168.200.66:2
>> libjawt.so path: 
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-3.b16.fc25.x86_64/jre/lib/amd64
>> CConn: connected to host 192.168.200.66 port 5902
>> CConnection: Server supports RFB protocol version 3.8
>> CConnection: Using RFB protocol version 3.8
>> com.turbovnc.rdr.SystemException: javax.net.ssl.SSLHandshakeException: No 
>> appropriate protocol (protocol is disabled or cipher suites are 
>> inappropriate)
>>      at com.turbovnc.rfb.CSecurityTLS.processMsg(CSecurityTLS.java:118)
>>      at com.turbovnc.rfb.CSecurityStack.processMsg(CSecurityStack.java:39)
>>      at 
>> com.turbovnc.rfb.CSecurityVeNCrypt.processMsg(CSecurityVeNCrypt.java:179)
>>      at com.turbovnc.rfb.CSecurityTight.processMsg(CSecurityTight.java:56)
>>      at com.turbovnc.rfb.CConnection.processSecurityMsg(CConnection.java:213)
>>      at com.turbovnc.rfb.CConnection.processMsg(CConnection.java:62)
>>      at com.turbovnc.vncviewer.VncViewer.run(VncViewer.java:838)
>>      at java.lang.Thread.run(Thread.java:745)
>> 
>> It seems some kind of cipher was removed during an upgrade of the
>> server.
>> 
>> I can still connect from another machine, which is running fedora 23.
>> This suggests something happened on the fedora 25 server, maybe some
>> cipher deprecation.
>> 
>> 
>> I tried various workarounds like
>> /opt/TurboVNC/bin/vncviewer 192.168.200.66::5902  --SecurityTypes=Tight 
>> --User=joakim  -loglevel 100
>> but so far found no working solution
>> 
>> both the problem client and server are running fedora 25, and the latest
>> 2.1 turbovnc rpm.
>> 
>> I also tried commenting out
>> #jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768
>> in java.security, on a hunch. Havent tried this on the server yet.
>> 
>> 
>> 
>
> ------------------------------------------------------------------------------
-- 
Joakim Verona
joa...@verona.se
+46705459454


------------------------------------------------------------------------------
_______________________________________________
TurboVNC-Users mailing list
TurboVNC-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/turbovnc-users

Reply via email to