If you see different IPs logging into a use account from several IPs all at the same time. How do I prevent / ban / block this from happening?

Is this what the protector mod is for? I have Protector v3.5.
Also I get the following errors for the protector settings page

Warning: require_once(XOOPS_ROOT_PATH/class/pagenav.php) [function.require-once]: failed to open stream: No such file or directory in ..../modules/protector/admin/index.php on line 3

Fatal error: require_once() [function.require]: Failed opening required 'XOOPS_ROOT_PATH/class/pagenav.php' (include_path='.:/usr/local/php5/lib/php') in ....../modules/protector/admin/index.php on line

This is my line 3
require_once XOOPS_ROOT_PATH.'/class/pagenav.php' ;

can you guys please tell me if this is what protector is for?

Hiya,

The IP restriction can be done with code modification to the core and database to properly work and what version of Xoops are you using now (As I know you upgraded earlier).

Also, what is the lines above

require_once XOOPS_ROOT_PATH.'/class/pagenav.php' ; at line 3?

here U are:
http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=94&cid=1&easiestml_lang=xlang%3Aen

Not to cloud the issue, but how does this help her?

Just add the groups in protector prefs you wish not to move IP in session, that you wish not to be able to hop about.

Hey Catz,
Since the upgrade I no longer have the protector errors (above).

The problem I am having with protector is that I know nothing about that stuff so Red-Slider sending me the link, although you are trying to help, really just adds to my confusion.

When I read what it does, I don't understand the terminology

DoS - what is dos? To me that is early programming code.
- Bad Crawlers (like bots collecting e-mails...) - this I get
- SQL Injection - ???
- XSS (not all though) - ???
- System globals pollution - ???
- Session hi-jacking - I think this is what I need but I really don't know what that is. All I know about session is that sometimes my site logs me out and gives me a session error. Or if I take too long to create a post I will get a session error.

RedSlider is this protector diff from the version that comes with 2.4.4? Should I be using this one instead or should I try what MadDan suggested.

You guys will have to tell me exactly what file to edit and exactly where in the file to put the code.

Thanks

1) Just use the Protector that comes with XOOPS, as it takes advantage of Preloads

2) In the Admin go to the Protector

3) It should open in the "Protect Center" Tab

4) At the "Bad IP" box, input the IP that you want to block

5) click on "Go" and you're done

Don't worry about anything else...

Welcome
I see that I created a little confusion. You asked, so I sent to the source - the module creator site.
Protector is like a firewall. Prevents many attacks on your the portal. It's really a fantastic tool. GIJOE was I gave you, you can read more about the methods of hacking (etc.) - the sum of all the risks to which your site is exposed.

As to your questions about the different methods of attack will send to google.
DoS - what is dos?
- Bad Crawlers (like bots collecting e-mails...) - this I get - OK
- SQL Injection - ???
- XSS (not all though) - ???
- System globals pollution - ??? - almost all the rest
- Session hi-jacking - I think this is what I need but I really don't know what that is. All I know about session is that sometimes my site logs me out and gives me a session error. Or if I take too long to create a post I will get a session error.
- yes - but that hijack your session, and gives 4e admin permissions on your site

There are many pages about hacking - I recommend to read some basic articles on temad most popular methods - this will allow you to understand the attack and operation of the Protector.

Quote:

You ask whether to use the version of the package if the version of the GIJOE. The answer is simple - when configured with a module, then use this bundle.

Quote:
And now the answer to your question.
Quote:
1. I understand that you know the IP number that you want to block.
2. You have two options:
a) go into: yoursite.com/http://smartklub.pl/modules/system/admin.php?fct=preferences&op=show&confcat_id=1
look into last filed. Here U can put IP adress, that U want to block
b) go into: yoursite.com/modules/protector/admin/index.php
look onto first field - and do the same

I hope this time I helped ;)

I think all of you have gone right off in the wrong direction from what she is asking, she wants to know how to prevent the SAME user from a different IP from logging into the site. This way, a user who has paid membership cannot just hand over their login details to someone else and then expect still to login to the system.

Sure protector will ban an IP address and stop them from logging into the system, but she first needs to know the IP address and secondly, she really doesn't want to sit there examining everyone who logs in to see what IP address they are using.

Now while this can be done, there are issues that need to be looked at first.

Not every IP address is static, for example, DSL connections IP addresses are rotated frequently and this is where the problem will arise. So, preventing a user from logging in with a different IP address, may affect legitimate users in reality.