You may want to consider moving away from password authentication to secure key authentication. An alternative to your current arrangement is to set up an ssh tunnel with public key authentication between the client and server and forward port 5900 through it. It would be better if you do not use the default port 22 for the sshd on the server, but another higher random number port, which will not be immediately targeted by botnets. Disabling passwd authentication and enabling public key authentication only, will make the server drop any passwd authentication attempts.
There's links to help you set this up in the Real VNC FAQs and Google. Other alternatives are to set up VPN between client and server, or to drop at the server firewall (iptables) repeated attempts from the same IP address/domain. HTH. On Sunday 22 April 2007 14:22, [EMAIL PROTECTED] wrote: > I've been using VNC happily for for many years now, with a Xvnc server > (Xvnc version 3.3.3r2+tight1.1p9) and a variety of clients, most > recently RealVNC 4.1.2 > > Last week, I found I could no longer connect, because of "too many > authentication errors." It seems that someone has been trying, so far > unsuccessfully, to break into my Xvnc server. > > My understanding what that further attempts were supposed to be > blocked only from the malicious IP, but, in fact, all attempts to > access to th server were blocked. > > This looks like an unbelievably easy DOS attack on VNC. > > Does anyone have any suggestions? I've taken my VNC server off-line > for now, but what a nuisance.... > > Many thanks. > > -Joel > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list -- Regards, Mick [demime 1.01d removed an attachment of type application/pgp-signature] _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
