- Changing the fixed DES key in the code will make your builds of VNC
incompatible with others but will buy little security-wise. All someone
will have to do is have a copy of your viewer or server binary to get =
key out. And of course anything you type won't be encrypted.
- The existing password system uses DES, which has 56 bit keys, which is =
7-bit characters. So 8 characters is already the maximum using that =
- Why do you want to force the encoding options? VNC already =
the ZRLE encoding and a lower number of bits per pixel for slow =
and I believe that TightVNC does the equivalent, doesn't it?
Dr. James "Wez" Weatherall
RealVNC Ltd. - http://www.realvnc.com - The Home of VNC
I have some questions about simple source code modification.
- By default, the standard DES fixed key is 23,82,107,6,35,78,88,7. If i =
change this key in the vncserver, i need to change it too in the =
and then, the only viewer which can connect to my vncserver, is the one =
compiled with my personnal DES key, right ? (i test it, it works)
So, is-it a good and simple security improvement for my vncserver or is =
totally useless XD ? ( if you not use an encrypted tunnel, i think it's=20
harder to get the password by bruteforce both challenge-response and DES =
And then ^^ the vnc server/viewer is quite easy to modify in c++, but as =
non-java-nerd ;D i can't find where is this key in the java source code, =
does someone know where is it ? (i prefer modifying the javaviewer, then =
customized viewer will wotk on every platform)
- By default the maximum password lenght is 8, and the challenge size is =
I didn't try it yet, but same questionq, is-it usefull? both viewer and=20
server need to be modified? will it block all non-modified viewer? and =
is it in this java source code XD ?
Special questions ;D: what's the maximum value? and are another=20
-How to force, in the source code, the encoding options ? i want the =
only accept connection using the so efficient tight encoding.
-I know ZVNC have a encrypted (ZeBeDe) algo built in (i've got the =
code, thanks to its author), But it's not maintained anymore, does =
know another encrypted VNC ? I know Laplink Secure VNC, but it doesn't =
for me (i guess it's not that easy to replace the standard Socket by a=20
SSLSocket or another).
I've tryed Laplink Secure VNC (SSL built in), but it doesn't wotk for =
only loopback connection works (which are not SSL) if i want to connect =
remote computer with Laplink Secure vnc server/viewer, there's no =
(not even the failed connection message). I got the exact same problem =
i tried to use SSL with an external tunneling. Does anyone knows this=20
problem. if i tried another viewer (real/java/Tight) on the Laplink =
i got the failed connection message. I tried the Laplink viewer on=20
real/tight server and it's work.
I will try SSH tomorrow, but even SSH tunneling will works, it's easier =
remote install on NT machine (which have none VNC yet of course XD) and=20
register as a service, etc... when all it's built in. A simple batch =
all i need ^^.
Thanks in advance