ZNC based on TightVNC

>I don't suppose you might consider using TightVNC instead of WinVNC as your >base code, would you? TightVNC is actively being developed, has many more >features, less bugs and is more stable than WinVNC. I have made the "please incorporate this technology" overture to both VNC and TightVNC, bu

new location for ZNC

Since at&t is playing domain name games, ZNC is moving to a new home. Find it at: http://home.attbi.com/~davedyer/znc/zvnc.html The is no change (except from the location) from the version you may already be using. - To uns

Re: Secure Windows Connection

First, securing VNC (or anything) is a process, not a matter of simply using some program or other. Several parties to this list have pointed out other aspects besides securing the communication stream that are known to be points of attack; for example, VNC's use of the windows registry to store

VNC for secure connections

No, the only visible change to WinVNC is to listen on port 6000+n for secure connections. It doesn't tweak with the registry usage or other options. The intent was to be completely backward compatible, which necessarily doesn't permit fixing perceived problems with the current practices. htt

Insecure VNC through corporate firewalls

Just a reminder to those concerned about the inherent insecurity of VNC protocols ( and those who would recommend tunneling with SSH ) I've produced a version of VNCViewer and WinVNC which automatically use a secure connection. I've got lots of users and no complaints: http://people.we.media

RE: VNC with builtin Encryption

>From: Glenn Mabbutt <[EMAIL PROTECTED]> >Subject: RE: VNC with builtin Encryption > >Very cool!! Feature request: pls. port it to latest TightVNC. > >Glenn You'll have to lobby the tightvnc people for that; but it may not as important as you would think. ZeBeDee (and therefore ZVNC) includes

Re: VNC with HTTPS

>This is awesome. However, I am still searching for the following. I would >like to be able to connect to the built in java client via a secure >connection from a web client (i.e. https://Some_server:port address). Any >clues to how I can set this up? No. HTTPS (secure sockets) is a comple

ZVNC tunnelnig to a nonstandard port

>Date: Mon, 1 Oct 2001 06:51:45 -0700 >From: >Subject: Re: VNC with builtin Encryption > >Is there any way to connect to do this? > >Connect to a Zebedee server running on non-standard port A and that >tunnels to a normal VNC server that runs on non-standard port B. The one I built is halfway th

New: VNC with builtin Encryption

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've built a new VNC branch which embeds the encryption and tunneling from ZeBeDee directly in the VNC server and client. The new server and client (windows only) are compatible with standard VNC and with any existing setup which uses ZeBeDee tunne

vnc with zebedee integration

I'm working on a project to integrate zebedee secure tunneling into VNC client and server. Instead of vnc server <> zebedee server <> zebedee client <> vnc client it will be possible to run zeevnc server <> zebedee client <> vnc client or vnc server <> zebedee server <>

embedding secure tuneling (zebedee) in vnc

Tunneling works with VNC, but isn't a really satisfactory solution for several reasons. (1) it's a pain to set up initially, (2) even if used properly, the insecure VNC port is still open. (3) using a tunnel server opens another point of attack on the host machine: for example, ZeBeDee's

Another option for securing VNC communication

I just discovered http://www.cs.berkeley.edu/~smcpeak/SafeTP/ It's a free, secure, and completely transparent FTP proxy. The method is similar to SSH tunneling, but easier to set up. The same methods could be used to build a transparent VNC proxy which would encrypt all VNC traffic.