Menu
▾
▴
#741 Auto-ban Feature Versus Brute Force Attacks
open
5
2020-07-06
2018-05-15
No
To whom it may interest,
Despite OS server capabilities of temporarily denying access to IPs from brute force attacks, it would be more efficient if there was an auto-ban feature implemented directly on TightVNC Access Control tab...
Att, Felipe Sofia Zanuzzo
An auto-ban feature would be a great addition .
Currently tightvnc is a time delayed open hole for all sorts of hackers.
On real server environments it is not an issue as there is somekind of firewall built in somewhere + someone having an eye on systems.
BUT tightvnc is also widely used by individuals on not-server environments with basic routers and windows 10 in its dumbest form.
As hackers do have time and resources, they can simply brute force the credentials with 10.ths of thousands login attempts without user having no warning whatsoever. All failed login attempts are nicely logged in windows logs, but which user does review these logs when the system runs fine?
Please figure out whether it will be an autoban or user notification what is needed. This is not some fancy UI improvement but a real security issue.