TradeExpert Docs

User Tools

Site Tools

Trace:
te3:allowed_ips

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Last revisionBoth sides next revision
te3:allowed_ips [2014/08/08 11:52] – created moderatorte3:allowed_ips [2014/11/20 13:01] – moderator
Line 1: Line 1:
-====== Allowed IPs ====== +====== IP protect your admin interface ====== 
-Menu: {{:te3:user_logo.png?nolink|}} User / Allowed IPs +~~NOTOC~~
- +
-{{INLINETOC}} +
- +
----- +
- +
- +
- +
-===== IP protect your admin interface =====+
  
 +  * [[te3:allowed_ips#allowed ips|Allowed IPs]]
 +  * [[te3:allowed_ips#.htaccess|.htaccess]]
 +  * [[te3:allowed_ips#PHP files inside /te3/ directory|PHP files inside /te3/ directory]]
  
  
Line 16: Line 11:
 You should use all of the available security measures to make that task as hard as possible for them. We will describe two measures how you can and should protect yourself. TE3's "Allowed IPs" module & ''.htaccess'' file protection. It is strongly recommended that you use at least one method. Of course ''.htaccess'' method might be better, it is bullet proof (IPs / IP blocks are blocked on the server level) and it is also more flexible (you can specify exactly which files you want to block), but for a novice user it might be a bit trickier to configure. For additional protection, you can use both methods simultaneously. You should use all of the available security measures to make that task as hard as possible for them. We will describe two measures how you can and should protect yourself. TE3's "Allowed IPs" module & ''.htaccess'' file protection. It is strongly recommended that you use at least one method. Of course ''.htaccess'' method might be better, it is bullet proof (IPs / IP blocks are blocked on the server level) and it is also more flexible (you can specify exactly which files you want to block), but for a novice user it might be a bit trickier to configure. For additional protection, you can use both methods simultaneously.
  
-<color blue>If you have a static IP</color> (IP is never changing) on your home machine, it is very simple to configure "Allowed IPs" module. Open {{:te3:user_logo.png?nolink|}} ''User'' drop down menu in the [[te3:admin_panel|Admin panel]] and click on ''Allowed IPs'' then simply add your IP ( 213.161.30.4 ) into the textarea and press ''Update'' button.+**If you have a static IP** (IP is never changing) on your home machine, it is very simple to configure "Allowed IPs" module. Open {{:te3:user_logo.png?nolink|}} ''User'' drop down menu in the [[te3:admin_panel|Admin panel]] and click on ''Allowed IPs'' then simply add your IP ( 213.161.30.4 ) into the textarea and press ''Update'' button.
  
-<color blue>If your IP is changing</color> all the time, you can still configure it, but it might be a bit tricker. Usually internet service providers will only change last one or last two numbers of your IP. If that is the case, simply add your whole block. Even if you will add a whole IP block, you will reduce the number of potential hackers to nearly zero. Users that are not listed in the "Allowed IPs" module and/or htaccess, will get: ''Your IP is not on the access list / Forbidden'' message.+**If your IP is changing** all the time, you can still configure it, but it might be a bit tricker. Usually internet service providers will only change last one or last two numbers of your IP. If that is the case, simply add your whole block. Even if you will add a whole IP block, you will reduce the number of potential hackers to nearly zero. Users that are not listed in the "Allowed IPs" module and/or htaccess, will get: ''Your IP is not on the access list / Forbidden'' message.
  
 ---- ----
  
- +===== Allowed IPs: =====
-==== Allowed IPs: ==== +
  
 It only protects TE3 files that should never be opened to the public (no function or meaning to open them to the public). It doesn't protect files such as ''signup.php'', because these files are usually opened to public. We understand there are many webmasters that would like to make their own list of protected files. If that is the case, you should use more flexible htaccess method instead (read the next chapter). It only protects TE3 files that should never be opened to the public (no function or meaning to open them to the public). It doesn't protect files such as ''signup.php'', because these files are usually opened to public. We understand there are many webmasters that would like to make their own list of protected files. If that is the case, you should use more flexible htaccess method instead (read the next chapter).
Line 35: Line 28:
 ---- ----
  
-==== .htaccess: ==== +===== .htaccess: ===== 
- + 
 IP protection with htaccess is more flexible than "Allowed IPs" module as it allows you to specify files you want to protect. It is supposed to be bulletproof as it is based on the server level. Different webmasters have different demands. Check the list of all the TE3's PHP files with descriptions. Based on that you should be able to decide which files you need IP protected and which ones will have to remain opened to the public. IP protection with htaccess is more flexible than "Allowed IPs" module as it allows you to specify files you want to protect. It is supposed to be bulletproof as it is based on the server level. Different webmasters have different demands. Check the list of all the TE3's PHP files with descriptions. Based on that you should be able to decide which files you need IP protected and which ones will have to remain opened to the public.
  
-<color grey>Here is an example of how htaccess protection should look like. You can use (copy paste) an example below and feel free to modify it. Add additional files if you don't need them opened to the public and want to protect them. As you can see, in this example protected files are: ''index.php'' and ''rlogin.php''. And let's imagine your server's IP is ''210.10.15.20'' and your home IP is always changing the last two numbers ( first two numbers are ''90.60.'' ). You can add it like this:</color> +++++ Example of htaccess protection | 
 +Here is an example of how htaccess protection should look like. You can use (copy paste) an example below and feel free to modify it. Add additional files if you don't need them opened to the public and want to protect them. As you can see, in this example protected files are: ''index.php'' and ''rlogin.php''. And let's imagine your server's IP is ''210.10.15.20'' and your home IP is always changing the last two numbers (first two numbers are ''90.60.'' ). You can add it like this:
  
 <code><files ~ "(index\.php|rlogin\.php)"> <code><files ~ "(index\.php|rlogin\.php)">
Line 47: Line 40:
 </files></code> </files></code>
  
 +++++
  
 ---- ----
  
-==== PHP files inside /te3/ directory ==== +===== PHP files inside /te3/ directory =====
  
 Here is a brief description of the PHP files inside /te3/ directory, so you can better understand what is their task and which of them should be <color blue>IP protected</color>. Here is a brief description of the PHP files inside /te3/ directory, so you can better understand what is their task and which of them should be <color blue>IP protected</color>.
te3/allowed_ips.txt · Last modified: 2015/07/13 18:13 by moderator
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki