java ssl viewer

[Rudi De Vos]

http://sc.uvnc.com/javaviewer/index.html

[Rudi De Vos]

jar updated (signed)
cgi script changed so netscape also works

Using signed jar, prowy settings now also works.

[Zagrophyte]

It appears that there is a bug with this release, "TestB" is set to the buf2 variable, and must be recompiled from source with the "TestB" taken out, or it will not work with a repeater.

I have recompiled using JRE1.5_06:
http://www.juxentente.com/~zenzagg/VncViewer.jar

Here is a standalone GUI Java my friend made:
http://www.juxentente.com/~zenzagg/dist.rar

I have not fixed the RFB 16 error though.


Reference:
[topic=5953][/topic]:

finally i'm gonna resolve the problem by myself,
i succesfully connected the javaViewer to the repeater by editing the following line in RFBRepeaterSocketFactory

Code: Select all

final String buf2 = "testB";

by

Code: Select all

final String buf2 = "";

don't know what is testB used for.

Then I successfuly took control of the comp where winncv.exe was running whith a client added to the repeater.

Next step was using SC to connect to repeater, all was ok till a tried to remote control it with the javaViewer. Connection was succesfully established the SC try icon went green for a sec then the javaViewer crashed with the next error :

Code: Select all

java.lang.Exception: Unknown RFB rectangle encoding 16
Error: Unknown RFB rectangle encoding 16
	at vnc2.VncCanvas.processNormalProtocol(VncCanvas.java:448)
	at vnc2.VncViewer.run(VncViewer.java:240)
	at java.lang.Thread.run(Unknown Source)

any1 faster then me can help?

[topic=4678][/topic]

Viewer accept, 127.0.0.1:1159
DBG: remotehost testBID remoteport 1234
resolving host by name: testBID
failed to resolve locally.
Unable to connect to destination host, errno=6

I had this same error:
"resolving host by name: testBID"
but I was not using host by name but only IP address.

[redge]

SCIII fail with java SSL viewer

symptom:
Error: Unknown RFB rectangle encoding 16

cause:
SCIII with and without CERTIFICATE.PEM
http://sc.uvnc.com/sciii/winvnc.exe
and
http://sc.uvnc.com/sciii/sciii_test4.exe

-id 12345 -sslproxy -connect 216.55.178.47:443 -noregistry
or
-id 12345 -sslproxy -connect 216.55.178.47::443 -noregistry


workaround solution:
work for classic winvnc manually initiate outgoing connection
uvnc.com:5500
and
http://sc.uvnc.com/javaviewer/index.html
success !


question:
need new update SCIII winvncsc or new CERTIFICATE.PEM ?

[superwopguy]

Does Single Click work with the ONLINE Java Viewer!!!

I can successfully connect the Online Java viewer to a winvnc client running uvnc.com and any ID.

However, when ever I try to connect the Online Java Viewer to a single click client running uvnc.com:5500 it does not work. Can someone please tell me how to successfully connect ultravnc sc to the online java viewer here:

http://sc.uvnc.com/javaviewer/index.html

[redge]

currently,
SCIII does not work with javaviewer SSL
Javaviewer SSL accept actually only the RFB protocol.
or
bug or limitation of javaviewer on uvnc.com ?

[superwopguy]

I'm curious to know who is working on this fix (SC connection to online ssl javaviewer) and if I can help in any way. My java knowledge is very limited but I am always available as a BETA tester. Please let me know...

[redge]

https://sc.uvnc.com/javaviewer/index.html

6 month for finding one bug ...
this certificate not allow to open the SSL web site (bloqued, unpossible to force accept) and indeed, could not be used with SCIII for this reason ?

[lokkju]

It seems the problem has to do with the defines for the encoding.

In WinVNC (rfb/rfbproto.h), there are 10 encodings defined, 0 to 9, and 16

In the javaviewer, there are only 8, 0 to 7

the VNC SC, I would guess, must be set to not try to push the ones the javaviewer does not handle...

How hard would it be to add support for ZlibHex, Ultra, and ZRLE to the javaviewer?

[lokkju]

After a bit more research, I think I found the root of the problem. in vncEncodeMgr.h, you will find the following:

Code: Select all

	case rfbEncodingTight:
	case rfbEncodingZlib:
	case rfbEncodingZlibHex:
	case rfbEncodingZRLE:
		vnclog.Print(LL_INTINFO, VNCLOG("ZRLE encoder requested\n"));
		if (!zrleEncoder)
			zrleEncoder = new vncEncodeZRLE;
		m_encoder = zrleEncoder;
		break;

If you notice, Tight, Zlib, and ZlibHex ALL use ZRLE instead of their own encoders - and the java viewer does not support ZRLE. To me, this seems like a major, major, bug - no viewer really ever connects with Tight or Zlib encoding!