IP Blocker for v1.5.x

is there an IP blocker mod for 1.5.1??

I used to have the blocker for 1.3.9 which allowed me and staff to block bad ips and people trying to get into admin and werid pages etc, but this isn't for 1.5.1 is there a mod out there??

ANSWER: Yes: IP Blocker for Zen Cart v1.5.0+

I usually ban them in WHM or in the .htaccess

yeah I ban through my cpanel etc..... but don't really want to give staff access to cpanel etc as they could kill everything!!!!!

also nice to be able to ban via admin then tjhat on less tab they have to have open along side the 10 tabes and screens already open

I've submitted v2.0.0 to the plugins; it will support Zen Cart versions 1.5.0 and later only and will be available here once approved. This version is organized a little bit differently than the previous version, there are no core-file overwrites and the same database structure is used.

lat9:

I've submitted v2.0.0 to the plugins; it will support Zen Cart versions 1.5.0 and later only and will be available here once approved. This version is organized a little bit differently than the previous version, there are no core-file overwrites and the same database structure is used.

Awesome, I know what I'm installing later! Thank you Lat9 :hug:

Hi Lat9
Just a thought: how about a facility when admin is informed when the special_login page is repeatedly probed?
I have an IP that I've blocked but I can see it (who's online) sat on the special_login page. Is it possible to stop these banned addresses from probing the login after X number of attempts they get a 'sod off' page. WordPress has similar plugins such as Login Lockdown.
Just a thought.

Now available in the plugins: http://www.zen-cart.com/downloads.php?do=file&id=1814

picandnix:

Hi Lat9
Just a thought: how about a facility when admin is informed when the special_login page is repeatedly probed?
I have an IP that I've blocked but I can see it (who's online) sat on the special_login page. Is it possible to stop these banned addresses from probing the login after X number of attempts they get a 'sod off' page. WordPress has similar plugins such as Login Lockdown.
Just a thought.
I'll give it a look a bit later, sounds like a good idea. My preference would be that after **X **attempts on special_login that the special_login simply display a white-page (the PHP equivalent of sod-off) and accept no additional input; does that work for you?

lat9:

I'll give it a look a bit later, sounds like a good idea. My preference would be that after **X **attempts on special_login that the special_login simply display a white-page (the PHP equivalent of sod-off) and accept no additional input; does that work for you?

That sounds perfect to me :hug:

picandnix:

That sounds perfect to me :hug:
That's the tack I'll take then; I'll update here when it's ready.

lat9:

That's the tack I'll take then; I'll update here when it's ready.

You star!

Thank You!

lat9:

I've submitted v2.0.1 to the plugins area to correct the issue discovered by kitcorsa and to add a blocked-IP, failed address lockout count to the plugin's configuration.
Now available via the plugins ...

Was just looking over the code... (Trying to see if can incorporate into another plug-in if both are installed.)

When looking at init_ip_blocker.php of the includes/init_includes directory... Seems like (and maybe I'm wrong) that upon completion of the file, the session 'ip_blocker_pass' variable is always false... Even if momentarily previously set as true inside the loop. Do I misunderstand what the code does? Ie. is there extra code that doesn't really do accomplish anything?

I'll grant that it looks funny; is it not working?

lat9:

I'll grant that it looks funny; is it not working?

So far no complaints, it was that I was taking a look to see what I would need to incorporate to add a link to choose to block an address, and so had to follow the code through. Wasn't exactly digging for each line, but the general flow. That set of instructions (setting to true in a loop/if statement) made me wonder if there was something listening for a change in the setting. If there was, then I wanted to follow through with what that code did and wanted to find it. The call to change it doesn't use the notifier code, but having not looked at everything, thought I would ask the developer. :)

Are you considering implementing a sort of consolidation function into this in the future?

Ie. Inspect all entries, if two or more are consecutive to change from two independent entries, to a single combined? And if perchance all in a subset have been added, to change to that subset? (Thus preventing the overlap described in the readme.)

mc12345678:

Are you considering implementing a sort of consolidation function into this in the future?

Ie. Inspect all entries, if two or more are consecutive to change from two independent entries, to a single combined? And if perchance all in a subset have been added, to change to that subset? (Thus preventing the overlap described in the readme.)
Nope, no plans to do this.

mc12345678:

So far no complaints, it was that I was taking a look to see what I would need to incorporate to add a link to choose to block an address, and so had to follow the code through. Wasn't exactly digging for each line, but the general flow. That set of instructions (setting to true in a loop/if statement) made me wonder if there was something listening for a change in the setting. If there was, then I wanted to follow through with what that code did and wanted to find it. The call to change it doesn't use the notifier code, but having not looked at everything, thought I would ask the developer. :)
I've submitted v2.0.2 to the plugins area to correct the session-based variable handling and to remove the debug code display from the "special login" page.