VNC source code is readily available, along with some pretty optimized code for
Rijndael AES.
A little cut and paste, viola! you now have a fully encrypted VNC stream and a package
installation
that no hacker is going to download somewhere. You also don't have to deal with
"wrappers" etc,
which is often a pain on WindowsNT.
Cons:
VNC is already a CPU hog, adding crypto just makes it worse.
Are you a multinational company and have crypto export controls problems?
You need a little C/C++ coding experience.
It's unsupported and your code might be buggy....but VNC is unsupported anyway.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 11:05 AM
Subject: VNC stream
> hi,
> Yes VNC does not encrypt its stream or anything like that. You need
> to tunnel via SSH. PPTP is not near as good @ encrypting the stream as
> SSH does it. (Then that problem is solved.)
> Another thing to consider is that VNC uses the same key for
> crypt as encrypt which leads to very bad karma;-)) Last time i checked
> anyhow. IIR; Therefore use it at your own risk. But then again that is with
> any sw you use.
> Best Regards
> [EMAIL PROTECTED]
> ----------------------------------------
> E-Mail: [EMAIL PROTECTED]
> Date: 09-May-2001
>
> Open Source Opens Minds. - DREAMWVR.COM
> ----------------------------------------
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
