Access Blocker Support Thread

[swguy]

Hmm.... not having much luck so far. Entered my API key and turned on Access Blocker, then entered country codes CN,HK (the source of the bad traffic.)

However, there's no downward movement in Who's Online.

Also tried setting the top 2 octets of the IP and even the Organization for good measure, but not seeing any changes. Getting new sessions by the second from the bad guy address.

[swguy]

I may have misunderstood the design intent. If this plugin only blocks access to the create account (etc.) pages, I wonder if it would be possible to extend it to block access to ALL pages based on the configuration.

[lat9]

I may have misunderstood the design intent. If this plugin only blocks access to the create account (etc.) pages, I wonder if it would be possible to extend it to block access to ALL pages based on the configuration.

Yes, Access Blocker is a pseudo-recaptcha in that it does all its blocking at the server level (nothing for the script-kiddies to grab on).

What you're looking for, IMO, is an automatic .htaccess generator (dangerous to do on the fly for busy shops).

[swguy]

I quite agree it would be risky to attempt to update the .htaccess file as part of storefront processing (because of the danger of having it done simultaneously by multiple threads). But what if the logic was to add these bad IPs to a table, and have a separate process regenerate the .htaccess from a cron job ?

[lat9]

I quite agree it would be risky to attempt to update the .htaccess file as part of storefront processing (because of the danger of having it done simultaneously by multiple threads). But what if the logic was to add these bad IPs to a table, and have a separate process regenerate the .htaccess from a cron job ?

That's outside of the scope I intended for this module.

[swguy]

Right - this would be done as a separate project.

[lat9]

I've just submitted v1.1.1 of the Access Blocker to the Zen Cart moderators for review; I'll post back here when it's available for download.

This release corrects the generation of PHP notices when one or more of the submitted form-fields is missing; see GitHub issue #8.