1. It forces Path2ban into either menu callback or hook mode. Previous versions could allow users to use both, potentially resulting in duplication.
2. It includes system status "requirements" to make sure that the settings are set correctly. On previous versions going back to 1.0 the user could delete the site_403 and site_404 entries, silently stopping Path2ban from working.
1. It forces Path2ban into either menu callback or hook mode. Previous versions could allow users to use both, potentially resulting in duplication.
2. It includes system status "requirements" to make sure that the settings are set correctly. On previous versions going back to 1.0 the user could delete the site_403 and site_404 entries, silently stopping Path2ban from working.
1. It forces Path2ban into either menu callback or hook mode. Previous versions could allow users to use both at once (resulting in duplication) or neither just by incorrectly setting the configuration.
2. It includes system status "requirements" to make sure that the settings are set correctly. On previous versions going back to 1.0 the user could delete the site_403 and site_404 entries, silently stopping Path2ban from working [I'm classing this as a bug fix].
Added new entry - hackers sometimes look for swap (temporary) files of settings.php - this prevents that.
Added new feature - a count of blocked visitors, visible on the settings page.
Allows path2ban that uses a hook as its action. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated in this module, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
This is the first iteration of path2ban that uses a hook as its action. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated in this module, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
This is the first iteration of path2ban that uses a hook as its action. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated in this module, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
This is the first iteration of path2ban that uses a hook as its action. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated in this module, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
This is the first iteration of path2ban that uses a hook. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. I am likely to select a different hook for it eventually. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
This is the first iteration of path2ban that uses a hook. It should be compatible with customised 404 pages such as search 404, and Drupal's core customised 404 pages. The exception is fast_404, because it behaves quite differently. I am likely to select a different hook for it eventually. A much lower level hook (e.g. init, boot) would require some Drupal core functions to be duplicated, which I'm hesitant to do.
To enable this feature go to the path2ban config page and check the "Use hook" tick box.
1. Adds a new "ignore path2ban" role, replacing the old "test mode".
2. New entries to ban bots attempting to exploit Drupalgeddon 2 - not a substitute for patching!
Other maintenance includes the moving of default entries into a separate file.