Easier way to allow host back when got blocked

The first one, is to avoid the rogue host attempting to login again, but leaving the site accesible (where site is the rest of the public content).

Please, read the readme carefully to understand how the module operates. This is a resume. Every login attempt is tracked in the _track table. on every login form submit operation, some checks are performed to this _track table:

If there are more than N entries of any protection, it's enabled. In the case of temporary protections (soft blocking a host, delaying the submit..) the number of entries in the _track table are used to see how should operate. The time window (it's the time that attempts are 'efective' for this checks) is used to remove the old entries from the database (also cron should clean the rest). So, temporary protections could not be "removed" from anywhere, asn they will expire in a short time.

On the other hand, once a permanent protection is activated (a temporary condition like number of attempts activates the hard block of a host), a bloking operation is performed in the site, as a denying rule or just blocking a user. All these entries could be deleted using current drupal's administrative interface (even if not very userfriendly for this operation).

So, temporary protections will expire on 'time window' and can't be removed from anywhere, and permanent protections could be removed using rules or users admin interfaces.

I guess the answer did clear the idea of the two settings. Please, open again if the issue is not fixed for you.