From: Fred <fm...@do...> - 2002-04-30 16:16:29
|
Thanks. I don't suppose this can be done by TightVNC itself? I'm not a system administrator, so I'd probably have to learn tons of stuff if it has to be done outside of TightVNC. Also, I'm not even sure I have the permissions to set something like that up. Fred Ross Presser wrote: > > > Yeah, it might be better to respond to multiple failed connections with a delayed response. So the 4th authorization failure won't report failure for 10 seconds, the 5th failed connection won't report it for 30 seconds, etc. > > > -----Original Message----- > > From: David Brodbeck [mailto:da...@in...] > > Sent: Tuesday, April 30, 2002 9:31 AM > > To: Fred > > Cc: vnc...@li... > > Subject: Re: -via vs explicit ssh; malicious connections to server > > > > > > On Tue, 2002-04-30 at 02:14, Fred wrote: > > > (2) From what I can see, someone could repeatedly > > > try to connect to a vncserver as often as they wish. > > > Is there a way to lock or suspend the vncserver > > > process after 3 failed connection attempts? I run > > > the server on solaris 8. > > > > Be careful with this. You're basically giving anyone the ability to > > shut down your VNC server, a classic "denial of service" attack... > > > > -- > > > > David Brodbeck, System Administrator > > InterClean Equipment, Inc. > > Ann Arbor, Michigan > > da...@ma... > > (734) 975-2967 x221 > > > > > > ___________________________________________________________ > > TightVNC mailing list, VNC...@li... > > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list > > -- ------------------------------------------- Fred Ma Department of Electronics Carleton University, Mackenzie Building 1125 Colonel By Drive Ottawa, Ontario Canada K1S 5B6 fm...@do... =========================================== |