All In One WP Security & Firewall - Version 1.9

Version Description

  • Added new WordPress PingBack Vulnerability Protection feature. This allows the user to prohibit access to the xmlrpc.php file in order to protect against certain vulnerabilities in the pingback functionality.
  • Added a configuration item in the brute force login prevention feature to allow ajax functionality to work properly when this feature is enabled.
  • Added a POT file for language translations.
  • Made the DB Prefix feature more robust by adding a check to ensure that plugin can write to the wp-config.php file. This will prevent user from losing access to their site in cases where the system changed the prefix but not the entry in the wp-config.php file.
  • Tightened the data validation for the cookie based brute force login feature to ensure that the user must enter a secret word which consists of alphanumeric characters.
  • Added edit links to the user account list in the "User Acounts" menu.
Download this release

Release Info

Developer mra13
Plugin Icon 128x128 All In One WP Security & Firewall
Version 1.9
Comparing to
See all releases

Code changes from version 1.8 to 1.9

admin/wp-security-database-menu.php CHANGED
@@ -77,27 +77,38 @@ class AIOWPSecurity_Database_Menu extends AIOWPSecurity_Admin_Menu
77
  $aio_wp_security->debug_logger->log_debug("Nonce check failed for DB prefix change operation!",4);
78
  die(__('Nonce check failed for DB prefix change operation!','aiowpsecurity'));
79
  }
80
- if( isset($_POST['aiowps_enable_random_prefix']))
81
- {//User has elected to generate a random DB prefix
82
- $string = AIOWPSecurity_Utility::generate_alpha_numeric_random_string('6');
83
- $new_db_prefix = $string . '_';
84
- $perform_db_change = true;
85
- }else
86
  {
87
- if (empty($_POST['aiowps_new_manual_db_prefix']))
88
- {
89
- $this->show_msg_error(__('Please enter a value for the DB prefix.', 'aiowpsecurity'));
90
- }
91
- else
 
 
 
 
 
92
  {
93
- //User has chosen their own DB prefix value
94
- $new_db_prefix = wp_strip_all_tags( trim( $_POST['aiowps_new_manual_db_prefix'] ) );
95
- $error = $wpdb->set_prefix( $new_db_prefix );
96
- if(is_wp_error($error))
97
  {
98
- wp_die( __('<strong>ERROR</strong>: The table prefix can only contain numbers, letters, and underscores.', 'aiowpsecurity') );
 
 
 
 
 
 
 
 
 
 
 
99
  }
100
- $perform_db_change = true;
101
  }
102
  }
103
  }
@@ -334,6 +345,9 @@ class AIOWPSecurity_Database_Menu extends AIOWPSecurity_Admin_Menu
334
  global $wpdb, $aio_wp_security;
335
  $old_prefix_length = strlen( $table_old_prefix );
336
 
 
 
 
337
  //Get the table resource
338
  $result = mysql_list_tables(DB_NAME);
339
 
@@ -342,12 +356,11 @@ class AIOWPSecurity_Database_Menu extends AIOWPSecurity_Admin_Menu
342
  $table_count = 0;
343
 
344
  //TODO - after reading up on internationalization mixed with html code I found that the WP experts say to do it as below. We will need to clean up other areas where we haven't used the following convention
345
- $info_msg_string = '<p class="aio_info_with_icon">'.sprintf( __('Starting DB prefix change.....', 'aiowpsecurity')).'</p>';
 
346
  $info_msg_string .= '<p class="aio_info_with_icon">'.sprintf( __('Your WordPress system has a total of %s tables and your new DB prefix will be: %s', 'aiowpsecurity'), '<strong>'.$num_rows.'</strong>', '<strong>'.$table_new_prefix.'</strong>').'</p>';
347
  echo ($info_msg_string);
348
 
349
- //Config file path
350
- $config_file = ABSPATH.'wp-config.php';
351
  //Do a back of the config file
352
  if(!AIOWPSecurity_Utility_File::backup_a_file($config_file))
353
  {
77
  $aio_wp_security->debug_logger->log_debug("Nonce check failed for DB prefix change operation!",4);
78
  die(__('Nonce check failed for DB prefix change operation!','aiowpsecurity'));
79
  }
80
+
81
+ //Let's first check if user's system allows writing to wp-config.php file. If plugin cannot write to wp-config we will not do the prefix change.
82
+ $config_file = ABSPATH.'wp-config.php';
83
+ $file_write = AIOWPSecurity_Utility_File::is_file_writable($config_file);
84
+ if ($file_write == false)
 
85
  {
86
+ $this->show_msg_error(__('The plugin has detected that it cannot write to the wp-config.php file. This feature can only be used if the plugin can successfully write to the wp-config.php file.', 'aiowpsecurity'));
87
+ }
88
+ else
89
+ {
90
+ if( isset($_POST['aiowps_enable_random_prefix']))
91
+ {//User has elected to generate a random DB prefix
92
+ $string = AIOWPSecurity_Utility::generate_alpha_numeric_random_string('6');
93
+ $new_db_prefix = $string . '_';
94
+ $perform_db_change = true;
95
+ }else
96
  {
97
+ if (empty($_POST['aiowps_new_manual_db_prefix']))
 
 
 
98
  {
99
+ $this->show_msg_error(__('Please enter a value for the DB prefix.', 'aiowpsecurity'));
100
+ }
101
+ else
102
+ {
103
+ //User has chosen their own DB prefix value
104
+ $new_db_prefix = wp_strip_all_tags( trim( $_POST['aiowps_new_manual_db_prefix'] ) );
105
+ $error = $wpdb->set_prefix( $new_db_prefix );
106
+ if(is_wp_error($error))
107
+ {
108
+ wp_die( __('<strong>ERROR</strong>: The table prefix can only contain numbers, letters, and underscores.', 'aiowpsecurity') );
109
+ }
110
+ $perform_db_change = true;
111
  }
 
112
  }
113
  }
114
  }
345
  global $wpdb, $aio_wp_security;
346
  $old_prefix_length = strlen( $table_old_prefix );
347
 
348
+ //Config file path
349
+ $config_file = ABSPATH.'wp-config.php';
350
+
351
  //Get the table resource
352
  $result = mysql_list_tables(DB_NAME);
353
 
356
  $table_count = 0;
357
 
358
  //TODO - after reading up on internationalization mixed with html code I found that the WP experts say to do it as below. We will need to clean up other areas where we haven't used the following convention
359
+ $info_msg_string = '<p class="aio_info_with_icon">'.__('Starting DB prefix change operations.....', 'aiowpsecurity').'</p>';
360
+
361
  $info_msg_string .= '<p class="aio_info_with_icon">'.sprintf( __('Your WordPress system has a total of %s tables and your new DB prefix will be: %s', 'aiowpsecurity'), '<strong>'.$num_rows.'</strong>', '<strong>'.$table_new_prefix.'</strong>').'</p>';
362
  echo ($info_msg_string);
363
 
 
 
364
  //Do a back of the config file
365
  if(!AIOWPSecurity_Utility_File::backup_a_file($config_file))
366
  {
admin/wp-security-firewall-menu.php CHANGED
@@ -89,6 +89,15 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
89
  $aio_wp_security->configs->set_value('aiowps_enable_basic_firewall','');
90
  }
91
 
 
 
 
 
 
 
 
 
 
92
  //Commit the config settings
93
  $aio_wp_security->configs->save_config();
94
 
@@ -100,7 +109,7 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
100
 
101
  if ($res)
102
  {
103
- $this->show_msg_updated(__('You have successfully saved the Basic Firewall Protection configuration', 'aiowpsecurity'));
104
  }
105
  else if($res == -1)
106
  {
@@ -110,11 +119,14 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
110
 
111
  ?>
112
  <h2><?php _e('Firewall Settings', 'aiowpsecurity')?></h2>
 
 
 
113
  <div class="aio_blue_box">
114
  <?php
115
  $backup_tab_link = '<a href="admin.php?page='.AIOWPSEC_SETTINGS_MENU_SLUG.'&tab=tab2" target="_blank">backup</a>';
116
  $info_msg = sprintf( __('This should not have any impact on your site\'s general functionality but if you wish you can take a %s of your .htaccess file before proceeding.', 'aiowpsecurity'), $backup_tab_link);
117
- echo '<p>'.__('This feature allows you to activate some basic firewall security protection rules for your site.', 'aiowpsecurity').
118
  '<br />'.__('The firewall functionality is achieved via the insertion of special code into your currently active .htaccess file.', 'aiowpsecurity').
119
  '<br />'.$info_msg.'</p>';
120
  ?>
@@ -127,8 +139,6 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
127
  //Display security info badge
128
  $aiowps_feature_mgr->output_feature_details_badge("firewall-basic-rules");
129
  ?>
130
- <form action="" method="POST">
131
- <?php wp_nonce_field('aiowpsec-enable-basic-firewall-nonce'); ?>
132
  <table class="form-table">
133
  <tr valign="top">
134
  <th scope="row"><?php _e('Enable Basic Firewall Protection', 'aiowpsecurity')?>:</th>
@@ -150,9 +160,39 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
150
  </td>
151
  </tr>
152
  </table>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
153
  <input type="submit" name="aiowps_apply_basic_firewall_settings" value="<?php _e('Save Basic Firewall Settings', 'aiowpsecurity')?>" class="button-primary" />
154
  </form>
155
- </div></div>
156
  <?php
157
  }
158
 
@@ -496,6 +536,7 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
496
  {
497
  global $aio_wp_security;
498
  global $aiowps_feature_mgr;
 
499
 
500
  //Save settings for brute force cookie method
501
  if(isset($_POST['aiowps_apply_cookie_based_bruteforce_firewall']))
@@ -512,6 +553,9 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
512
  $brute_force_feature_secret_word = sanitize_text_field($_POST['aiowps_brute_force_secret_word']);
513
  if(empty($brute_force_feature_secret_word)){
514
  $brute_force_feature_secret_word = "aiowps_secret";
 
 
 
515
  }
516
 
517
  if(filter_var($_POST['aiowps_cookie_based_brute_force_redirect_url'], FILTER_VALIDATE_URL))
@@ -522,22 +566,18 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
522
  {
523
  $aio_wp_security->configs->set_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
524
  }
525
-
526
- $aio_wp_security->configs->set_value('aiowps_brute_force_secret_word',$brute_force_feature_secret_word);
527
  $aio_wp_security->configs->set_value('aiowps_enable_brute_force_attack_prevention','1');
528
-
529
- if(isset($_POST['aiowps_brute_force_attack_prevention_pw_protected_exception'])){
530
- $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','1');
531
- }else {
532
- $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');
 
 
 
 
533
  }
534
-
535
- //TODO - pretty up the following messages
536
- $msg = '<p>'.__('You have successfully enabled the cookie based brute force prevention feature', 'aiowpsecurity').'</p>';
537
- $msg .= '<p>'.__('From now on you will need to log into your WP Admin using the following URL:', 'aiowpsecurity').'</p>';
538
- $msg .= '<p><strong>'.AIOWPSEC_WP_URL.'/?'.$brute_force_feature_secret_word.'=1</strong></p>';
539
- $msg .= '<p>'.__('It is important that you save this URL value somewhere in case you forget it, OR,', 'aiowpsecurity').'</p>';
540
- $msg .= '<p>'.sprintf( __('simply remember to add a "?%s=1" to your current site URL address.', 'aiowpsecurity'), $brute_force_feature_secret_word).'</p>';
541
  }
542
  else
543
  {
@@ -545,21 +585,45 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
545
  $msg = __('You have successfully saved cookie based brute force prevention feature settings.', 'aiowpsecurity');
546
  }
547
 
548
- $aio_wp_security->configs->save_config();//save the value
549
-
550
- //Recalculate points after the feature status/options have been altered
551
- $aiowps_feature_mgr->check_feature_status_and_recalculate_points();
552
-
553
- $res = AIOWPSecurity_Utility_Htaccess::write_to_htaccess();
554
- if ($res){
555
- echo '<div id="message" class="updated fade"><p>';
556
- echo $msg;
557
- echo '</p></div>';
558
  }
559
- else if($res == -1){
560
- $this->show_msg_error(__('Could not write to the .htaccess file. Please check the file permissions.', 'aiowpsecurity'));
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
561
  }
562
-
563
  }
564
 
565
  ?>
@@ -603,7 +667,7 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
603
  echo '<br />';
604
  _e('1) Enable the checkbox.', 'aiowpsecurity');
605
  echo '<br />';
606
- _e('2) Enter a secret word which will be difficult to guess. This secret word will be useful whenever you need to know the special URL which you will use to access the login page (see point below).', 'aiowpsecurity');
607
  echo '<br />';
608
  _e('3) You will then be provided with a special login URL. You will need to use this URL to login to your WordPress site instead of the usual login URL. NOTE: The system will deposit a special cookie in your browser which will allow you access to the WordPress administration login page.', 'aiowpsecurity');
609
  echo '<br />';
@@ -616,7 +680,7 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
616
  <tr valign="top">
617
  <th scope="row"><?php _e('Secret Word', 'aiowpsecurity')?>:</th>
618
  <td><input size="40" name="aiowps_brute_force_secret_word" value="<?php echo $aio_wp_security->configs->get_value('aiowps_brute_force_secret_word'); ?>" />
619
- <span class="description"><?php _e('Choose a secret word which you can use to access your special URL. Your are highly encouraged to choose a word which will be difficult to guess.', 'aiowpsecurity'); ?></span>
620
  </td>
621
  </tr>
622
  <tr valign="top">
@@ -666,6 +730,23 @@ class AIOWPSecurity_Firewall_Menu extends AIOWPSecurity_Admin_Menu
666
  </div>
667
  </td>
668
  </tr>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
669
  </table>
670
  <?php
671
  $cookie_test_value = $aio_wp_security->configs->get_value('aiowps_cookie_test_success');
89
  $aio_wp_security->configs->set_value('aiowps_enable_basic_firewall','');
90
  }
91
 
92
+ if(isset($_POST['aiowps_enable_pingback_firewall']))
93
+ {
94
+ $aio_wp_security->configs->set_value('aiowps_enable_pingback_firewall','1');
95
+ }
96
+ else
97
+ {
98
+ $aio_wp_security->configs->set_value('aiowps_enable_pingback_firewall','');
99
+ }
100
+
101
  //Commit the config settings
102
  $aio_wp_security->configs->save_config();
103
 
109
 
110
  if ($res)
111
  {
112
+ $this->show_msg_updated(__('Settings were successfully saved', 'aiowpsecurity'));
113
  }
114
  else if($res == -1)
115
  {
119
 
120
  ?>
121
  <h2><?php _e('Firewall Settings', 'aiowpsecurity')?></h2>
122
+ <form action="" method="POST">
123
+ <?php wp_nonce_field('aiowpsec-enable-basic-firewall-nonce'); ?>
124
+
125
  <div class="aio_blue_box">
126
  <?php
127
  $backup_tab_link = '<a href="admin.php?page='.AIOWPSEC_SETTINGS_MENU_SLUG.'&tab=tab2" target="_blank">backup</a>';
128
  $info_msg = sprintf( __('This should not have any impact on your site\'s general functionality but if you wish you can take a %s of your .htaccess file before proceeding.', 'aiowpsecurity'), $backup_tab_link);
129
+ echo '<p>'.__('The features in this tab allow you to activate some basic firewall security protection rules for your site.', 'aiowpsecurity').
130
  '<br />'.__('The firewall functionality is achieved via the insertion of special code into your currently active .htaccess file.', 'aiowpsecurity').
131
  '<br />'.$info_msg.'</p>';
132
  ?>
139
  //Display security info badge
140
  $aiowps_feature_mgr->output_feature_details_badge("firewall-basic-rules");
141
  ?>
 
 
142
  <table class="form-table">
143
  <tr valign="top">
144
  <th scope="row"><?php _e('Enable Basic Firewall Protection', 'aiowpsecurity')?>:</th>
160
  </td>
161
  </tr>
162
  </table>
163
+ </div></div>
164
+
165
+ <div class="postbox">
166
+ <h3><label for="title"><?php _e('WordPress Pingback Vulnerability Protection', 'aiowpsecurity'); ?></label></h3>
167
+ <div class="inside">
168
+ <?php
169
+ //Display security info badge
170
+ $aiowps_feature_mgr->output_feature_details_badge("firewall-pingback-rules");
171
+ ?>
172
+ <table class="form-table">
173
+ <tr valign="top">
174
+ <th scope="row"><?php _e('Enable Pingback Protection', 'aiowpsecurity')?>:</th>
175
+ <td>
176
+ <input name="aiowps_enable_pingback_firewall" type="checkbox"<?php if($aio_wp_security->configs->get_value('aiowps_enable_pingback_firewall')=='1') echo ' checked="checked"'; ?> value="1"/>
177
+ <span class="description"><?php _e('Check this if you are not using the WP XML-RPC functionality and you want to enable protection against WordPress pingback vulnerabilities.', 'aiowpsecurity'); ?></span>
178
+ <span class="aiowps_more_info_anchor"><span class="aiowps_more_info_toggle_char">+</span><span class="aiowps_more_info_toggle_text"><?php _e('More Info', 'aiowpsecurity'); ?></span></span>
179
+ <div class="aiowps_more_info_body">
180
+ <?php
181
+ echo '<p class="description">'.__('This setting will add a directive in your .htaccess to disable access to the WordPress xmlrpc.php file which is responsible for the XML-RPC functionality such as pingbacks in WordPress.', 'aiowpsecurity').'</p>';
182
+ echo '<p class="description">'.__('Hackers can exploit various pingback vulnerabilities in the WordPress XML-RPC API in a number of ways such as:', 'aiowpsecurity').'</p>';
183
+ echo '<p class="description">'.__('1) Denial of Service (DoS) attacks', 'aiowpsecurity').'</p>';
184
+ echo '<p class="description">'.__('2) Hacking internal routers.', 'aiowpsecurity').'</p>';
185
+ echo '<p class="description">'.__('3) Scanning ports in internal networks to get info from various hosts.', 'aiowpsecurity').'</p>';
186
+ echo '<p class="description">'.__('Apart from the security protection benefit, this feature may also help reduce load on your server, particularly if your site currently has a lot of unwanted traffic hitting the XML-RPC API on your installation.', 'aiowpsecurity').'</p>';
187
+ echo '<p class="description">'.__('NOTE: You should only enable this feature if you are not currently using the XML-RPC functionality on your WordPress installation.', 'aiowpsecurity').'</p>';
188
+ ?>
189
+ </div>
190
+ </td>
191
+ </tr>
192
+ </table>
193
+ </div></div>
194
  <input type="submit" name="aiowps_apply_basic_firewall_settings" value="<?php _e('Save Basic Firewall Settings', 'aiowpsecurity')?>" class="button-primary" />
195
  </form>
 
196
  <?php
197
  }
198
 
536
  {
537
  global $aio_wp_security;
538
  global $aiowps_feature_mgr;
539
+ $error = false;
540
 
541
  //Save settings for brute force cookie method
542
  if(isset($_POST['aiowps_apply_cookie_based_bruteforce_firewall']))
553
  $brute_force_feature_secret_word = sanitize_text_field($_POST['aiowps_brute_force_secret_word']);
554
  if(empty($brute_force_feature_secret_word)){
555
  $brute_force_feature_secret_word = "aiowps_secret";
556
+ }else if(!ctype_alnum($brute_force_feature_secret_word)){
557
+ $msg = '<p>'.__('Settings have not been saved - your secret word must consist only of alphanumeric characters, ie, letters and/or numbers only!', 'aiowpsecurity').'</p>';
558
+ $error = true;
559
  }
560
 
561
  if(filter_var($_POST['aiowps_cookie_based_brute_force_redirect_url'], FILTER_VALIDATE_URL))
566
  {
567
  $aio_wp_security->configs->set_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
568
  }
569
+
 
570
  $aio_wp_security->configs->set_value('aiowps_enable_brute_force_attack_prevention','1');
571
+
572
+ if (!$error)
573
+ {
574
+ $aio_wp_security->configs->set_value('aiowps_brute_force_secret_word',$brute_force_feature_secret_word);
575
+ $msg = '<p>'.__('You have successfully enabled the cookie based brute force prevention feature', 'aiowpsecurity').'</p>';
576
+ $msg .= '<p>'.__('From now on you will need to log into your WP Admin using the following URL:', 'aiowpsecurity').'</p>';
577
+ $msg .= '<p><strong>'.AIOWPSEC_WP_URL.'/?'.$brute_force_feature_secret_word.'=1</strong></p>';
578
+ $msg .= '<p>'.__('It is important that you save this URL value somewhere in case you forget it, OR,', 'aiowpsecurity').'</p>';
579
+ $msg .= '<p>'.sprintf( __('simply remember to add a "?%s=1" to your current site URL address.', 'aiowpsecurity'), $brute_force_feature_secret_word).'</p>';
580
  }
 
 
 
 
 
 
 
581
  }
582
  else
583
  {
585
  $msg = __('You have successfully saved cookie based brute force prevention feature settings.', 'aiowpsecurity');
586
  }
587
 
588
+ if(isset($_POST['aiowps_brute_force_attack_prevention_pw_protected_exception']))
589
+ {
590
+ $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','1');
 
 
 
 
 
 
 
591
  }
592
+ else
593
+ {
594
+ $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');
595
+ }
596
+
597
+ if(isset($_POST['aiowps_brute_force_attack_prevention_ajax_exception']))
598
+ {
599
+ $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_ajax_exception','1');
600
+ }
601
+ else
602
+ {
603
+ $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_ajax_exception','');
604
+ }
605
+
606
+ if (!$error)
607
+ {
608
+ $aio_wp_security->configs->save_config();//save the value
609
+
610
+ //Recalculate points after the feature status/options have been altered
611
+ $aiowps_feature_mgr->check_feature_status_and_recalculate_points();
612
+
613
+ $res = AIOWPSecurity_Utility_Htaccess::write_to_htaccess();
614
+ if ($res){
615
+ echo '<div id="message" class="updated fade"><p>';
616
+ echo $msg;
617
+ echo '</p></div>';
618
+ }
619
+ else if($res == -1){
620
+ $this->show_msg_error(__('Could not write to the .htaccess file. Please check the file permissions.', 'aiowpsecurity'));
621
+ }
622
+ }
623
+ else
624
+ {
625
+ $this->show_msg_error($msg);
626
  }
 
627
  }
628
 
629
  ?>
667
  echo '<br />';
668
  _e('1) Enable the checkbox.', 'aiowpsecurity');
669
  echo '<br />';
670
+ _e('2) Enter a secret word consisting of alphanumeric characters which will be difficult to guess. This secret word will be useful whenever you need to know the special URL which you will use to access the login page (see point below).', 'aiowpsecurity');
671
  echo '<br />';
672
  _e('3) You will then be provided with a special login URL. You will need to use this URL to login to your WordPress site instead of the usual login URL. NOTE: The system will deposit a special cookie in your browser which will allow you access to the WordPress administration login page.', 'aiowpsecurity');
673
  echo '<br />';
680
  <tr valign="top">
681
  <th scope="row"><?php _e('Secret Word', 'aiowpsecurity')?>:</th>
682
  <td><input size="40" name="aiowps_brute_force_secret_word" value="<?php echo $aio_wp_security->configs->get_value('aiowps_brute_force_secret_word'); ?>" />
683
+ <span class="description"><?php _e('Choose a secret word consisting of alphanumeric characters which you can use to access your special URL. Your are highly encouraged to choose a word which will be difficult to guess.', 'aiowpsecurity'); ?></span>
684
  </td>
685
  </tr>
686
  <tr valign="top">
730
  </div>
731
  </td>
732
  </tr>
733
+ <tr valign="top">
734
+ <th scope="row"><?php _e('My Site Has a Theme or Plugins Which Use AJAX', 'aiowpsecurity')?>:</th>
735
+ <td>
736
+ <input name="aiowps_brute_force_attack_prevention_ajax_exception" type="checkbox"<?php if($aio_wp_security->configs->get_value('aiowps_brute_force_attack_prevention_ajax_exception')=='1') echo ' checked="checked"'; ?> value="1"/>
737
+ <span class="description"><?php _e('Check this if your site uses AJAX functionality.', 'aiowpsecurity'); ?></span>
738
+ <span class="aiowps_more_info_anchor"><span class="aiowps_more_info_toggle_char">+</span><span class="aiowps_more_info_toggle_text"><?php _e('More Info', 'aiowpsecurity'); ?></span></span>
739
+ <div class="aiowps_more_info_body">
740
+ <p class="description">
741
+ <?php
742
+ _e('In the cases where your WordPress installation has a theme or plugins which use AJAX, a few extra lines of directives and exceptions need to be added to your .htacces file to prevent AJAX requests from being automatically blocked by the brute force prevention feature.', 'aiowpsecurity');
743
+ echo '<br />';
744
+ _e('By enabling this checkbox the plugin will add the necessary rules and exceptions to your .htacces file so that AJAX operations will work as expected.', 'aiowpsecurity');
745
+ ?>
746
+ </p>
747
+ </div>
748
+ </td>
749
+ </tr>
750
  </table>
751
  <?php
752
  $cookie_test_value = $aio_wp_security->configs->get_value('aiowps_cookie_test_success');
admin/wp-security-user-accounts-menu.php CHANGED
@@ -175,7 +175,7 @@ class AIOWPSecurity_User_Accounts_Menu extends AIOWPSecurity_Admin_Menu
175
  foreach ($login_nick_name_accounts as $usr){
176
  echo '<tr valign="top">';
177
  // echo '<th scope="row"><label for="UserID'.$usr['ID'].'"> Login Name: </label></th>';
178
- echo '<td><a href="'.$edit_user_page.$usr['ID'].'" target="_blank">'.$usr['user_login'].'</a>';
179
  echo '</tr>';
180
  }
181
  ?>
@@ -324,6 +324,8 @@ class AIOWPSecurity_User_Accounts_Menu extends AIOWPSecurity_Admin_Menu
324
  }else {
325
  $account_output .= '<td>'.$entry->user_login.'</td>';
326
  }
 
 
327
  $account_output .= '</tr>';
328
  }
329
  $account_output .= '</table>';
175
  foreach ($login_nick_name_accounts as $usr){
176
  echo '<tr valign="top">';
177
  // echo '<th scope="row"><label for="UserID'.$usr['ID'].'"> Login Name: </label></th>';
178
+ echo '<td><a href="'.$edit_user_page.$usr['ID'].'" target="_blank">'.$usr['user_login'].'</a></td>';
179
  echo '</tr>';
180
  }
181
  ?>
324
  }else {
325
  $account_output .= '<td>'.$entry->user_login.'</td>';
326
  }
327
+ $user_acct_edit_link = get_option('siteurl').'/wp-admin/user-edit.php?user_id=';
328
+ $account_output .= '<td><a href="'.$user_acct_edit_link.$entry->ID.'" target="_blank">Edit User</a></td>';
329
  $account_output .= '</tr>';
330
  }
331
  $account_output .= '</table>';
classes/grade-system/wp-security-feature-item-manager.php CHANGED
@@ -61,6 +61,7 @@ class AIOWPSecurity_Feature_Item_Manager
61
  //Firewall Menu Features
62
  //Basic firewall
63
  $this->feature_items[] = new AIOWPSecurity_Feature_Item("firewall-basic-rules", "Enable Basic Firewall", $this->feature_point_3, $this->sec_level_basic);
 
64
 
65
  //Additional and Advanced firewall
66
  $this->feature_items[] = new AIOWPSecurity_Feature_Item("firewall-enable-brute-force-attack-prevention", "Enable Brute Force Attack Prevention", $this->feature_point_4, $this->sec_level_inter);
@@ -171,6 +172,13 @@ class AIOWPSecurity_Feature_Item_Manager
171
  {
172
  $this->check_enable_basic_firewall_feature($item);
173
  }
 
 
 
 
 
 
 
174
  if($item->feature_id == "firewall-enable-brute-force-attack-prevention")
175
  {
176
  $this->check_enable_bfap_firewall_feature($item);
@@ -381,6 +389,19 @@ class AIOWPSecurity_Feature_Item_Manager
381
  }
382
  }
383
 
 
 
 
 
 
 
 
 
 
 
 
 
 
384
  function check_disable_trace_track_firewall_feature($item)
385
  {
386
  global $aio_wp_security;
61
  //Firewall Menu Features
62
  //Basic firewall
63
  $this->feature_items[] = new AIOWPSecurity_Feature_Item("firewall-basic-rules", "Enable Basic Firewall", $this->feature_point_3, $this->sec_level_basic);
64
+ $this->feature_items[] = new AIOWPSecurity_Feature_Item("firewall-pingback-rules", "Enable Pingback Vulnerability Protection", $this->feature_point_3, $this->sec_level_basic);
65
 
66
  //Additional and Advanced firewall
67
  $this->feature_items[] = new AIOWPSecurity_Feature_Item("firewall-enable-brute-force-attack-prevention", "Enable Brute Force Attack Prevention", $this->feature_point_4, $this->sec_level_inter);
172
  {
173
  $this->check_enable_basic_firewall_feature($item);
174
  }
175
+
176
+ if($item->feature_id == "firewall-pingback-rules")
177
+ {
178
+ $this->check_enable_pingback_firewall_feature($item);
179
+ }
180
+
181
+
182
  if($item->feature_id == "firewall-enable-brute-force-attack-prevention")
183
  {
184
  $this->check_enable_bfap_firewall_feature($item);
389
  }
390
  }
391
 
392
+ function check_enable_pingback_firewall_feature($item)
393
+ {
394
+ global $aio_wp_security;
395
+ if ($aio_wp_security->configs->get_value('aiowps_enable_pingback_firewall') == '1') {
396
+ $item->set_feature_status($this->feature_active);
397
+ }
398
+ else
399
+ {
400
+ $item->set_feature_status($this->feature_inactive);
401
+ }
402
+ }
403
+
404
+
405
  function check_disable_trace_track_firewall_feature($item)
406
  {
407
  global $aio_wp_security;
classes/wp-security-configure-settings.php CHANGED
@@ -49,6 +49,7 @@ class AIOWPSecurity_Configure_Settings
49
 
50
  //Firewall features
51
  $aio_wp_security->configs->set_value('aiowps_enable_basic_firewall','');//Checkbox
 
52
  $aio_wp_security->configs->set_value('aiowps_disable_index_views','');//Checkbox
53
  $aio_wp_security->configs->set_value('aiowps_disable_trace_and_track','');//Checkbox
54
  $aio_wp_security->configs->set_value('aiowps_forbid_proxy_comments','');//Checkbox
@@ -60,6 +61,7 @@ class AIOWPSecurity_Configure_Settings
60
  $aio_wp_security->configs->set_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
61
  $aio_wp_security->configs->set_value('aiowps_enable_brute_force_attack_prevention','');//Checkbox
62
  $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');//Checkbox
 
63
 
64
  //Maintenance menu - Visitor lockout feature
65
  $aio_wp_security->configs->set_value('aiowps_site_lockout','');//Checkbox
@@ -114,6 +116,7 @@ class AIOWPSecurity_Configure_Settings
114
 
115
  //Firewall features
116
  $aio_wp_security->configs->add_value('aiowps_enable_basic_firewall','');//Checkbox
 
117
  $aio_wp_security->configs->add_value('aiowps_disable_index_views','');//Checkbox
118
  $aio_wp_security->configs->add_value('aiowps_disable_trace_and_track','');//Checkbox
119
  $aio_wp_security->configs->add_value('aiowps_forbid_proxy_comments','');//Checkbox
@@ -124,6 +127,8 @@ class AIOWPSecurity_Configure_Settings
124
  $aio_wp_security->configs->add_value('aiowps_brute_force_secret_word','');
125
  $aio_wp_security->configs->add_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
126
  $aio_wp_security->configs->add_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');//Checkbox
 
 
127
 
128
  //Maintenance menu - Visitor lockout feature
129
  $aio_wp_security->configs->add_value('aiowps_site_lockout','');//Checkbox
49
 
50
  //Firewall features
51
  $aio_wp_security->configs->set_value('aiowps_enable_basic_firewall','');//Checkbox
52
+ $aio_wp_security->configs->set_value('aiowps_enable_pingback_firewall','');//Checkbox
53
  $aio_wp_security->configs->set_value('aiowps_disable_index_views','');//Checkbox
54
  $aio_wp_security->configs->set_value('aiowps_disable_trace_and_track','');//Checkbox
55
  $aio_wp_security->configs->set_value('aiowps_forbid_proxy_comments','');//Checkbox
61
  $aio_wp_security->configs->set_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
62
  $aio_wp_security->configs->set_value('aiowps_enable_brute_force_attack_prevention','');//Checkbox
63
  $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');//Checkbox
64
+ $aio_wp_security->configs->set_value('aiowps_brute_force_attack_prevention_ajax_exception','');//Checkbox
65
 
66
  //Maintenance menu - Visitor lockout feature
67
  $aio_wp_security->configs->set_value('aiowps_site_lockout','');//Checkbox
116
 
117
  //Firewall features
118
  $aio_wp_security->configs->add_value('aiowps_enable_basic_firewall','');//Checkbox
119
+ $aio_wp_security->configs->add_value('aiowps_enable_pingback_firewall','');//Checkbox
120
  $aio_wp_security->configs->add_value('aiowps_disable_index_views','');//Checkbox
121
  $aio_wp_security->configs->add_value('aiowps_disable_trace_and_track','');//Checkbox
122
  $aio_wp_security->configs->add_value('aiowps_forbid_proxy_comments','');//Checkbox
127
  $aio_wp_security->configs->add_value('aiowps_brute_force_secret_word','');
128
  $aio_wp_security->configs->add_value('aiowps_cookie_based_brute_force_redirect_url','http://127.0.0.1');
129
  $aio_wp_security->configs->add_value('aiowps_brute_force_attack_prevention_pw_protected_exception','');//Checkbox
130
+ $aio_wp_security->configs->add_value('aiowps_brute_force_attack_prevention_ajax_exception','');//Checkbox
131
+
132
 
133
  //Maintenance menu - Visitor lockout feature
134
  $aio_wp_security->configs->add_value('aiowps_site_lockout','');//Checkbox
classes/wp-security-utility-file.php CHANGED
@@ -102,6 +102,23 @@ class AIOWPSecurity_Utility_File
102
  return $perms;
103
  }
104
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
105
  /*
106
  * This function will compare the current permission value for a file or dir with the recommended value.
107
  * It will compare the individual "execute", "write" and "read" bits for the "public", "group" and "owner" permissions.
102
  return $perms;
103
  }
104
 
105
+ /*
106
+ * Checks if a write operation is possible for the file in question
107
+ */
108
+ static function is_file_writable($filepath)
109
+ {
110
+ $test_string = ""; //We will attempt to append an empty string at the end of the file for the test
111
+ $write_result = @file_put_contents($filepath, $test_string, FILE_APPEND | LOCK_EX);
112
+ if ($write_result === false)
113
+ {
114
+ return false;
115
+ }
116
+ else
117
+ {
118
+ return true;
119
+ }
120
+ }
121
+
122
  /*
123
  * This function will compare the current permission value for a file or dir with the recommended value.
124
  * It will compare the individual "execute", "write" and "read" bits for the "public", "group" and "owner" permissions.
classes/wp-security-utility-htaccess.php CHANGED
@@ -13,6 +13,9 @@ class AIOWPSecurity_Utility_Htaccess
13
  public static $basic_htaccess_rules_marker_start = '#AIOWPS_BASIC_HTACCESS_RULES_START';
14
  public static $basic_htaccess_rules_marker_end = '#AIOWPS_BASIC_HTACCESS_RULES_END';
15
 
 
 
 
16
  public static $user_agent_blacklist_marker_start = '#AIOWPS_USER_AGENT_BLACKLIST_START';
17
  public static $user_agent_blacklist_marker_end = '#AIOWPS_USER_AGENT_BLACKLIST_END';
18
 
@@ -195,6 +198,7 @@ class AIOWPSecurity_Utility_Htaccess
195
  $rules = "";
196
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_block_wp_file_access();
197
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_basic_htaccess();
 
198
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_disable_index_views();
199
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_blacklist();
200
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_disable_trace_and_track();
@@ -409,6 +413,24 @@ class AIOWPSecurity_Utility_Htaccess
409
  return $rules;
410
  }
411
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
412
  /*
413
  * This function will write some drectives to block all people who do not have a cookie
414
  * when trying to access the WP login page
@@ -424,6 +446,10 @@ class AIOWPSecurity_Utility_Htaccess
424
  $rules .= AIOWPSecurity_Utility_Htaccess::$enable_brute_force_attack_prevention_marker_start . PHP_EOL; //Add feature marker start
425
  $rules .= 'RewriteEngine On' . PHP_EOL;
426
  $rules .= 'RewriteCond %{REQUEST_URI} (wp-admin|wp-login)'. PHP_EOL;// If URI contains wp-admin or wp-login
 
 
 
 
427
  if($aio_wp_security->configs->get_value('aiowps_brute_force_attack_prevention_pw_protected_exception')=='1')
428
  {
429
  $rules .= 'RewriteCond %{QUERY_STRING} !(action\=postpass)' . PHP_EOL; // Possible workaround for people usign the password protected page/post feature
13
  public static $basic_htaccess_rules_marker_start = '#AIOWPS_BASIC_HTACCESS_RULES_START';
14
  public static $basic_htaccess_rules_marker_end = '#AIOWPS_BASIC_HTACCESS_RULES_END';
15
 
16
+ public static $pingback_htaccess_rules_marker_start = '#AIOWPS_PINGBACK_HTACCESS_RULES_START';
17
+ public static $pingback_htaccess_rules_marker_end = '#AIOWPS_PINGBACK_HTACCESS_RULES_END';
18
+
19
  public static $user_agent_blacklist_marker_start = '#AIOWPS_USER_AGENT_BLACKLIST_START';
20
  public static $user_agent_blacklist_marker_end = '#AIOWPS_USER_AGENT_BLACKLIST_END';
21
 
198
  $rules = "";
199
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_block_wp_file_access();
200
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_basic_htaccess();
201
+ $rules .= AIOWPSecurity_Utility_Htaccess::getrules_pingback_htaccess();
202
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_disable_index_views();
203
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_blacklist();
204
  $rules .= AIOWPSecurity_Utility_Htaccess::getrules_disable_trace_and_track();
413
  return $rules;
414
  }
415
 
416
+ static function getrules_pingback_htaccess()
417
+ {
418
+ global $aio_wp_security;
419
+
420
+ $rules = '';
421
+ if($aio_wp_security->configs->get_value('aiowps_enable_pingback_firewall')=='1')
422
+ {
423
+ $rules .= AIOWPSecurity_Utility_Htaccess::$pingback_htaccess_rules_marker_start . PHP_EOL; //Add feature marker start
424
+ //protect the htaccess file - this is done by default with apache config file but we are including it here for good measure
425
+ $rules .= '<IfModule mod_alias.c>' . PHP_EOL;
426
+ $rules .= 'RedirectMatch 403 /(.*)/xmlrpc\.php$' . PHP_EOL;
427
+ $rules .= '</IfModule>' . PHP_EOL;
428
+
429
+ $rules .= AIOWPSecurity_Utility_Htaccess::$pingback_htaccess_rules_marker_end . PHP_EOL; //Add feature marker end
430
+ }
431
+ return $rules;
432
+ }
433
+
434
  /*
435
  * This function will write some drectives to block all people who do not have a cookie
436
  * when trying to access the WP login page
446
  $rules .= AIOWPSecurity_Utility_Htaccess::$enable_brute_force_attack_prevention_marker_start . PHP_EOL; //Add feature marker start
447
  $rules .= 'RewriteEngine On' . PHP_EOL;
448
  $rules .= 'RewriteCond %{REQUEST_URI} (wp-admin|wp-login)'. PHP_EOL;// If URI contains wp-admin or wp-login
449
+ if($aio_wp_security->configs->get_value('aiowps_brute_force_attack_prevention_ajax_exception')=='1')
450
+ {
451
+ $rules .= 'RewriteCond %{REQUEST_URI} !(wp-admin/admin-ajax.php)' . PHP_EOL; // To allow ajax requests through
452
+ }
453
  if($aio_wp_security->configs->get_value('aiowps_brute_force_attack_prevention_pw_protected_exception')=='1')
454
  {
455
  $rules .= 'RewriteCond %{QUERY_STRING} !(action\=postpass)' . PHP_EOL; // Possible workaround for people usign the password protected page/post feature
languages/aiowpsecurity.pot ADDED
@@ -0,0 +1,2446 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ msgid ""
2
+ msgstr ""
3
+ "Project-Id-Version: All In One WP Security & Firewall\n"
4
+ "POT-Creation-Date: 2013-07-22 17:50+1000\n"
5
+ "PO-Revision-Date: 2013-MO-DA HO:MI+ZONE\n"
6
+ "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
7
+ "Language-Team: \n"
8
+ "MIME-Version: 1.0\n"
9
+ "Content-Type: text/plain; charset=UTF-8\n"
10
+ "Content-Transfer-Encoding: 8bit\n"
11
+ "X-Generator: Poedit 1.5.7\n"
12
+ "X-Poedit-KeywordsList: __;_e\n"
13
+ "X-Poedit-Basepath: .\n"
14
+ "X-Poedit-SearchPath-0: ..\n"
15
+
16
+ #: ../admin/wp-security-admin-init.php:140
17
+ msgid "WP Security"
18
+ msgstr ""
19
+
20
+ #: ../admin/wp-security-admin-init.php:141
21
+ msgid "Dashboard"
22
+ msgstr ""
23
+
24
+ #: ../admin/wp-security-admin-init.php:142
25
+ msgid "Settings"
26
+ msgstr ""
27
+
28
+ #: ../admin/wp-security-admin-init.php:143
29
+ msgid "User Accounts"
30
+ msgstr ""
31
+
32
+ #: ../admin/wp-security-admin-init.php:144
33
+ msgid "User Login"
34
+ msgstr ""
35
+
36
+ #: ../admin/wp-security-admin-init.php:145
37
+ msgid "Database Security"
38
+ msgstr ""
39
+
40
+ #: ../admin/wp-security-admin-init.php:146
41
+ msgid "Filesystem Security"
42
+ msgstr ""
43
+
44
+ #: ../admin/wp-security-admin-init.php:147
45
+ msgid "WHOIS Lookup"
46
+ msgstr ""
47
+
48
+ #: ../admin/wp-security-admin-init.php:148
49
+ msgid "Blacklist Manager"
50
+ msgstr ""
51
+
52
+ #: ../admin/wp-security-admin-init.php:149
53
+ msgid "Firewall"
54
+ msgstr ""
55
+
56
+ #: ../admin/wp-security-admin-init.php:150
57
+ msgid "Maintenance"
58
+ msgstr ""
59
+
60
+ #: ../admin/wp-security-admin-menu.php:43
61
+ msgid "Settings successfully updated."
62
+ msgstr ""
63
+
64
+ #: ../admin/wp-security-admin-menu.php:50
65
+ msgid "The selected record(s) deleted successfully!"
66
+ msgstr ""
67
+
68
+ #: ../admin/wp-security-blacklist-menu.php:77
69
+ msgid "Nonce check failed for save blacklist settings!"
70
+ msgstr ""
71
+
72
+ #: ../admin/wp-security-blacklist-menu.php:129
73
+ #: ../admin/wp-security-list-comment-spammer-ip.php:137
74
+ msgid ""
75
+ "The plugin was unable to write to the .htaccess file. Please edit file "
76
+ "manually."
77
+ msgstr ""
78
+
79
+ #: ../admin/wp-security-blacklist-menu.php:136
80
+ msgid "Ban IPs or User Agents"
81
+ msgstr ""
82
+
83
+ #: ../admin/wp-security-blacklist-menu.php:139
84
+ msgid ""
85
+ "The All In One WP Security Blacklist feature gives you the option of banning "
86
+ "certain host IP addresses or ranges and also user agents."
87
+ msgstr ""
88
+
89
+ #: ../admin/wp-security-blacklist-menu.php:140
90
+ msgid ""
91
+ "This feature will deny total site access for users which have IP addresses "
92
+ "or user agents matching those which you have configured in the settings "
93
+ "below."
94
+ msgstr ""
95
+
96
+ #: ../admin/wp-security-blacklist-menu.php:141
97
+ msgid ""
98
+ "The plugin achieves this by making appropriate modifications to your ."
99
+ "htaccess file."
100
+ msgstr ""
101
+
102
+ #: ../admin/wp-security-blacklist-menu.php:142
103
+ msgid ""
104
+ "By blocking people via the .htaccess file your are using the most secure "
105
+ "first line of defence which denies all access to blacklisted visitors as "
106
+ "soon as they hit your hosting server."
107
+ msgstr ""
108
+
109
+ #: ../admin/wp-security-blacklist-menu.php:148
110
+ msgid "IP Hosts and User Agent Blacklist Settings"
111
+ msgstr ""
112
+
113
+ #: ../admin/wp-security-blacklist-menu.php:159
114
+ msgid "Enable IP or User Agent Blacklisting"
115
+ msgstr ""
116
+
117
+ #: ../admin/wp-security-blacklist-menu.php:162
118
+ msgid ""
119
+ "Check this if you want to enable the banning (or blacklisting) of selected "
120
+ "IP addresses and/or user agents specified in the settings below"
121
+ msgstr ""
122
+
123
+ #: ../admin/wp-security-blacklist-menu.php:166
124
+ msgid "Enter IP Addresses:"
125
+ msgstr ""
126
+
127
+ #: ../admin/wp-security-blacklist-menu.php:170
128
+ msgid "Enter one or more IP addresses or IP ranges."
129
+ msgstr ""
130
+
131
+ #: ../admin/wp-security-blacklist-menu.php:171
132
+ #: ../admin/wp-security-blacklist-menu.php:191
133
+ #: ../admin/wp-security-blacklist-menu.php:276
134
+ #: ../admin/wp-security-firewall-menu.php:148
135
+ #: ../admin/wp-security-firewall-menu.php:178
136
+ #: ../admin/wp-security-firewall-menu.php:309
137
+ #: ../admin/wp-security-firewall-menu.php:339
138
+ #: ../admin/wp-security-firewall-menu.php:370
139
+ #: ../admin/wp-security-firewall-menu.php:398
140
+ #: ../admin/wp-security-firewall-menu.php:427
141
+ #: ../admin/wp-security-firewall-menu.php:515
142
+ #: ../admin/wp-security-firewall-menu.php:651
143
+ #: ../admin/wp-security-firewall-menu.php:685
144
+ #: ../admin/wp-security-firewall-menu.php:708
145
+ msgid "More Info"
146
+ msgstr ""
147
+
148
+ #: ../admin/wp-security-blacklist-menu.php:174
149
+ msgid "Each IP address must be on a new line."
150
+ msgstr ""
151
+
152
+ #: ../admin/wp-security-blacklist-menu.php:175
153
+ msgid ""
154
+ "To specify an IP range use a wildcard \"*\" character. Acceptable ways to "
155
+ "use wildcards is shown in the examples below:"
156
+ msgstr ""
157
+
158
+ #: ../admin/wp-security-blacklist-menu.php:176
159
+ msgid "Example 1: 195.47.89.*"
160
+ msgstr ""
161
+
162
+ #: ../admin/wp-security-blacklist-menu.php:177
163
+ msgid "Example 2: 195.47.*.*"
164
+ msgstr ""
165
+
166
+ #: ../admin/wp-security-blacklist-menu.php:178
167
+ msgid "Example 3: 195.*.*.*"
168
+ msgstr ""
169
+
170
+ #: ../admin/wp-security-blacklist-menu.php:185
171
+ msgid "Enter User Agents:"
172
+ msgstr ""
173
+
174
+ #: ../admin/wp-security-blacklist-menu.php:190
175
+ msgid "Enter one or more user agent strings."
176
+ msgstr ""
177
+
178
+ #: ../admin/wp-security-blacklist-menu.php:194
179
+ msgid "Each user agent string must be on a new line."
180
+ msgstr ""
181
+
182
+ #: ../admin/wp-security-blacklist-menu.php:195
183
+ msgid "Example 1 - A single user agent string to block:"
184
+ msgstr ""
185
+
186
+ #: ../admin/wp-security-blacklist-menu.php:197
187
+ msgid "Example 2 - A list of more than 1 user agent strings to block"
188
+ msgstr ""
189
+
190
+ #: ../admin/wp-security-blacklist-menu.php:205
191
+ #: ../admin/wp-security-database-menu.php:333
192
+ #: ../admin/wp-security-filesystem-menu.php:220
193
+ #: ../admin/wp-security-settings-menu.php:452
194
+ #: ../admin/wp-security-user-login-menu.php:211
195
+ #: ../admin/wp-security-user-login-menu.php:379
196
+ msgid "Save Settings"
197
+ msgstr ""
198
+
199
+ #: ../admin/wp-security-blacklist-menu.php:224
200
+ msgid "Nonce check failed for list SPAM comment IPs!"
201
+ msgstr ""
202
+
203
+ #: ../admin/wp-security-blacklist-menu.php:230
204
+ msgid ""
205
+ "You entered a non numeric value for the minimum SPAM comments per IP field. "
206
+ "It has been set to the default value."
207
+ msgstr ""
208
+
209
+ #: ../admin/wp-security-blacklist-menu.php:236
210
+ #: ../admin/wp-security-database-menu.php:248
211
+ #: ../admin/wp-security-user-login-menu.php:115
212
+ #: ../admin/wp-security-user-login-menu.php:332
213
+ msgid "Attention!"
214
+ msgstr ""
215
+
216
+ #: ../admin/wp-security-blacklist-menu.php:242
217
+ #, php-format
218
+ msgid ""
219
+ "Displaying results for IP addresses which have posted a minimum of %s SPAM "
220
+ "comments"
221
+ msgstr ""
222
+
223
+ #: ../admin/wp-security-blacklist-menu.php:258
224
+ msgid ""
225
+ "This tab displays a list of the IP addresses of the people or bots who have "
226
+ "left SPAM comments on your site."
227
+ msgstr ""
228
+
229
+ #: ../admin/wp-security-blacklist-menu.php:259
230
+ msgid ""
231
+ "This information can be handy for identifying the most persistent IP "
232
+ "addresses or ranges used by spammers."
233
+ msgstr ""
234
+
235
+ #: ../admin/wp-security-blacklist-menu.php:260
236
+ msgid ""
237
+ "By inspecting the IP address data coming from spammers you will be in a "
238
+ "better position to determine which addresses or address ranges you should "
239
+ "block by adding them to your blacklist."
240
+ msgstr ""
241
+
242
+ #: ../admin/wp-security-blacklist-menu.php:261
243
+ msgid ""
244
+ "To add one or more of the IP addresses displayed in the table below to your "
245
+ "blacklist, simply click the \"Block\" link for the individual row or select "
246
+ "more than one address \n"
247
+ " using the checkboxes and then choose the \"block"
248
+ "\" option from the Bulk Actions dropdown list and click the \"Apply\" button."
249
+ msgstr ""
250
+
251
+ #: ../admin/wp-security-blacklist-menu.php:267
252
+ msgid "List SPAMMER IP Addresses"
253
+ msgstr ""
254
+
255
+ #: ../admin/wp-security-blacklist-menu.php:273
256
+ msgid "Minimum number of SPAM comments per IP"
257
+ msgstr ""
258
+
259
+ #: ../admin/wp-security-blacklist-menu.php:275
260
+ msgid ""
261
+ "This field allows you to list only those IP addresses which have been used "
262
+ "to post X or more SPAM comments."
263
+ msgstr ""
264
+
265
+ #: ../admin/wp-security-blacklist-menu.php:279
266
+ msgid ""
267
+ "Example 1: Setting this value to \"0\" or \"1\" will list ALL IP addresses "
268
+ "which were used to submit SPAM comments."
269
+ msgstr ""
270
+
271
+ #: ../admin/wp-security-blacklist-menu.php:280
272
+ msgid ""
273
+ "Example 2: Setting this value to \"5\" will list only those IP addresses "
274
+ "which were used to submit 5 SPAM comments or more on your site."
275
+ msgstr ""
276
+
277
+ #: ../admin/wp-security-blacklist-menu.php:287
278
+ msgid "Find IP Addresses"
279
+ msgstr ""
280
+
281
+ #: ../admin/wp-security-blacklist-menu.php:291
282
+ msgid "SPAMMER IP Address Results"
283
+ msgstr ""
284
+
285
+ #: ../admin/wp-security-dashboard-menu.php:111
286
+ msgid "Total Achievable Points: "
287
+ msgstr ""
288
+
289
+ #: ../admin/wp-security-dashboard-menu.php:113
290
+ msgid "Current Score of Your Site: "
291
+ msgstr ""
292
+
293
+ #: ../admin/wp-security-dashboard-menu.php:168
294
+ msgid ""
295
+ "Below is the current status of the critical features that you should "
296
+ "activate on your site to achieve a minimum level of recommended security"
297
+ msgstr ""
298
+
299
+ #: ../admin/wp-security-dashboard-menu.php:172
300
+ msgid "Admin Username"
301
+ msgstr ""
302
+
303
+ #: ../admin/wp-security-dashboard-menu.php:187
304
+ msgid "Login Lockdown"
305
+ msgstr ""
306
+
307
+ #: ../admin/wp-security-dashboard-menu.php:202
308
+ msgid "File Permission"
309
+ msgstr ""
310
+
311
+ #: ../admin/wp-security-dashboard-menu.php:217
312
+ msgid "Basic Firewall"
313
+ msgstr ""
314
+
315
+ #: ../admin/wp-security-dashboard-menu.php:239
316
+ msgid ""
317
+ "Maintenance mode is currently enabled. Remember to turn it off when you are "
318
+ "done"
319
+ msgstr ""
320
+
321
+ #: ../admin/wp-security-dashboard-menu.php:242
322
+ msgid "Maintenance mode is currently off."
323
+ msgstr ""
324
+
325
+ #: ../admin/wp-security-dashboard-menu.php:246
326
+ msgid "Maintenance Mode"
327
+ msgstr ""
328
+
329
+ #: ../admin/wp-security-dashboard-menu.php:316
330
+ #: ../admin/wp-security-filesystem-menu.php:124
331
+ #: ../admin/wp-security-filesystem-menu.php:143
332
+ msgid "Name"
333
+ msgstr ""
334
+
335
+ #: ../admin/wp-security-dashboard-menu.php:317
336
+ msgid "Version"
337
+ msgstr ""
338
+
339
+ #: ../admin/wp-security-dashboard-menu.php:318
340
+ msgid "Plugin URL"
341
+ msgstr ""
342
+
343
+ #: ../admin/wp-security-database-menu.php:78
344
+ msgid "Nonce check failed for DB prefix change operation!"
345
+ msgstr ""
346
+
347
+ #: ../admin/wp-security-database-menu.php:86
348
+ msgid ""
349
+ "The plugin has detected that it cannot write to the wp-config.php file. This "
350
+ "feature can only be used if the plugin can successfully write to the wp-"
351
+ "config.php file."
352
+ msgstr ""
353
+
354
+ #: ../admin/wp-security-database-menu.php:99
355
+ msgid "Please enter a value for the DB prefix."
356
+ msgstr ""
357
+
358
+ #: ../admin/wp-security-database-menu.php:108
359
+ msgid ""
360
+ "<strong>ERROR</strong>: The table prefix can only contain numbers, letters, "
361
+ "and underscores."
362
+ msgstr ""
363
+
364
+ #: ../admin/wp-security-database-menu.php:116
365
+ msgid "Change Database Prefix"
366
+ msgstr ""
367
+
368
+ #: ../admin/wp-security-database-menu.php:119
369
+ msgid ""
370
+ "Your WordPress DB is the most important asset of your website because it "
371
+ "contains a lot of your site's precious information."
372
+ msgstr ""
373
+
374
+ #: ../admin/wp-security-database-menu.php:120
375
+ msgid ""
376
+ "The DB is also a target for hackers via methods such as SQL injections and "
377
+ "malicious and automated code which targets certain tables."
378
+ msgstr ""
379
+
380
+ #: ../admin/wp-security-database-menu.php:121
381
+ msgid ""
382
+ "One way to add a layer of protection for your DB is to change the default "
383
+ "WordPress table prefix from \"wp_\" to something else which will be "
384
+ "difficult for hackers to guess."
385
+ msgstr ""
386
+
387
+ #: ../admin/wp-security-database-menu.php:122
388
+ msgid ""
389
+ "This feature allows you to easily change the prefix to a value of your "
390
+ "choice or to a random value set by this plugin."
391
+ msgstr ""
392
+
393
+ #: ../admin/wp-security-database-menu.php:128
394
+ msgid "DB Prefix Options"
395
+ msgstr ""
396
+
397
+ #: ../admin/wp-security-database-menu.php:139
398
+ #, php-format
399
+ msgid "It is recommended that you perform a %s before using this feature"
400
+ msgstr ""
401
+
402
+ #: ../admin/wp-security-database-menu.php:148
403
+ msgid "Current DB Table Prefix"
404
+ msgstr ""
405
+
406
+ #: ../admin/wp-security-database-menu.php:154
407
+ msgid ""
408
+ "Your site is currently using the default WordPress DB prefix value of \"wp_"
409
+ "\". \n"
410
+ " To increase your site's security you should "
411
+ "consider changing the DB prefix value to another value."
412
+ msgstr ""
413
+
414
+ #: ../admin/wp-security-database-menu.php:161
415
+ msgid "Generate New DB Table Prefix"
416
+ msgstr ""
417
+
418
+ #: ../admin/wp-security-database-menu.php:164
419
+ msgid ""
420
+ "Check this if you want the plugin to generate a random 6 character string "
421
+ "for the table prefix"
422
+ msgstr ""
423
+
424
+ #: ../admin/wp-security-database-menu.php:165
425
+ msgid "OR"
426
+ msgstr ""
427
+
428
+ #: ../admin/wp-security-database-menu.php:167
429
+ msgid ""
430
+ "Choose your own DB prefix by specifying a string which contains letters and/"
431
+ "or numbers and/or underscores. Example: xyz_"
432
+ msgstr ""
433
+
434
+ #: ../admin/wp-security-database-menu.php:171
435
+ msgid "Change DB Prefix"
436
+ msgstr ""
437
+
438
+ #: ../admin/wp-security-database-menu.php:192
439
+ #: ../admin/wp-security-filesystem-menu.php:80
440
+ msgid "Nonce check failed for manual DB backup operation!"
441
+ msgstr ""
442
+
443
+ #: ../admin/wp-security-database-menu.php:201
444
+ msgid ""
445
+ "DB Backup was successfully completed! Right click on the following file name "
446
+ "and save the backup to your computer."
447
+ msgstr ""
448
+
449
+ #: ../admin/wp-security-database-menu.php:203
450
+ msgid "Your DB Backup File: "
451
+ msgstr ""
452
+
453
+ #: ../admin/wp-security-database-menu.php:211
454
+ msgid "DB Backup failed. Please check the permissions of the backup directory."
455
+ msgstr ""
456
+
457
+ #: ../admin/wp-security-database-menu.php:228
458
+ msgid ""
459
+ "You entered a non numeric value for the \"backup time interval\" field. It "
460
+ "has been set to the default value."
461
+ msgstr ""
462
+
463
+ #: ../admin/wp-security-database-menu.php:235
464
+ msgid ""
465
+ "You entered a non numeric value for the \"number of backup files to keep\" "
466
+ "field. It has been set to the default value."
467
+ msgstr ""
468
+
469
+ #: ../admin/wp-security-database-menu.php:242
470
+ #: ../admin/wp-security-user-login-menu.php:109
471
+ msgid ""
472
+ "You have entered an incorrect email address format. It has been set to your "
473
+ "WordPress admin email as default."
474
+ msgstr ""
475
+
476
+ #: ../admin/wp-security-database-menu.php:275
477
+ msgid "Manual Backup"
478
+ msgstr ""
479
+
480
+ #: ../admin/wp-security-database-menu.php:281
481
+ msgid "To create a new DB backup just click on the button below."
482
+ msgstr ""
483
+
484
+ #: ../admin/wp-security-database-menu.php:284
485
+ msgid "Create DB Backup Now"
486
+ msgstr ""
487
+
488
+ #: ../admin/wp-security-database-menu.php:288
489
+ msgid "Automated Scheduled Backups"
490
+ msgstr ""
491
+
492
+ #: ../admin/wp-security-database-menu.php:300
493
+ msgid "Enable Automated Scheduled Backups"
494
+ msgstr ""
495
+
496
+ #: ../admin/wp-security-database-menu.php:303
497
+ msgid ""
498
+ "Check this if you want the system to automatically generate backups "
499
+ "periodically based on the settings below"
500
+ msgstr ""
501
+
502
+ #: ../admin/wp-security-database-menu.php:307
503
+ msgid "Backup Time Interval"
504
+ msgstr ""
505
+
506
+ #: ../admin/wp-security-database-menu.php:310
507
+ msgid "Hours"
508
+ msgstr ""
509
+
510
+ #: ../admin/wp-security-database-menu.php:311
511
+ msgid "Days"
512
+ msgstr ""
513
+
514
+ #: ../admin/wp-security-database-menu.php:312
515
+ msgid "Weeks"
516
+ msgstr ""
517
+
518
+ #: ../admin/wp-security-database-menu.php:314
519
+ msgid "Set the value for how often you would like an automated backup to occur"
520
+ msgstr ""
521
+
522
+ #: ../admin/wp-security-database-menu.php:318
523
+ msgid "Number of Backup Files To Keep"
524
+ msgstr ""
525
+
526
+ #: ../admin/wp-security-database-menu.php:320
527
+ msgid ""
528
+ "Thie field allows you to choose the number of backup files you would like to "
529
+ "keep in the backup directory"
530
+ msgstr ""
531
+
532
+ #: ../admin/wp-security-database-menu.php:324
533
+ msgid "Send Backup File Via Email"
534
+ msgstr ""
535
+
536
+ #: ../admin/wp-security-database-menu.php:327
537
+ msgid ""
538
+ "Check this if you want the system to email you the backup file after a DB "
539
+ "backup has been performed"
540
+ msgstr ""
541
+
542
+ #: ../admin/wp-security-database-menu.php:329
543
+ #: ../admin/wp-security-user-login-menu.php:207
544
+ msgid "Enter an email address"
545
+ msgstr ""
546
+
547
+ #: ../admin/wp-security-database-menu.php:359
548
+ msgid "Starting DB prefix change operations....."
549
+ msgstr ""
550
+
551
+ #: ../admin/wp-security-database-menu.php:361
552
+ #, php-format
553
+ msgid ""
554
+ "Your WordPress system has a total of %s tables and your new DB prefix will "
555
+ "be: %s"
556
+ msgstr ""
557
+
558
+ #: ../admin/wp-security-database-menu.php:367
559
+ #: ../admin/wp-security-filesystem-menu.php:458
560
+ msgid ""
561
+ "Failed to make a backup of the wp-config.php file. This operation will not "
562
+ "go ahead."
563
+ msgstr ""
564
+
565
+ #: ../admin/wp-security-database-menu.php:371
566
+ msgid "A backup copy of your wp-config.php file was created successfully!"
567
+ msgstr ""
568
+
569
+ #: ../admin/wp-security-database-menu.php:394
570
+ #, php-format
571
+ msgid "%s table name update failed"
572
+ msgstr ""
573
+
574
+ #: ../admin/wp-security-database-menu.php:406
575
+ #, php-format
576
+ msgid "Please change the prefix manually for the above tables to: %s"
577
+ msgstr ""
578
+
579
+ #: ../admin/wp-security-database-menu.php:409
580
+ #, php-format
581
+ msgid "%s tables had their prefix updated successfully!"
582
+ msgstr ""
583
+
584
+ #: ../admin/wp-security-database-menu.php:424
585
+ msgid "wp-config.php file was updated successfully!"
586
+ msgstr ""
587
+
588
+ #: ../admin/wp-security-database-menu.php:427
589
+ #, php-format
590
+ msgid ""
591
+ "The \"wp-config.php\" file was not able to be modified. Please modify this "
592
+ "file manually using your favourite editor and search \n"
593
+ " for variable \"$table_prefix\" and assign the following "
594
+ "value to that variable: %s"
595
+ msgstr ""
596
+
597
+ #: ../admin/wp-security-database-menu.php:448
598
+ msgid "There was an error when updating the options table."
599
+ msgstr ""
600
+
601
+ #: ../admin/wp-security-database-menu.php:452
602
+ msgid ""
603
+ "The options table records which had references to the old DB prefix were "
604
+ "updated successfully!"
605
+ msgstr ""
606
+
607
+ #: ../admin/wp-security-database-menu.php:477
608
+ #, php-format
609
+ msgid ""
610
+ "Error updating user_meta table where new meta_key = %s, old meta_key = %s "
611
+ "and user_id = %s."
612
+ msgstr ""
613
+
614
+ #: ../admin/wp-security-database-menu.php:483
615
+ msgid ""
616
+ "The usermeta table records which had references to the old DB prefix were "
617
+ "updated successfully!"
618
+ msgstr ""
619
+
620
+ #: ../admin/wp-security-database-menu.php:485
621
+ msgid "DB prefix change tasks have been completed."
622
+ msgstr ""
623
+
624
+ #: ../admin/wp-security-filesystem-menu.php:90
625
+ #, php-format
626
+ msgid "The permissions for %s were succesfully changed to %s"
627
+ msgstr ""
628
+
629
+ #: ../admin/wp-security-filesystem-menu.php:94
630
+ #, php-format
631
+ msgid "Unable to change permissions for %s!"
632
+ msgstr ""
633
+
634
+ #: ../admin/wp-security-filesystem-menu.php:100
635
+ msgid "File Permissions Scan"
636
+ msgstr ""
637
+
638
+ #: ../admin/wp-security-filesystem-menu.php:103
639
+ msgid ""
640
+ "Your WordPress file and folder permission settings govern the accessability "
641
+ "and read/write privileges of the files and folders which make up your WP "
642
+ "installation."
643
+ msgstr ""
644
+
645
+ #: ../admin/wp-security-filesystem-menu.php:104
646
+ msgid ""
647
+ "Your WP installation already comes with reasonably secure file permission "
648
+ "settings for the filesystem."
649
+ msgstr ""
650
+
651
+ #: ../admin/wp-security-filesystem-menu.php:105
652
+ msgid ""
653
+ "However, sometimes people or other plugins modify the various permission "
654
+ "settings of certain core WP folders or files such that they end up making "
655
+ "their site less secure because they chose the wrong permission values."
656
+ msgstr ""
657
+
658
+ #: ../admin/wp-security-filesystem-menu.php:106
659
+ msgid ""
660
+ "This feature will scan the critical WP core folders and files and will "
661
+ "highlight any permission settings which are insecure."
662
+ msgstr ""
663
+
664
+ #: ../admin/wp-security-filesystem-menu.php:112
665
+ msgid "WP Directory and File Permissions Scan Results"
666
+ msgstr ""
667
+
668
+ #: ../admin/wp-security-filesystem-menu.php:125
669
+ #: ../admin/wp-security-filesystem-menu.php:144
670
+ msgid "File/Folder"
671
+ msgstr ""
672
+
673
+ #: ../admin/wp-security-filesystem-menu.php:126
674
+ #: ../admin/wp-security-filesystem-menu.php:145
675
+ msgid "Current Permissions"
676
+ msgstr ""
677
+
678
+ #: ../admin/wp-security-filesystem-menu.php:127
679
+ #: ../admin/wp-security-filesystem-menu.php:146
680
+ msgid "Recommended Permissions"
681
+ msgstr ""
682
+
683
+ #: ../admin/wp-security-filesystem-menu.php:128
684
+ #: ../admin/wp-security-filesystem-menu.php:147
685
+ msgid "Recommended Action"
686
+ msgstr ""
687
+
688
+ #: ../admin/wp-security-filesystem-menu.php:190
689
+ msgid "File Editing"
690
+ msgstr ""
691
+
692
+ #: ../admin/wp-security-filesystem-menu.php:193
693
+ msgid ""
694
+ "The Wordpress Dashboard by default allows administrators to edit PHP files, "
695
+ "such as plugin and theme files."
696
+ msgstr ""
697
+
698
+ #: ../admin/wp-security-filesystem-menu.php:194
699
+ msgid ""
700
+ "This is often the first tool an attacker will use if able to login, since it "
701
+ "allows code execution."
702
+ msgstr ""
703
+
704
+ #: ../admin/wp-security-filesystem-menu.php:195
705
+ msgid ""
706
+ "This feature will disable the ability for people to edit PHP files via the "
707
+ "dashboard."
708
+ msgstr ""
709
+
710
+ #: ../admin/wp-security-filesystem-menu.php:201
711
+ msgid "Disable PHP File Editing"
712
+ msgstr ""
713
+
714
+ #: ../admin/wp-security-filesystem-menu.php:213
715
+ msgid "Disable Ability To Edit PHP Files"
716
+ msgstr ""
717
+
718
+ #: ../admin/wp-security-filesystem-menu.php:216
719
+ msgid ""
720
+ "Check this if you want to remove the ability for people to edit PHP files "
721
+ "via the WP dashboard"
722
+ msgstr ""
723
+
724
+ #: ../admin/wp-security-filesystem-menu.php:260
725
+ msgid ""
726
+ "You have successfully saved the Prevent Access to Default WP Files "
727
+ "configuration."
728
+ msgstr ""
729
+
730
+ #: ../admin/wp-security-filesystem-menu.php:264
731
+ #: ../admin/wp-security-firewall-menu.php:116
732
+ #: ../admin/wp-security-firewall-menu.php:270
733
+ #: ../admin/wp-security-firewall-menu.php:481
734
+ #: ../admin/wp-security-firewall-menu.php:611
735
+ msgid ""
736
+ "Could not write to the .htaccess file. Please check the file permissions."
737
+ msgstr ""
738
+
739
+ #: ../admin/wp-security-filesystem-menu.php:269
740
+ msgid "WordPress Files"
741
+ msgstr ""
742
+
743
+ #: ../admin/wp-security-filesystem-menu.php:272
744
+ #, php-format
745
+ msgid ""
746
+ "This feature allows you to prevent access to files such as %s, %s and %s "
747
+ "which are delivered with all WP installations."
748
+ msgstr ""
749
+
750
+ #: ../admin/wp-security-filesystem-menu.php:273
751
+ msgid ""
752
+ "By preventing access to these files you are hiding some key pieces of "
753
+ "information (such as WordPress version info) from potential hackers."
754
+ msgstr ""
755
+
756
+ #: ../admin/wp-security-filesystem-menu.php:278
757
+ msgid "Prevent Access to Default WP Files"
758
+ msgstr ""
759
+
760
+ #: ../admin/wp-security-filesystem-menu.php:289
761
+ msgid "Prevent Access to WP Default Install Files"
762
+ msgstr ""
763
+
764
+ #: ../admin/wp-security-filesystem-menu.php:292
765
+ msgid ""
766
+ "Check this if you want to prevent access to readme.html, license.txt and wp-"
767
+ "config-sample.php."
768
+ msgstr ""
769
+
770
+ #: ../admin/wp-security-filesystem-menu.php:296
771
+ msgid "Save Setting"
772
+ msgstr ""
773
+
774
+ #: ../admin/wp-security-filesystem-menu.php:307
775
+ msgid "System Logs"
776
+ msgstr ""
777
+
778
+ #: ../admin/wp-security-filesystem-menu.php:310
779
+ msgid ""
780
+ "Sometimes your hosting platform will produce error or warning logs in a file "
781
+ "called \"error_log\"."
782
+ msgstr ""
783
+
784
+ #: ../admin/wp-security-filesystem-menu.php:311
785
+ msgid ""
786
+ "Depending on the nature and cause of the error or warning, your hosting "
787
+ "server can create multiple instances of this file in numerous directory "
788
+ "locations of your WordPress installation."
789
+ msgstr ""
790
+
791
+ #: ../admin/wp-security-filesystem-menu.php:312
792
+ msgid ""
793
+ "By occassionally viewing the contents of these logs files you can keep "
794
+ "informed of any underlying problems on your system which you might need to "
795
+ "address."
796
+ msgstr ""
797
+
798
+ #: ../admin/wp-security-filesystem-menu.php:318
799
+ msgid "View System Logs"
800
+ msgstr ""
801
+
802
+ #: ../admin/wp-security-filesystem-menu.php:323
803
+ msgid "View Latest System Logs"
804
+ msgstr ""
805
+
806
+ #: ../admin/wp-security-filesystem-menu.php:325
807
+ msgid "Loading..."
808
+ msgstr ""
809
+
810
+ #: ../admin/wp-security-filesystem-menu.php:342
811
+ msgid "No system logs were found!"
812
+ msgstr ""
813
+
814
+ #: ../admin/wp-security-filesystem-menu.php:395
815
+ msgid "Set Recommended Permissions"
816
+ msgstr ""
817
+
818
+ #: ../admin/wp-security-filesystem-menu.php:401
819
+ msgid "No Action Required"
820
+ msgstr ""
821
+
822
+ #: ../admin/wp-security-filesystem-menu.php:434
823
+ msgid ""
824
+ "Your system config file is already configured to disallow PHP file editing."
825
+ msgstr ""
826
+
827
+ #: ../admin/wp-security-filesystem-menu.php:445
828
+ #: ../admin/wp-security-filesystem-menu.php:472
829
+ msgid ""
830
+ "Settings Saved - Your system is now configured to not allow PHP file editing."
831
+ msgstr ""
832
+
833
+ #: ../admin/wp-security-filesystem-menu.php:449
834
+ #: ../admin/wp-security-filesystem-menu.php:475
835
+ #: ../admin/wp-security-filesystem-menu.php:525
836
+ msgid "Operation failed! Unable to modify wp-config.php file!"
837
+ msgstr ""
838
+
839
+ #: ../admin/wp-security-filesystem-menu.php:463
840
+ msgid "A backup copy of your wp-config.php file was created successfully...."
841
+ msgstr ""
842
+
843
+ #: ../admin/wp-security-filesystem-menu.php:506
844
+ #: ../admin/wp-security-filesystem-menu.php:514
845
+ msgid ""
846
+ "Your system config file is already configured to allow PHP file editing."
847
+ msgstr ""
848
+
849
+ #: ../admin/wp-security-filesystem-menu.php:521
850
+ msgid ""
851
+ "Settings Saved - Your system is now configured to allow PHP file editing."
852
+ msgstr ""
853
+
854
+ #: ../admin/wp-security-filesystem-menu.php:565
855
+ #, php-format
856
+ msgid "Showing latest entries of error_log file: %s"
857
+ msgstr ""
858
+
859
+ #: ../admin/wp-security-firewall-menu.php:112
860
+ msgid "Settings were successfully saved"
861
+ msgstr ""
862
+
863
+ #: ../admin/wp-security-firewall-menu.php:121
864
+ #: ../admin/wp-security-firewall-menu.php:486
865
+ msgid "Firewall Settings"
866
+ msgstr ""
867
+
868
+ #: ../admin/wp-security-firewall-menu.php:128
869
+ #: ../admin/wp-security-firewall-menu.php:627
870
+ #, php-format
871
+ msgid ""
872
+ "This should not have any impact on your site's general functionality but if "
873
+ "you wish you can take a %s of your .htaccess file before proceeding."
874
+ msgstr ""
875
+
876
+ #: ../admin/wp-security-firewall-menu.php:129
877
+ msgid ""
878
+ "The features in this tab allow you to activate some basic firewall security "
879
+ "protection rules for your site."
880
+ msgstr ""
881
+
882
+ #: ../admin/wp-security-firewall-menu.php:130
883
+ msgid ""
884
+ "The firewall functionality is achieved via the insertion of special code "
885
+ "into your currently active .htaccess file."
886
+ msgstr ""
887
+
888
+ #: ../admin/wp-security-firewall-menu.php:136
889
+ msgid "Basic Firewall Settings"
890
+ msgstr ""
891
+
892
+ #: ../admin/wp-security-firewall-menu.php:144
893
+ msgid "Enable Basic Firewall Protection"
894
+ msgstr ""
895
+
896
+ #: ../admin/wp-security-firewall-menu.php:147
897
+ msgid "Check this if you want to apply basic firewall protection to your site."
898
+ msgstr ""
899
+
900
+ #: ../admin/wp-security-firewall-menu.php:151
901
+ msgid ""
902
+ "This setting will implement the following basic firewall protection "
903
+ "mechanisms on your site:"
904
+ msgstr ""
905
+
906
+ #: ../admin/wp-security-firewall-menu.php:152
907
+ msgid "1) Protect your htaccess file by denying access to it."
908
+ msgstr ""
909
+
910
+ #: ../admin/wp-security-firewall-menu.php:153
911
+ msgid "2) Disable the server signature."
912
+ msgstr ""
913
+
914
+ #: ../admin/wp-security-firewall-menu.php:154
915
+ msgid "3) Limit file upload size (10MB)."
916
+ msgstr ""
917
+
918
+ #: ../admin/wp-security-firewall-menu.php:155
919
+ msgid "4) Protect your wp-config.php file by denying access to it."
920
+ msgstr ""
921
+
922
+ #: ../admin/wp-security-firewall-menu.php:156
923
+ msgid ""
924
+ "The above firewall features will be applied via your .htaccess file and "
925
+ "should not affect your site's overall functionality."
926
+ msgstr ""
927
+
928
+ #: ../admin/wp-security-firewall-menu.php:157
929
+ msgid ""
930
+ "You are still advised to take a backup of your active .htaccess file just in "
931
+ "case."
932
+ msgstr ""
933
+
934
+ #: ../admin/wp-security-firewall-menu.php:166
935
+ msgid "WordPress Pingback Vulnerability Protection"
936
+ msgstr ""
937
+
938
+ #: ../admin/wp-security-firewall-menu.php:174
939
+ msgid "Enable Pingback Protection"
940
+ msgstr ""
941
+
942
+ #: ../admin/wp-security-firewall-menu.php:177
943
+ msgid ""
944
+ "Check this if you are not using the WP XML-RPC functionality and you want to "
945
+ "enable protection against WordPress pingback vulnerabilities."
946
+ msgstr ""
947
+
948
+ #: ../admin/wp-security-firewall-menu.php:181
949
+ msgid ""
950
+ "This setting will add a directive in your .htaccess to disable access to the "
951
+ "WordPress xmlrpc.php file which is responsible for the XML-RPC functionality "
952
+ "such as pingbacks in WordPress."
953
+ msgstr ""
954
+
955
+ #: ../admin/wp-security-firewall-menu.php:182
956
+ msgid ""
957
+ "Hackers can exploit various pingback vulnerabilities in the WordPress XML-"
958
+ "RPC API in a number of ways such as:"
959
+ msgstr ""
960
+
961
+ #: ../admin/wp-security-firewall-menu.php:183
962
+ msgid "1) Denial of Service (DoS) attacks"
963
+ msgstr ""
964
+
965
+ #: ../admin/wp-security-firewall-menu.php:184
966
+ msgid "2) Hacking internal routers."
967
+ msgstr ""
968
+
969
+ #: ../admin/wp-security-firewall-menu.php:185
970
+ msgid "3) Scanning ports in internal networks to get info from various hosts."
971
+ msgstr ""
972
+
973
+ #: ../admin/wp-security-firewall-menu.php:186
974
+ msgid ""
975
+ "Apart from the security protection benefit, this feature may also help "
976
+ "reduce load on your server, particularly if your site currently has a lot of "
977
+ "unwanted traffic hitting the XML-RPC API on your installation."
978
+ msgstr ""
979
+
980
+ #: ../admin/wp-security-firewall-menu.php:187
981
+ msgid ""
982
+ "NOTE: You should only enable this feature if you are not currently using the "
983
+ "XML-RPC functionality on your WordPress installation."
984
+ msgstr ""
985
+
986
+ #: ../admin/wp-security-firewall-menu.php:194
987
+ msgid "Save Basic Firewall Settings"
988
+ msgstr ""
989
+
990
+ #: ../admin/wp-security-firewall-menu.php:266
991
+ msgid ""
992
+ "You have successfully saved the Additional Firewall Protection configuration"
993
+ msgstr ""
994
+
995
+ #: ../admin/wp-security-firewall-menu.php:280
996
+ msgid "Additional Firewall Protection"
997
+ msgstr ""
998
+
999
+ #: ../admin/wp-security-firewall-menu.php:284
1000
+ #, php-format
1001
+ msgid ""
1002
+ "Due to the nature of the code being inserted to the .htaccess file, this "
1003
+ "feature may break some functionality for certain plugins and you are "
1004
+ "therefore advised to take a %s of .htaccess before applying this "
1005
+ "configuration."
1006
+ msgstr ""
1007
+
1008
+ #: ../admin/wp-security-firewall-menu.php:286
1009
+ msgid ""
1010
+ "This feature allows you to activate more advanced firewall settings to your "
1011
+ "site."
1012
+ msgstr ""
1013
+
1014
+ #: ../admin/wp-security-firewall-menu.php:287
1015
+ msgid ""
1016
+ "The advanced firewall rules are applied via the insertion of special code to "
1017
+ "your currently active .htaccess file."
1018
+ msgstr ""
1019
+
1020
+ #: ../admin/wp-security-firewall-menu.php:296
1021
+ msgid "Listing of Directory Contents"
1022
+ msgstr ""
1023
+
1024
+ #: ../admin/wp-security-firewall-menu.php:305
1025
+ msgid "Disable Index Views"
1026
+ msgstr ""
1027
+
1028
+ #: ../admin/wp-security-firewall-menu.php:308
1029
+ msgid "Check this if you want to disable directory and file listing."
1030
+ msgstr ""
1031
+
1032
+ #: ../admin/wp-security-firewall-menu.php:313
1033
+ msgid ""
1034
+ "By default, an Apache server will allow the listing of the contents of a "
1035
+ "directory if it doesn't contain an index.php file."
1036
+ msgstr ""
1037
+
1038
+ #: ../admin/wp-security-firewall-menu.php:315
1039
+ msgid "This feature will prevent the listing of contents for all directories."
1040
+ msgstr ""
1041
+
1042
+ #: ../admin/wp-security-firewall-menu.php:317
1043
+ msgid ""
1044
+ "NOTE: In order for this feature to work \"AllowOverride\" must be enabled in "
1045
+ "your httpd.conf file. Ask your hosting provider to check this if you don't "
1046
+ "have access to httpd.conf"
1047
+ msgstr ""
1048
+
1049
+ #: ../admin/wp-security-firewall-menu.php:326
1050
+ msgid "Trace and Track"
1051
+ msgstr ""
1052
+
1053
+ #: ../admin/wp-security-firewall-menu.php:335
1054
+ msgid "Disable Trace and Track"
1055
+ msgstr ""
1056
+
1057
+ #: ../admin/wp-security-firewall-menu.php:338
1058
+ msgid "Check this if you want to disable trace and track."
1059
+ msgstr ""
1060
+
1061
+ #: ../admin/wp-security-firewall-menu.php:343
1062
+ msgid ""
1063
+ "HTTP Trace attack (XST) can be used to return header requests and grab "
1064
+ "cookies and other information."
1065
+ msgstr ""
1066
+
1067
+ #: ../admin/wp-security-firewall-menu.php:345
1068
+ msgid ""
1069
+ "This hacking technique is usually used together with cross site scripting "
1070
+ "attacks (XSS)."
1071
+ msgstr ""
1072
+
1073
+ #: ../admin/wp-security-firewall-menu.php:347
1074
+ msgid ""
1075
+ "Disabling trace and track on your site will help prevent HTTP Trace attacks."
1076
+ msgstr ""
1077
+
1078
+ #: ../admin/wp-security-firewall-menu.php:356
1079
+ msgid "Proxy Comment Posting"
1080
+ msgstr ""
1081
+
1082
+ #: ../admin/wp-security-firewall-menu.php:366
1083
+ msgid "Forbid Proxy Comment Posting"
1084
+ msgstr ""
1085
+
1086
+ #: ../admin/wp-security-firewall-menu.php:369
1087
+ msgid "Check this if you want to forbid proxy comment posting."
1088
+ msgstr ""
1089
+
1090
+ #: ../admin/wp-security-firewall-menu.php:374
1091
+ msgid ""
1092
+ "This setting will deny any requests that use a proxy server when posting "
1093
+ "comments."
1094
+ msgstr ""
1095
+
1096
+ #: ../admin/wp-security-firewall-menu.php:375
1097
+ msgid ""
1098
+ "By forbidding proxy comments you are in effect eliminating some SPAM and "
1099
+ "other proxy requests."
1100
+ msgstr ""
1101
+
1102
+ #: ../admin/wp-security-firewall-menu.php:384
1103
+ msgid "Bad Query Strings"
1104
+ msgstr ""
1105
+
1106
+ #: ../admin/wp-security-firewall-menu.php:394
1107
+ msgid "Deny Bad Query Strings"
1108
+ msgstr ""
1109
+
1110
+ #: ../admin/wp-security-firewall-menu.php:397
1111
+ msgid "This will help protect you against malicious queries via XSS."
1112
+ msgstr ""
1113
+
1114
+ #: ../admin/wp-security-firewall-menu.php:402
1115
+ msgid ""
1116
+ "This feature will write rules in your .htaccess file to prevent malicious "
1117
+ "string attacks on your site using XSS."
1118
+ msgstr ""
1119
+
1120
+ #: ../admin/wp-security-firewall-menu.php:403
1121
+ msgid ""
1122
+ "NOTE: Some of these strings might be used for plugins or themes and hence "
1123
+ "this might break some functionality."
1124
+ msgstr ""
1125
+
1126
+ #: ../admin/wp-security-firewall-menu.php:404
1127
+ #: ../admin/wp-security-firewall-menu.php:434
1128
+ msgid ""
1129
+ "You are therefore strongly advised to take a backup of your active .htaccess "
1130
+ "file before applying this feature."
1131
+ msgstr ""
1132
+
1133
+ #: ../admin/wp-security-firewall-menu.php:413
1134
+ msgid "Advanced Character String Filter"
1135
+ msgstr ""
1136
+
1137
+ #: ../admin/wp-security-firewall-menu.php:423
1138
+ msgid "Enable Advanced Character String Filter"
1139
+ msgstr ""
1140
+
1141
+ #: ../admin/wp-security-firewall-menu.php:426
1142
+ msgid "This will block bad character matches from XSS."
1143
+ msgstr ""
1144
+
1145
+ #: ../admin/wp-security-firewall-menu.php:431
1146
+ msgid ""
1147
+ "This is an advanced character string filter to prevent malicious string "
1148
+ "attacks on your site coming from Cross Site Scripting (XSS)."
1149
+ msgstr ""
1150
+
1151
+ #: ../admin/wp-security-firewall-menu.php:432
1152
+ msgid ""
1153
+ "This setting matches for common malicious string patterns and exploits and "
1154
+ "will produce a 403 error for the hacker attempting the query."
1155
+ msgstr ""
1156
+
1157
+ #: ../admin/wp-security-firewall-menu.php:433
1158
+ msgid "NOTE: Some strings for this setting might break some functionality."
1159
+ msgstr ""
1160
+
1161
+ #: ../admin/wp-security-firewall-menu.php:442
1162
+ msgid "Save Additional Firewall Settings"
1163
+ msgstr ""
1164
+
1165
+ #: ../admin/wp-security-firewall-menu.php:477
1166
+ msgid "You have successfully saved the 5G Firewall Protection configuration"
1167
+ msgstr ""
1168
+
1169
+ #: ../admin/wp-security-firewall-menu.php:490
1170
+ #, php-format
1171
+ msgid ""
1172
+ "This feature allows you to activate the 5G firewall security protection "
1173
+ "rules designed and produced by %s."
1174
+ msgstr ""
1175
+
1176
+ #: ../admin/wp-security-firewall-menu.php:491
1177
+ msgid ""
1178
+ "The 5G Blacklist is a simple, flexible blacklist that helps reduce the "
1179
+ "number of malicious URL requests that hit your website."
1180
+ msgstr ""
1181
+
1182
+ #: ../admin/wp-security-firewall-menu.php:492
1183
+ msgid ""
1184
+ "The added advantage of applying the 5G firewall to your site is that it has "
1185
+ "been tested and confirmed by the people at PerishablePress.com to be an "
1186
+ "optimal and least disruptive set of .htaccess security rules for general WP "
1187
+ "sites running on an Apache server or similar."
1188
+ msgstr ""
1189
+
1190
+ #: ../admin/wp-security-firewall-menu.php:493
1191
+ #, php-format
1192
+ msgid ""
1193
+ "Therefore the 5G firewall rules should not have any impact on your site's "
1194
+ "general functionality but if you wish you can take a %s of your .htaccess "
1195
+ "file before proceeding."
1196
+ msgstr ""
1197
+
1198
+ #: ../admin/wp-security-firewall-menu.php:499
1199
+ msgid "5G Blacklist/Firewall Settings"
1200
+ msgstr ""
1201
+
1202
+ #: ../admin/wp-security-firewall-menu.php:511
1203
+ msgid "Enable 5G Firewall Protection"
1204
+ msgstr ""
1205
+
1206
+ #: ../admin/wp-security-firewall-menu.php:514
1207
+ msgid ""
1208
+ "Check this if you want to apply the 5G Blacklist firewall protection from "
1209
+ "perishablepress.com to your site."
1210
+ msgstr ""
1211
+
1212
+ #: ../admin/wp-security-firewall-menu.php:518
1213
+ msgid ""
1214
+ "This setting will implement the 5G security firewall protection mechanisms "
1215
+ "on your site which include the following things:"
1216
+ msgstr ""
1217
+
1218
+ #: ../admin/wp-security-firewall-menu.php:519
1219
+ msgid "1) Block forbidden characters commonly used in exploitative attacks."
1220
+ msgstr ""
1221
+
1222
+ #: ../admin/wp-security-firewall-menu.php:520
1223
+ msgid "2) Block malicious encoded URL characters such as the \".css(\" string."
1224
+ msgstr ""
1225
+
1226
+ #: ../admin/wp-security-firewall-menu.php:521
1227
+ msgid ""
1228
+ "3) Guard against the common patterns and specific exploits in the root "
1229
+ "portion of targeted URLs."
1230
+ msgstr ""
1231
+
1232
+ #: ../admin/wp-security-firewall-menu.php:522
1233
+ msgid ""
1234
+ "4) Stop attackers from manipulating query strings by disallowing illicit "
1235
+ "characters."
1236
+ msgstr ""
1237
+
1238
+ #: ../admin/wp-security-firewall-menu.php:523
1239
+ msgid "....and much more."
1240
+ msgstr ""
1241
+
1242
+ #: ../admin/wp-security-firewall-menu.php:529
1243
+ msgid "Save 5G Firewall Settings"
1244
+ msgstr ""
1245
+
1246
+ #: ../admin/wp-security-firewall-menu.php:557
1247
+ msgid ""
1248
+ "Settings have not been saved - your secret word must consist only of "
1249
+ "alphanumeric characters, ie, letters and/or numbers only!"
1250
+ msgstr ""
1251
+
1252
+ #: ../admin/wp-security-firewall-menu.php:575
1253
+ msgid ""
1254
+ "You have successfully enabled the cookie based brute force prevention feature"
1255
+ msgstr ""
1256
+
1257
+ #: ../admin/wp-security-firewall-menu.php:576
1258
+ msgid ""
1259
+ "From now on you will need to log into your WP Admin using the following URL:"
1260
+ msgstr ""
1261
+
1262
+ #: ../admin/wp-security-firewall-menu.php:578
1263
+ msgid ""
1264
+ "It is important that you save this URL value somewhere in case you forget "
1265
+ "it, OR,"
1266
+ msgstr ""
1267
+
1268
+ #: ../admin/wp-security-firewall-menu.php:579
1269
+ #, php-format
1270
+ msgid "simply remember to add a \"?%s=1\" to your current site URL address."
1271
+ msgstr ""
1272
+
1273
+ #: ../admin/wp-security-firewall-menu.php:585
1274
+ msgid ""
1275
+ "You have successfully saved cookie based brute force prevention feature "
1276
+ "settings."
1277
+ msgstr ""
1278
+
1279
+ #: ../admin/wp-security-firewall-menu.php:621
1280
+ msgid "Brute Force Prevention Firewall Settings"
1281
+ msgstr ""
1282
+
1283
+ #: ../admin/wp-security-firewall-menu.php:628
1284
+ msgid ""
1285
+ "A Brute Force Attack is when a hacker tries many combinations of usernames "
1286
+ "and passwords until they succeed in guessing the right combination."
1287
+ msgstr ""
1288
+
1289
+ #: ../admin/wp-security-firewall-menu.php:629
1290
+ msgid ""
1291
+ "Due to the fact that at any one time there may be many concurrent login "
1292
+ "attempts occurring on your site via malicious automated robots, this also "
1293
+ "has a negative impact on your server's memory and performance."
1294
+ msgstr ""
1295
+
1296
+ #: ../admin/wp-security-firewall-menu.php:630
1297
+ msgid ""
1298
+ "The features in this tab will stop the majority of Brute Force Login Attacks "
1299
+ "at the .htaccess level thus providing even better protection for your WP "
1300
+ "login page and also reducing the load on your server because the system does "
1301
+ "not have to run PHP code to process the login attempts."
1302
+ msgstr ""
1303
+
1304
+ #: ../admin/wp-security-firewall-menu.php:636
1305
+ msgid "Cookie Based Brute Force Login Prevention"
1306
+ msgstr ""
1307
+
1308
+ #: ../admin/wp-security-firewall-menu.php:647
1309
+ msgid "Enable Brute Force Attack Prevention"
1310
+ msgstr ""
1311
+
1312
+ #: ../admin/wp-security-firewall-menu.php:650
1313
+ msgid ""
1314
+ "Check this if you want to protect your login page from Brute Force Attack."
1315
+ msgstr ""
1316
+
1317
+ #: ../admin/wp-security-firewall-menu.php:655
1318
+ msgid ""
1319
+ "This feature will deny access to your WordPress login page for all people "
1320
+ "except those who have a special cookie in their browser."
1321
+ msgstr ""
1322
+
1323
+ #: ../admin/wp-security-firewall-menu.php:657
1324
+ msgid "To use this feature do the following:"
1325
+ msgstr ""
1326
+
1327
+ #: ../admin/wp-security-firewall-menu.php:659
1328
+ msgid "1) Enable the checkbox."
1329
+ msgstr ""
1330
+
1331
+ #: ../admin/wp-security-firewall-menu.php:661
1332
+ msgid ""
1333
+ "2) Enter a secret word consisting of alphanumeric characters which will be "
1334
+ "difficult to guess. This secret word will be useful whenever you need to "
1335
+ "know the special URL which you will use to access the login page (see point "
1336
+ "below)."
1337
+ msgstr ""
1338
+
1339
+ #: ../admin/wp-security-firewall-menu.php:663
1340
+ msgid ""
1341
+ "3) You will then be provided with a special login URL. You will need to use "
1342
+ "this URL to login to your WordPress site instead of the usual login URL. "
1343
+ "NOTE: The system will deposit a special cookie in your browser which will "
1344
+ "allow you access to the WordPress administration login page."
1345
+ msgstr ""
1346
+
1347
+ #: ../admin/wp-security-firewall-menu.php:665
1348
+ msgid ""
1349
+ "Any person trying to access your login page who does not have the special "
1350
+ "cookie in their browser will be automatically blocked."
1351
+ msgstr ""
1352
+
1353
+ #: ../admin/wp-security-firewall-menu.php:672
1354
+ msgid "Secret Word"
1355
+ msgstr ""
1356
+
1357
+ #: ../admin/wp-security-firewall-menu.php:674
1358
+ msgid ""
1359
+ "Choose a secret word consisting of alphanumeric characters which you can use "
1360
+ "to access your special URL. Your are highly encouraged to choose a word "
1361
+ "which will be difficult to guess."
1362
+ msgstr ""
1363
+
1364
+ #: ../admin/wp-security-firewall-menu.php:678
1365
+ msgid "Re-direct URL"
1366
+ msgstr ""
1367
+
1368
+ #: ../admin/wp-security-firewall-menu.php:682
1369
+ msgid ""
1370
+ "Specify a URL to redirect a hacker to when they try to access your WordPress "
1371
+ "login page."
1372
+ msgstr ""
1373
+
1374
+ #: ../admin/wp-security-firewall-menu.php:689
1375
+ msgid ""
1376
+ "The URL specified here can be any site's URL and does not have to be your "
1377
+ "own. For example you can be as creative as you like and send hackers to the "
1378
+ "CIA or NSA home page."
1379
+ msgstr ""
1380
+
1381
+ #: ../admin/wp-security-firewall-menu.php:691
1382
+ msgid ""
1383
+ "This field will default to: http://127.0.0.1 if you do not enter a value."
1384
+ msgstr ""
1385
+
1386
+ #: ../admin/wp-security-firewall-menu.php:693
1387
+ msgid "Useful Tip:"
1388
+ msgstr ""
1389
+
1390
+ #: ../admin/wp-security-firewall-menu.php:695
1391
+ msgid ""
1392
+ "It's a good idea to not redirect attempted brute force login attempts to "
1393
+ "your site because it increases the load on your server."
1394
+ msgstr ""
1395
+
1396
+ #: ../admin/wp-security-firewall-menu.php:697
1397
+ msgid ""
1398
+ "Redirecting a hacker or malicious bot back to \"http://127.0.0.1\" is ideal "
1399
+ "because it deflects them back to their own local host and puts the load on "
1400
+ "their server instead of yours."
1401
+ msgstr ""
1402
+
1403
+ #: ../admin/wp-security-firewall-menu.php:704
1404
+ msgid "My Site Has Posts Or Pages Which Are Password Protected"
1405
+ msgstr ""
1406
+
1407
+ #: ../admin/wp-security-firewall-menu.php:707
1408
+ msgid ""
1409
+ "Check this if you are using the native WordPress password protection feature "
1410
+ "for some or all of your blog posts or pages."
1411
+ msgstr ""
1412
+
1413
+ #: ../admin/wp-security-firewall-menu.php:712
1414
+ msgid ""
1415
+ "In the cases where you are protecting some of your posts or pages using the "
1416
+ "in-built WordPress password protection feature, a few extra lines of "
1417
+ "directives and exceptions need to be added to your .htacces file so that "
1418
+ "people trying to access pages are not automatically blocked."
1419
+ msgstr ""
1420
+
1421
+ #: ../admin/wp-security-firewall-menu.php:714
1422
+ msgid ""
1423
+ "By enabling this checkbox the plugin will add the necessary rules and "
1424
+ "exceptions to your .htacces file so that people trying to access these pages "
1425
+ "are not automatically blocked."
1426
+ msgstr ""
1427
+
1428
+ #: ../admin/wp-security-firewall-menu.php:716
1429
+ msgid "Helpful Tip:"
1430
+ msgstr ""
1431
+
1432
+ #: ../admin/wp-security-firewall-menu.php:718
1433
+ msgid ""
1434
+ "If you do not use the WordPress password protection feature for your posts "
1435
+ "or pages then it is highly recommended that you leave this checkbox disabled."
1436
+ msgstr ""
1437
+
1438
+ #: ../admin/wp-security-firewall-menu.php:733
1439
+ msgid "The cookie test was successful. You can now enable this feature."
1440
+ msgstr ""
1441
+
1442
+ #: ../admin/wp-security-firewall-menu.php:736
1443
+ msgid "Save Feature Settings"
1444
+ msgstr ""
1445
+
1446
+ #: ../admin/wp-security-firewall-menu.php:743
1447
+ msgid ""
1448
+ "The cookie test failed on this server. So this feature cannot be used on "
1449
+ "this site."
1450
+ msgstr ""
1451
+
1452
+ #: ../admin/wp-security-firewall-menu.php:749
1453
+ msgid ""
1454
+ "Before using this feature you are required to perform a cookie test first. "
1455
+ "This is to make sure that your browser cookie is working correctly and that "
1456
+ "you won't lock yourself out."
1457
+ msgstr ""
1458
+
1459
+ #: ../admin/wp-security-firewall-menu.php:751
1460
+ msgid "Perform Cookie Test"
1461
+ msgstr ""
1462
+
1463
+ #: ../admin/wp-security-list-acct-activity.php:79
1464
+ #: ../admin/wp-security-list-comment-spammer-ip.php:76
1465
+ #: ../admin/wp-security-list-locked-ip.php:80
1466
+ #: ../admin/wp-security-list-locked-ip.php:91
1467
+ #: ../admin/wp-security-list-login-fails.php:78
1468
+ msgid "Please select some records using the checkboxes"
1469
+ msgstr ""
1470
+
1471
+ #: ../admin/wp-security-list-acct-activity.php:107
1472
+ #: ../admin/wp-security-list-login-fails.php:107
1473
+ msgid "The selected entries were deleted successfully!"
1474
+ msgstr ""
1475
+
1476
+ #: ../admin/wp-security-list-acct-activity.php:120
1477
+ #: ../admin/wp-security-list-login-fails.php:119
1478
+ msgid "The selected entry was deleted successfully!"
1479
+ msgstr ""
1480
+
1481
+ #: ../admin/wp-security-list-comment-spammer-ip.php:129
1482
+ msgid ""
1483
+ "The selected IP addresses were saved in the blacklist configuration settings."
1484
+ msgstr ""
1485
+
1486
+ #: ../admin/wp-security-list-comment-spammer-ip.php:143
1487
+ msgid ""
1488
+ "The .htaccess file was successfully modified to include the selected IP "
1489
+ "addresses."
1490
+ msgstr ""
1491
+
1492
+ #: ../admin/wp-security-list-comment-spammer-ip.php:149
1493
+ msgid ""
1494
+ "NOTE: The .htaccess file was not modified because you have disabled the "
1495
+ "\"Enable IP or User Agent Blacklisting\" check box."
1496
+ msgstr ""
1497
+
1498
+ #: ../admin/wp-security-list-comment-spammer-ip.php:150
1499
+ #, php-format
1500
+ msgid ""
1501
+ "To block these IP addresses you will need to enable the above flag in the %s "
1502
+ "menu"
1503
+ msgstr ""
1504
+
1505
+ #: ../admin/wp-security-list-locked-ip.php:115
1506
+ #: ../admin/wp-security-user-login-menu.php:439
1507
+ msgid "The selected IP ranges were unlocked successfully!"
1508
+ msgstr ""
1509
+
1510
+ #: ../admin/wp-security-list-locked-ip.php:124
1511
+ #: ../admin/wp-security-user-login-menu.php:448
1512
+ msgid "The selected IP range was unlocked successfully!"
1513
+ msgstr ""
1514
+
1515
+ #: ../admin/wp-security-maintenance-menu.php:82
1516
+ msgid "Site lockout feature settings saved!"
1517
+ msgstr ""
1518
+
1519
+ #: ../admin/wp-security-maintenance-menu.php:87
1520
+ msgid "General Visitor Lockout"
1521
+ msgstr ""
1522
+
1523
+ #: ../admin/wp-security-maintenance-menu.php:93
1524
+ msgid ""
1525
+ "This feature allows you to put your site into \"maintenance mode\" by "
1526
+ "locking down the front-end to all visitors except logged in users with super "
1527
+ "admin privileges."
1528
+ msgstr ""
1529
+
1530
+ #: ../admin/wp-security-maintenance-menu.php:94
1531
+ msgid ""
1532
+ "Locking your site down to general visitors can be useful if you are "
1533
+ "investigating some issues on your site or perhaps you might be doing some "
1534
+ "maintenance and wish to keep out all traffic for security reasons."
1535
+ msgstr ""
1536
+
1537
+ #: ../admin/wp-security-maintenance-menu.php:99
1538
+ msgid "Enable Front-end Lockout"
1539
+ msgstr ""
1540
+
1541
+ #: ../admin/wp-security-maintenance-menu.php:102
1542
+ msgid ""
1543
+ "Check this if you want all visitors except those who are logged in as "
1544
+ "administrator to be locked out of the front-end of your site."
1545
+ msgstr ""
1546
+
1547
+ #: ../admin/wp-security-maintenance-menu.php:106
1548
+ msgid "Enter a Message:"
1549
+ msgstr ""
1550
+
1551
+ #: ../admin/wp-security-maintenance-menu.php:118
1552
+ msgid ""
1553
+ "Enter a message you wish to display to visitors when your site is in "
1554
+ "maintenance mode."
1555
+ msgstr ""
1556
+
1557
+ #: ../admin/wp-security-maintenance-menu.php:125
1558
+ msgid "Save Site Lockout Settings"
1559
+ msgstr ""
1560
+
1561
+ #: ../admin/wp-security-settings-menu.php:81
1562
+ msgid "All the security features have been disabled successfully!"
1563
+ msgstr ""
1564
+
1565
+ #: ../admin/wp-security-settings-menu.php:90
1566
+ msgid "WP Security Plugin"
1567
+ msgstr ""
1568
+
1569
+ #: ../admin/wp-security-settings-menu.php:92
1570
+ msgid ""
1571
+ "Thank you for using our WordPress security plugin. There are a lot of "
1572
+ "security features in this plugin."
1573
+ msgstr ""
1574
+
1575
+ #: ../admin/wp-security-settings-menu.php:93
1576
+ msgid ""
1577
+ "Go through each menu items and enable the security options to add more "
1578
+ "security to your site."
1579
+ msgstr ""
1580
+
1581
+ #: ../admin/wp-security-settings-menu.php:94
1582
+ msgid ""
1583
+ "It is a good practice to take a backup of your .htaccess file, database and "
1584
+ "wp-config.php file before activating the security features. This plugin has "
1585
+ "options that you can use to backup those resources easily."
1586
+ msgstr ""
1587
+
1588
+ #: ../admin/wp-security-settings-menu.php:97
1589
+ msgid "Backup your database"
1590
+ msgstr ""
1591
+
1592
+ #: ../admin/wp-security-settings-menu.php:98
1593
+ msgid "Backup .htaccess file"
1594
+ msgstr ""
1595
+
1596
+ #: ../admin/wp-security-settings-menu.php:99
1597
+ msgid "Backup wp-config.php file"
1598
+ msgstr ""
1599
+
1600
+ #: ../admin/wp-security-settings-menu.php:105
1601
+ msgid "Disable Security Features"
1602
+ msgstr ""
1603
+
1604
+ #: ../admin/wp-security-settings-menu.php:111
1605
+ msgid ""
1606
+ "If you think that some plugin functionality on your site is broken due to a "
1607
+ "security feature you enabled in this plugin, then use the following option "
1608
+ "to turn off all the security features of this plugin."
1609
+ msgstr ""
1610
+
1611
+ #: ../admin/wp-security-settings-menu.php:115
1612
+ msgid "Disable All Security Features"
1613
+ msgstr ""
1614
+
1615
+ #: ../admin/wp-security-settings-menu.php:143
1616
+ msgid ""
1617
+ "Your .htaccess file was successfully backed up! Right click on the following "
1618
+ "file name and save the backup to your computer."
1619
+ msgstr ""
1620
+
1621
+ #: ../admin/wp-security-settings-menu.php:145
1622
+ msgid "Your .htaccess File: "
1623
+ msgstr ""
1624
+
1625
+ #: ../admin/wp-security-settings-menu.php:153
1626
+ msgid ""
1627
+ "htaccess file rename failed during backup. Please check your root directory "
1628
+ "for the backup file using FTP."
1629
+ msgstr ""
1630
+
1631
+ #: ../admin/wp-security-settings-menu.php:159
1632
+ msgid "htaccess backup failed."
1633
+ msgstr ""
1634
+
1635
+ #: ../admin/wp-security-settings-menu.php:174
1636
+ msgid "Please choose a .htaccess to restore from."
1637
+ msgstr ""
1638
+
1639
+ #: ../admin/wp-security-settings-menu.php:190
1640
+ msgid ""
1641
+ "htaccess file restore failed. Please attempt to restore the .htaccess "
1642
+ "manually using FTP."
1643
+ msgstr ""
1644
+
1645
+ #: ../admin/wp-security-settings-menu.php:194
1646
+ msgid "Your .htaccess file has successfully been restored!"
1647
+ msgstr ""
1648
+
1649
+ #: ../admin/wp-security-settings-menu.php:200
1650
+ msgid ""
1651
+ "htaccess Restore operation failed! Please check the contents of the file you "
1652
+ "are trying to restore from."
1653
+ msgstr ""
1654
+
1655
+ #: ../admin/wp-security-settings-menu.php:206
1656
+ msgid ".htaccess File Operations"
1657
+ msgstr ""
1658
+
1659
+ #: ../admin/wp-security-settings-menu.php:209
1660
+ msgid ""
1661
+ "Your \".htaccess\" file is a key component of your website's security and it "
1662
+ "can be modified to implement various levels of protection mechanisms."
1663
+ msgstr ""
1664
+
1665
+ #: ../admin/wp-security-settings-menu.php:210
1666
+ msgid ""
1667
+ "This feature allows you to backup and save your currently active .htaccess "
1668
+ "file should you need to re-use the the backed up file in the future."
1669
+ msgstr ""
1670
+
1671
+ #: ../admin/wp-security-settings-menu.php:211
1672
+ msgid ""
1673
+ "You can also restore your site's .htaccess settings using a backed up ."
1674
+ "htaccess file."
1675
+ msgstr ""
1676
+
1677
+ #: ../admin/wp-security-settings-menu.php:217
1678
+ msgid "Save the current .htaccess file"
1679
+ msgstr ""
1680
+
1681
+ #: ../admin/wp-security-settings-menu.php:221
1682
+ msgid ""
1683
+ "Click the button below to backup and save the currently active .htaccess "
1684
+ "file."
1685
+ msgstr ""
1686
+
1687
+ #: ../admin/wp-security-settings-menu.php:222
1688
+ msgid "Backup .htaccess File"
1689
+ msgstr ""
1690
+
1691
+ #: ../admin/wp-security-settings-menu.php:226
1692
+ msgid "Restore from a backed up .htaccess file"
1693
+ msgstr ""
1694
+
1695
+ #: ../admin/wp-security-settings-menu.php:232
1696
+ msgid ".htaccess file to restore from"
1697
+ msgstr ""
1698
+
1699
+ #: ../admin/wp-security-settings-menu.php:238
1700
+ msgid ""
1701
+ "After selecting your file, click the button below to restore your site using "
1702
+ "the backed up htaccess file (htaccess_backup.txt)."
1703
+ msgstr ""
1704
+
1705
+ #: ../admin/wp-security-settings-menu.php:244
1706
+ msgid "Restore .htaccess File"
1707
+ msgstr ""
1708
+
1709
+ #: ../admin/wp-security-settings-menu.php:248
1710
+ msgid "View Contents of the currently active .htaccess file"
1711
+ msgstr ""
1712
+
1713
+ #: ../admin/wp-security-settings-menu.php:282
1714
+ msgid ""
1715
+ "Your wp-config.php file was successfully backed up! Right click on the "
1716
+ "following file name and save the backup to your computer."
1717
+ msgstr ""
1718
+
1719
+ #: ../admin/wp-security-settings-menu.php:284
1720
+ msgid "Your wp-config.php File: "
1721
+ msgstr ""
1722
+
1723
+ #: ../admin/wp-security-settings-menu.php:292
1724
+ msgid ""
1725
+ "wp-config.php file rename failed during backup. Please check your root "
1726
+ "directory for the backup file using FTP."
1727
+ msgstr ""
1728
+
1729
+ #: ../admin/wp-security-settings-menu.php:298
1730
+ msgid "wp-config.php backup failed."
1731
+ msgstr ""
1732
+
1733
+ #: ../admin/wp-security-settings-menu.php:313
1734
+ msgid "Please choose a wp-config.php file to restore from."
1735
+ msgstr ""
1736
+
1737
+ #: ../admin/wp-security-settings-menu.php:329
1738
+ msgid ""
1739
+ "wp-config.php file restore failed. Please attempt to restore this file "
1740
+ "manually using FTP."
1741
+ msgstr ""
1742
+
1743
+ #: ../admin/wp-security-settings-menu.php:333
1744
+ msgid "Your wp-config.php file has successfully been restored!"
1745
+ msgstr ""
1746
+
1747
+ #: ../admin/wp-security-settings-menu.php:339
1748
+ msgid ""
1749
+ "wp-config.php Restore operation failed! Please check the contents of the "
1750
+ "file you are trying to restore from."
1751
+ msgstr ""
1752
+
1753
+ #: ../admin/wp-security-settings-menu.php:345
1754
+ msgid "wp-config.php File Operations"
1755
+ msgstr ""
1756
+
1757
+ #: ../admin/wp-security-settings-menu.php:348
1758
+ msgid ""
1759
+ "Your \"wp-config.php\" file is one of the most important in your WordPress "
1760
+ "installation. It is a primary configuration file and contains crucial things "
1761
+ "such as details of your database and other critical components."
1762
+ msgstr ""
1763
+
1764
+ #: ../admin/wp-security-settings-menu.php:349
1765
+ msgid ""
1766
+ "This feature allows you to backup and save your currently active wp-config."
1767
+ "php file should you need to re-use the the backed up file in the future."
1768
+ msgstr ""
1769
+
1770
+ #: ../admin/wp-security-settings-menu.php:350
1771
+ msgid ""
1772
+ "You can also restore your site's wp-config.php settings using a backed up wp-"
1773
+ "config.php file."
1774
+ msgstr ""
1775
+
1776
+ #: ../admin/wp-security-settings-menu.php:356
1777
+ msgid "Save the current wp-config.php file"
1778
+ msgstr ""
1779
+
1780
+ #: ../admin/wp-security-settings-menu.php:360
1781
+ msgid ""
1782
+ "Click the button below to backup and save the currently active wp-config.php "
1783
+ "file."
1784
+ msgstr ""
1785
+
1786
+ #: ../admin/wp-security-settings-menu.php:361
1787
+ msgid "Backup wp-config.php File"
1788
+ msgstr ""
1789
+
1790
+ #: ../admin/wp-security-settings-menu.php:365
1791
+ msgid "Restore from a backed up wp-config file"
1792
+ msgstr ""
1793
+
1794
+ #: ../admin/wp-security-settings-menu.php:371
1795
+ msgid "wp-config file to restore from"
1796
+ msgstr ""
1797
+
1798
+ #: ../admin/wp-security-settings-menu.php:377
1799
+ msgid ""
1800
+ "After selecting your file click the button below to restore your site using "
1801
+ "the backed up wp-config file (wp-config.php.backup.txt)."
1802
+ msgstr ""
1803
+
1804
+ #: ../admin/wp-security-settings-menu.php:383
1805
+ msgid "Restore wp-config File"
1806
+ msgstr ""
1807
+
1808
+ #: ../admin/wp-security-settings-menu.php:387
1809
+ msgid "View Contents of the currently active wp-config.php file"
1810
+ msgstr ""
1811
+
1812
+ #: ../admin/wp-security-settings-menu.php:421
1813
+ msgid "WP Generator Meta Tag"
1814
+ msgstr ""
1815
+
1816
+ #: ../admin/wp-security-settings-menu.php:424
1817
+ msgid ""
1818
+ "Wordpress generator automatically adds some meta information inside the "
1819
+ "\"head\" tags of every page on your site's front end. Below is an example of "
1820
+ "this:"
1821
+ msgstr ""
1822
+
1823
+ #: ../admin/wp-security-settings-menu.php:426
1824
+ msgid ""
1825
+ "The above meta information shows which version of WordPress your site is "
1826
+ "currently running and thus can help hackers or crawlers scan your site to "
1827
+ "see if you have an older version of WordPress or one with a known exploit."
1828
+ msgstr ""
1829
+
1830
+ #: ../admin/wp-security-settings-menu.php:427
1831
+ msgid ""
1832
+ "This feature will allow you to remove the WP generator meta info from your "
1833
+ "site's pages."
1834
+ msgstr ""
1835
+
1836
+ #: ../admin/wp-security-settings-menu.php:433
1837
+ msgid "WP Generator Meta Info"
1838
+ msgstr ""
1839
+
1840
+ #: ../admin/wp-security-settings-menu.php:445
1841
+ msgid "Remove WP Generator Meta Info"
1842
+ msgstr ""
1843
+
1844
+ #: ../admin/wp-security-settings-menu.php:448
1845
+ msgid ""
1846
+ "Check this if you want to remove the meta info produced by WP Generator from "
1847
+ "all pages"
1848
+ msgstr ""
1849
+
1850
+ #: ../admin/wp-security-user-accounts-menu.php:79
1851
+ msgid "Admin User Security"
1852
+ msgstr ""
1853
+
1854
+ #: ../admin/wp-security-user-accounts-menu.php:82
1855
+ msgid ""
1856
+ "By default, WordPress sets the administrator username to \"admin\" at "
1857
+ "installation time."
1858
+ msgstr ""
1859
+
1860
+ #: ../admin/wp-security-user-accounts-menu.php:83
1861
+ msgid ""
1862
+ "A lot of hackers try to take advantage of this information by attempting "
1863
+ "\"Brute Force Login Attacks\" where they repeatedly try to guess the "
1864
+ "password by using \"admin\" for username."
1865
+ msgstr ""
1866
+
1867
+ #: ../admin/wp-security-user-accounts-menu.php:84
1868
+ msgid ""
1869
+ "From a security perspective, changing the default \"admin\" user name is one "
1870
+ "of the first and smartest things you should do on your site."
1871
+ msgstr ""
1872
+
1873
+ #: ../admin/wp-security-user-accounts-menu.php:85
1874
+ msgid ""
1875
+ "This feature will allow you to change your default \"admin\" user name to a "
1876
+ "more secure name of your choosing."
1877
+ msgstr ""
1878
+
1879
+ #: ../admin/wp-security-user-accounts-menu.php:92
1880
+ msgid "List of Administrator Accounts"
1881
+ msgstr ""
1882
+
1883
+ #: ../admin/wp-security-user-accounts-menu.php:102
1884
+ msgid "Change Admin Username"
1885
+ msgstr ""
1886
+
1887
+ #: ../admin/wp-security-user-accounts-menu.php:110
1888
+ msgid ""
1889
+ "Your site currently has an account which uses the default \"admin\" "
1890
+ "username. \n"
1891
+ " It is highly recommended that you change this name to "
1892
+ "something else. \n"
1893
+ " Use the following field to change the admin username."
1894
+ msgstr ""
1895
+
1896
+ #: ../admin/wp-security-user-accounts-menu.php:118
1897
+ msgid "New Admin Username"
1898
+ msgstr ""
1899
+
1900
+ #: ../admin/wp-security-user-accounts-menu.php:120
1901
+ msgid "Choose a new username for admin."
1902
+ msgstr ""
1903
+
1904
+ #: ../admin/wp-security-user-accounts-menu.php:124
1905
+ msgid "Change Username"
1906
+ msgstr ""
1907
+
1908
+ #: ../admin/wp-security-user-accounts-menu.php:126
1909
+ msgid ""
1910
+ "NOTE: If you are currently logged in as \"admin\" you will be automatically "
1911
+ "logged out after changing your username and will be required to log back in."
1912
+ msgstr ""
1913
+
1914
+ #: ../admin/wp-security-user-accounts-menu.php:133
1915
+ msgid "No action required! "
1916
+ msgstr ""
1917
+
1918
+ #: ../admin/wp-security-user-accounts-menu.php:135
1919
+ msgid ""
1920
+ "Your site does not have any account which uses the default \"admin\" "
1921
+ "username. "
1922
+ msgstr ""
1923
+
1924
+ #: ../admin/wp-security-user-accounts-menu.php:136
1925
+ msgid "This is good security practice."
1926
+ msgstr ""
1927
+
1928
+ #: ../admin/wp-security-user-accounts-menu.php:148
1929
+ msgid "Display Name Security"
1930
+ msgstr ""
1931
+
1932
+ #: ../admin/wp-security-user-accounts-menu.php:151
1933
+ msgid ""
1934
+ "When you submit a post or answer a comment, WordPress will usually display "
1935
+ "your \"nickname\"."
1936
+ msgstr ""
1937
+
1938
+ #: ../admin/wp-security-user-accounts-menu.php:152
1939
+ msgid ""
1940
+ "By default the nickname is set to the login (or user) name of your account."
1941
+ msgstr ""
1942
+
1943
+ #: ../admin/wp-security-user-accounts-menu.php:153
1944
+ msgid ""
1945
+ "From a security perspective, leaving your nickname the same as your user "
1946
+ "name is bad practice because it gives a hacker at least half of your "
1947
+ "account's login credentials."
1948
+ msgstr ""
1949
+
1950
+ #: ../admin/wp-security-user-accounts-menu.php:154
1951
+ msgid ""
1952
+ "Therefore to further tighten your site's security you are advised to change "
1953
+ "your <strong>nickname</strong> and <strong>Display name</strong> to be "
1954
+ "different from your <strong>Username</strong>."
1955
+ msgstr ""
1956
+
1957
+ #: ../admin/wp-security-user-accounts-menu.php:160
1958
+ msgid "Modify Accounts With Identical Login Name & Display Name"
1959
+ msgstr ""
1960
+
1961
+ #: ../admin/wp-security-user-accounts-menu.php:169
1962
+ msgid ""
1963
+ "Your site currently has the following accounts which have an identical login "
1964
+ "name and display name."
1965
+ msgstr ""
1966
+
1967
+ #: ../admin/wp-security-user-accounts-menu.php:170
1968
+ msgid "Click on the link to edit the settings of that particular user account"
1969
+ msgstr ""
1970
+
1971
+ #: ../admin/wp-security-user-accounts-menu.php:185
1972
+ msgid "No action required."
1973
+ msgstr ""
1974
+
1975
+ #: ../admin/wp-security-user-accounts-menu.php:186
1976
+ msgid ""
1977
+ "Your site does not have a user account where the display name is identical "
1978
+ "to the username."
1979
+ msgstr ""
1980
+
1981
+ #: ../admin/wp-security-user-accounts-menu.php:197
1982
+ msgid "Password Tool"
1983
+ msgstr ""
1984
+
1985
+ #: ../admin/wp-security-user-accounts-menu.php:200
1986
+ msgid ""
1987
+ "Poor password selection is one of the most common weak points of many sites "
1988
+ "and is usually the first thing a hacker will try to exploit when attempting "
1989
+ "to break into your site."
1990
+ msgstr ""
1991
+
1992
+ #: ../admin/wp-security-user-accounts-menu.php:201
1993
+ msgid ""
1994
+ "Many people fall into the trap of using a simple word or series of numbers "
1995
+ "as their password. Such a predictable and simple password would take a "
1996
+ "competent hacker merely minutes to guess your password by using a simple "
1997
+ "script which cycles through the easy and most common combinations."
1998
+ msgstr ""
1999
+
2000
+ #: ../admin/wp-security-user-accounts-menu.php:202
2001
+ msgid ""
2002
+ "The longer and more complex your password is the harder it is for hackers to "
2003
+ "\"crack\" because more complex passwords require much greater computing "
2004
+ "power and time."
2005
+ msgstr ""
2006
+
2007
+ #: ../admin/wp-security-user-accounts-menu.php:203
2008
+ msgid ""
2009
+ "This section contains a useful password strength tool which you can use to "
2010
+ "check whether your password is sufficiently strong enough."
2011
+ msgstr ""
2012
+
2013
+ #: ../admin/wp-security-user-accounts-menu.php:208
2014
+ msgid "Password Strength Tool"
2015
+ msgstr ""
2016
+
2017
+ #: ../admin/wp-security-user-accounts-menu.php:213
2018
+ msgid "Start typing a password."
2019
+ msgstr ""
2020
+
2021
+ #: ../admin/wp-security-user-accounts-menu.php:238
2022
+ msgid "Nonce check failed on admin username change operation!"
2023
+ msgstr ""
2024
+
2025
+ #: ../admin/wp-security-user-accounts-menu.php:245
2026
+ msgid "Username "
2027
+ msgstr ""
2028
+
2029
+ #: ../admin/wp-security-user-accounts-menu.php:245
2030
+ msgid " already exists. Please enter another value. "
2031
+ msgstr ""
2032
+
2033
+ #: ../admin/wp-security-user-accounts-menu.php:261
2034
+ msgid "The database update operation of the user account failed!"
2035
+ msgstr ""
2036
+
2037
+ #: ../admin/wp-security-user-accounts-menu.php:288
2038
+ msgid "You entered an invalid username. Please enter another value. "
2039
+ msgstr ""
2040
+
2041
+ #: ../admin/wp-security-user-accounts-menu.php:292
2042
+ msgid "Please enter a value for your username. "
2043
+ msgstr ""
2044
+
2045
+ #: ../admin/wp-security-user-accounts-menu.php:299
2046
+ msgid "Username Successfully Changed!"
2047
+ msgstr ""
2048
+
2049
+ #: ../admin/wp-security-user-accounts-menu.php:319
2050
+ msgid "Account Login Name"
2051
+ msgstr ""
2052
+
2053
+ #: ../admin/wp-security-user-login-menu.php:88
2054
+ msgid ""
2055
+ "You entered a non numeric value for the max login attempts field. It has "
2056
+ "been set to the default value."
2057
+ msgstr ""
2058
+
2059
+ #: ../admin/wp-security-user-login-menu.php:95
2060
+ msgid ""
2061
+ "You entered a non numeric value for the login retry time period field. It "
2062
+ "has been set to the default value."
2063
+ msgstr ""
2064
+
2065
+ #: ../admin/wp-security-user-login-menu.php:102
2066
+ msgid ""
2067
+ "You entered a non numeric value for the lockout time length field. It has "
2068
+ "been set to the default value."
2069
+ msgstr ""
2070
+
2071
+ #: ../admin/wp-security-user-login-menu.php:146
2072
+ msgid "Login Lockdown Configuration"
2073
+ msgstr ""
2074
+
2075
+ #: ../admin/wp-security-user-login-menu.php:150
2076
+ msgid "One of the ways hackers try to compromise sites is via a "
2077
+ msgstr ""
2078
+
2079
+ #: ../admin/wp-security-user-login-menu.php:150
2080
+ msgid "Brute Force Login Attack"
2081
+ msgstr ""
2082
+
2083
+ #: ../admin/wp-security-user-login-menu.php:151
2084
+ msgid ""
2085
+ "This is where attackers use repeated login attempts until they guess the "
2086
+ "password."
2087
+ msgstr ""
2088
+
2089
+ #: ../admin/wp-security-user-login-menu.php:152
2090
+ msgid ""
2091
+ "Apart from choosing strong passwords, monitoring and blocking IP addresses "
2092
+ "which are involved in repeated login failures in a short period of time is a "
2093
+ "very effective way to stop these types of attacks."
2094
+ msgstr ""
2095
+
2096
+ #: ../admin/wp-security-user-login-menu.php:153
2097
+ #, php-format
2098
+ msgid ""
2099
+ "You may also want to checkout our %s feature for another secure way to "
2100
+ "protect against these types of attacks."
2101
+ msgstr ""
2102
+
2103
+ #: ../admin/wp-security-user-login-menu.php:158
2104
+ msgid "Login Lockdown Options"
2105
+ msgstr ""
2106
+
2107
+ #: ../admin/wp-security-user-login-menu.php:170
2108
+ msgid "Enable Login Lockdown Feature"
2109
+ msgstr ""
2110
+
2111
+ #: ../admin/wp-security-user-login-menu.php:173
2112
+ msgid ""
2113
+ "Check this if you want to enable the login lockdown feature and apply the "
2114
+ "settings below"
2115
+ msgstr ""
2116
+
2117
+ #: ../admin/wp-security-user-login-menu.php:177
2118
+ msgid "Max Login Attempts"
2119
+ msgstr ""
2120
+
2121
+ #: ../admin/wp-security-user-login-menu.php:179
2122
+ msgid ""
2123
+ "Set the value for the maximum login retries before IP address is locked out"
2124
+ msgstr ""
2125
+
2126
+ #: ../admin/wp-security-user-login-menu.php:183
2127
+ msgid "Login Retry Time Period (min)"
2128
+ msgstr ""
2129
+
2130
+ #: ../admin/wp-security-user-login-menu.php:185
2131
+ msgid ""
2132
+ "If the maximum number of failed login attempts for a particular IP address "
2133
+ "occur within this time period the plugin will lock out that address"
2134
+ msgstr ""
2135
+
2136
+ #: ../admin/wp-security-user-login-menu.php:189
2137
+ msgid "Time Length of Lockout (min)"
2138
+ msgstr ""
2139
+
2140
+ #: ../admin/wp-security-user-login-menu.php:191
2141
+ msgid ""
2142
+ "Set the length of time for which a particular IP address will be prevented "
2143
+ "from logging in"
2144
+ msgstr ""
2145
+
2146
+ #: ../admin/wp-security-user-login-menu.php:195
2147
+ msgid "Display Generic Error Message"
2148
+ msgstr ""
2149
+
2150
+ #: ../admin/wp-security-user-login-menu.php:198
2151
+ msgid ""
2152
+ "Check this if you want to show a generic error message when a login attempt "
2153
+ "fails"
2154
+ msgstr ""
2155
+
2156
+ #: ../admin/wp-security-user-login-menu.php:202
2157
+ msgid "Notify By Email"
2158
+ msgstr ""
2159
+
2160
+ #: ../admin/wp-security-user-login-menu.php:205
2161
+ msgid ""
2162
+ "Check this if you want to receive an email when someone has been locked out "
2163
+ "due to maximum failed login attempts"
2164
+ msgstr ""
2165
+
2166
+ #: ../admin/wp-security-user-login-menu.php:215
2167
+ msgid "Currently Locked Out IP Address Ranges"
2168
+ msgstr ""
2169
+
2170
+ #: ../admin/wp-security-user-login-menu.php:242
2171
+ msgid "Nonce check failed for delete all failed login records operation!"
2172
+ msgstr ""
2173
+
2174
+ #: ../admin/wp-security-user-login-menu.php:251
2175
+ msgid "User Login Feature - Delete all failed login records operation failed!"
2176
+ msgstr ""
2177
+
2178
+ #: ../admin/wp-security-user-login-menu.php:255
2179
+ msgid "All records from the Failed Logins table were deleted successfully!"
2180
+ msgstr ""
2181
+
2182
+ #: ../admin/wp-security-user-login-menu.php:270
2183
+ msgid "This tab displays the failed login attempts for your site."
2184
+ msgstr ""
2185
+
2186
+ #: ../admin/wp-security-user-login-menu.php:271
2187
+ msgid ""
2188
+ "The information below can be handy if you need to do security investigations "
2189
+ "because it will show you the IP range, username and ID (if applicable) and "
2190
+ "the time/date of the failed login attempt."
2191
+ msgstr ""
2192
+
2193
+ #: ../admin/wp-security-user-login-menu.php:276
2194
+ msgid "Failed Login Records"
2195
+ msgstr ""
2196
+
2197
+ #: ../admin/wp-security-user-login-menu.php:292
2198
+ #: ../admin/wp-security-user-login-menu.php:301
2199
+ msgid "Delete All Failed Login Records"
2200
+ msgstr ""
2201
+
2202
+ #: ../admin/wp-security-user-login-menu.php:298
2203
+ msgid ""
2204
+ "Click this button if you wish to delete all failed login records in one go."
2205
+ msgstr ""
2206
+
2207
+ #: ../admin/wp-security-user-login-menu.php:326
2208
+ msgid ""
2209
+ "You entered a non numeric value for the logout time period field. It has "
2210
+ "been set to the default value."
2211
+ msgstr ""
2212
+
2213
+ #: ../admin/wp-security-user-login-menu.php:348
2214
+ msgid ""
2215
+ "Setting an expiry period for your WP administration session is a simple way "
2216
+ "to protect against unauthorized access to your site from your computer."
2217
+ msgstr ""
2218
+
2219
+ #: ../admin/wp-security-user-login-menu.php:349
2220
+ msgid ""
2221
+ "This feature allows you to specify a time period in minutes after which the "
2222
+ "admin session will expire and the user will be forced to log back in."
2223
+ msgstr ""
2224
+
2225
+ #: ../admin/wp-security-user-login-menu.php:354
2226
+ msgid "Force User Logout Options"
2227
+ msgstr ""
2228
+
2229
+ #: ../admin/wp-security-user-login-menu.php:366
2230
+ msgid "Enable Force WP User Logout"
2231
+ msgstr ""
2232
+
2233
+ #: ../admin/wp-security-user-login-menu.php:369
2234
+ msgid ""
2235
+ "Check this if you want to force a wp user to be logged out after a "
2236
+ "configured amount of time"
2237
+ msgstr ""
2238
+
2239
+ #: ../admin/wp-security-user-login-menu.php:373
2240
+ msgid "Logout the WP User After XX Minutes"
2241
+ msgstr ""
2242
+
2243
+ #: ../admin/wp-security-user-login-menu.php:375
2244
+ msgid ""
2245
+ "(Minutes) The user will be forced to log back in after this time period has "
2246
+ "elapased."
2247
+ msgstr ""
2248
+
2249
+ #: ../admin/wp-security-user-login-menu.php:399
2250
+ msgid ""
2251
+ "This tab displays the login activity for WordPress admin accounts registered "
2252
+ "with your site."
2253
+ msgstr ""
2254
+
2255
+ #: ../admin/wp-security-user-login-menu.php:400
2256
+ msgid ""
2257
+ "The information below can be handy if you need to do security investigations "
2258
+ "because it will show you the last 50 recent login events by username, IP "
2259
+ "address and time/date."
2260
+ msgstr ""
2261
+
2262
+ #: ../admin/wp-security-user-login-menu.php:405
2263
+ msgid "Account Activity Logs"
2264
+ msgstr ""
2265
+
2266
+ #: ../admin/wp-security-user-login-menu.php:470
2267
+ msgid "The selected records were deleted successfully!"
2268
+ msgstr ""
2269
+
2270
+ #: ../admin/wp-security-user-login-menu.php:479
2271
+ msgid "The selected record was deleted successfully!"
2272
+ msgstr ""
2273
+
2274
+ #: ../admin/wp-security-whois-menu.php:68
2275
+ msgid "WHOIS Lookup Information"
2276
+ msgstr ""
2277
+
2278
+ #: ../admin/wp-security-whois-menu.php:71
2279
+ msgid ""
2280
+ "This feature allows you to look up more detailed information about an IP "
2281
+ "address or domain name by querying the WHOIS API."
2282
+ msgstr ""
2283
+
2284
+ #: ../admin/wp-security-whois-menu.php:77
2285
+ msgid "Perform a WHOIS Lookup for an IP or Domain Name"
2286
+ msgstr ""
2287
+
2288
+ #: ../admin/wp-security-whois-menu.php:84
2289
+ msgid "Enter IP Address or Domain Name"
2290
+ msgstr ""
2291
+
2292
+ #: ../admin/wp-security-whois-menu.php:86
2293
+ msgid ""
2294
+ "Enter an IP address or domain name. Example: 111.11.12.13 OR some-domain-"
2295
+ "name.com"
2296
+ msgstr ""
2297
+
2298
+ #: ../admin/wp-security-whois-menu.php:90
2299
+ msgid "Perform IP or Domain Lookup"
2300
+ msgstr ""
2301
+
2302
+ #: ../admin/wp-security-whois-menu.php:110
2303
+ msgid "WHOIS lookup successfully completed. Please see the results below:"
2304
+ msgstr ""
2305
+
2306
+ #: ../admin/wp-security-whois-menu.php:122
2307
+ msgid ""
2308
+ "You have entered an incorrectly formatted IP address or domain name. Please "
2309
+ "try again."
2310
+ msgstr ""
2311
+
2312
+ #: ../admin/general/wp-security-list-table.php:178
2313
+ msgid "No items found."
2314
+ msgstr ""
2315
+
2316
+ #: ../admin/general/wp-security-list-table.php:281
2317
+ msgid "Bulk Actions"
2318
+ msgstr ""
2319
+
2320
+ #: ../admin/general/wp-security-list-table.php:291
2321
+ msgid "Apply"
2322
+ msgstr ""
2323
+
2324
+ #: ../admin/general/wp-security-list-table.php:365
2325
+ msgid "Show all dates"
2326
+ msgstr ""
2327
+
2328
+ #: ../admin/general/wp-security-list-table.php:378
2329
+ #, php-format
2330
+ msgid "%1$s %2$d"
2331
+ msgstr ""
2332
+
2333
+ #: ../admin/general/wp-security-list-table.php:394
2334
+ msgid "List View"
2335
+ msgstr ""
2336
+
2337
+ #: ../admin/general/wp-security-list-table.php:395
2338
+ msgid "Excerpt View"
2339
+ msgstr ""
2340
+
2341
+ #: ../admin/general/wp-security-list-table.php:421
2342
+ #, php-format
2343
+ msgid "%s pending"
2344
+ msgstr ""
2345
+
2346
+ #: ../admin/general/wp-security-list-table.php:653
2347
+ msgid "Select All"
2348
+ msgstr ""
2349
+
2350
+ #: ../classes/wp-security-backup.php:110
2351
+ msgid "All In One WP Security - Site Database Backup"
2352
+ msgstr ""
2353
+
2354
+ #: ../classes/wp-security-backup.php:112
2355
+ msgid "Attached is your latest DB backup file for site URL"
2356
+ msgstr ""
2357
+
2358
+ #: ../classes/wp-security-backup.php:112
2359
+ msgid " generated on"
2360
+ msgstr ""
2361
+
2362
+ #: ../classes/wp-security-user-login.php:39
2363
+ msgid ""
2364
+ "<strong>ERROR</strong>: Login failed because your IP address has been "
2365
+ "blocked due to too many failed login attempts.\n"
2366
+ " Please contact the administrator."
2367
+ msgstr ""
2368
+
2369
+ #: ../classes/wp-security-user-login.php:48
2370
+ msgid "<strong>ERROR</strong>: The username field is empty."
2371
+ msgstr ""
2372
+
2373
+ #: ../classes/wp-security-user-login.php:52
2374
+ msgid "<strong>ERROR</strong>: The password field is empty."
2375
+ msgstr ""
2376
+
2377
+ #: ../classes/wp-security-user-login.php:64
2378
+ msgid "unknown"
2379
+ msgstr ""
2380
+
2381
+ #: ../classes/wp-security-user-login.php:69
2382
+ #: ../classes/wp-security-user-login.php:92
2383
+ msgid "<strong>ERROR</strong>: Invalid login credentials."
2384
+ msgstr ""
2385
+
2386
+ #: ../classes/wp-security-user-login.php:72
2387
+ msgid "<strong>ERROR</strong>: Invalid username."
2388
+ msgstr ""
2389
+
2390
+ #: ../classes/wp-security-user-login.php:95
2391
+ #, php-format
2392
+ msgid ""
2393
+ "<strong>ERROR</strong>: Incorrect password. <a href=\"%s\" title=\"Password "
2394
+ "Lost and Found\">Lost your password</a>?"
2395
+ msgstr ""
2396
+
2397
+ #: ../classes/wp-security-user-login.php:217
2398
+ msgid "Site Lockout Notification"
2399
+ msgstr ""
2400
+
2401
+ #: ../classes/wp-security-user-login.php:218
2402
+ msgid ""
2403
+ "A lockdown event has occurred due to too many failed login attempts with the "
2404
+ "following user details"
2405
+ msgstr ""
2406
+
2407
+ #: ../classes/wp-security-user-login.php:219
2408
+ msgid "Username: "
2409
+ msgstr ""
2410
+
2411
+ #: ../classes/wp-security-user-login.php:220
2412
+ msgid "IP Range: "
2413
+ msgstr ""
2414
+
2415
+ #: ../classes/wp-security-user-login.php:221
2416
+ msgid ""
2417
+ "Log into your site's WordPress administration panel to see the duration of "
2418
+ "the lockout or to unlock the user."
2419
+ msgstr ""
2420
+
2421
+ #: ../classes/wp-security-user-login.php:336
2422
+ #, php-format
2423
+ msgid ""
2424
+ "Your session has expired because it has been over %d minutes since your last "
2425
+ "login."
2426
+ msgstr ""
2427
+
2428
+ #: ../classes/wp-security-user-login.php:337
2429
+ #: ../classes/wp-security-user-login.php:341
2430
+ msgid "Please log back in to continue."
2431
+ msgstr ""
2432
+
2433
+ #: ../classes/wp-security-user-login.php:340
2434
+ msgid "You were logged out because you just changed the \"admin\" username."
2435
+ msgstr ""
2436
+
2437
+ #: ../classes/wp-security-utility-ip-address.php:79
2438
+ #: ../classes/wp-security-utility-ip-address.php:98
2439
+ #: ../classes/wp-security-utility-ip-address.php:113
2440
+ #: ../classes/wp-security-utility-ip-address.php:128
2441
+ msgid " is not a valid ip address format."
2442
+ msgstr ""
2443
+
2444
+ #: ../classes/wp-security-utility-ip-address.php:136
2445
+ msgid "You cannot ban your own IP address: "
2446
+ msgstr ""
readme.txt CHANGED
@@ -4,7 +4,7 @@ Donate link: http://www.tipsandtricks-hq.com
4
  Tags: security, secure, Anti Virus, antivirus, virus, firewall, login, lockdown, htaccess, hacking, ban hacker, malware, vulnerability, protect, phishing, database, backup, plugin, sql injection, ssl, restrict
5
  Requires at least: 3.5
6
  Tested up to: 3.6
7
- Stable tag: 1.8
8
  License: GPLv3
9
 
10
  A comprehensive, user-friendly, all in one WordPress security and firewall plugin for your site.
@@ -79,6 +79,7 @@ So these firewall rules will stop malicious script(s) before it gets a chance to
79
  * Protect against Cross Site Scripting (XSS) by activating the comprehensive advanced character string filter.
80
  * Instantly block Brute Force Login Attacks via our special Cookie-Based Brute Force Login Prevention feature. This firewall functionality will block all login attempts from people
81
  or malicious bots who do not have a special cookie in their browser. You (the site admin) will know how to set this special cookie and be able to log into your site.
 
82
 
83
  = WhoIs Lookup =
84
  * Perform a WhoIs lookup of a suspicious host or IP address and get full details.
@@ -126,6 +127,14 @@ None
126
 
127
  == Changelog ==
128
 
 
 
 
 
 
 
 
 
129
  = 1.8 =
130
  - Moved the front end site lockout feature to a new menu called "Maintenance".
131
  - Added a feature in the front-end lockout feature to allow people to specify their own message which will be displayed on the front-end to visitors who try to access the site when it is in lock out state.
4
  Tags: security, secure, Anti Virus, antivirus, virus, firewall, login, lockdown, htaccess, hacking, ban hacker, malware, vulnerability, protect, phishing, database, backup, plugin, sql injection, ssl, restrict
5
  Requires at least: 3.5
6
  Tested up to: 3.6
7
+ Stable tag: 1.9
8
  License: GPLv3
9
 
10
  A comprehensive, user-friendly, all in one WordPress security and firewall plugin for your site.
79
  * Protect against Cross Site Scripting (XSS) by activating the comprehensive advanced character string filter.
80
  * Instantly block Brute Force Login Attacks via our special Cookie-Based Brute Force Login Prevention feature. This firewall functionality will block all login attempts from people
81
  or malicious bots who do not have a special cookie in their browser. You (the site admin) will know how to set this special cookie and be able to log into your site.
82
+ * WordPress PingBack Vulnerability Protection feature. This firewall feature allows the user to prohibit access to the xmlrpc.php file in order to protect against certain vulnerabilities in the pingback functionality. This is also helpful to block bots from constantly accessing the xmlrpc.php file and wasting your server resource.
83
 
84
  = WhoIs Lookup =
85
  * Perform a WhoIs lookup of a suspicious host or IP address and get full details.
127
 
128
  == Changelog ==
129
 
130
+ = 1.9 =
131
+ - Added new WordPress PingBack Vulnerability Protection feature. This allows the user to prohibit access to the xmlrpc.php file in order to protect against certain vulnerabilities in the pingback functionality.
132
+ - Added a configuration item in the brute force login prevention feature to allow ajax functionality to work properly when this feature is enabled.
133
+ - Added a POT file for language translations.
134
+ - Made the DB Prefix feature more robust by adding a check to ensure that plugin can write to the wp-config.php file. This will prevent user from losing access to their site in cases where the system changed the prefix but not the entry in the wp-config.php file.
135
+ - Tightened the data validation for the cookie based brute force login feature to ensure that the user must enter a secret word which consists of alphanumeric characters.
136
+ - Added edit links to the user account list in the "User Acounts" menu.
137
+
138
  = 1.8 =
139
  - Moved the front end site lockout feature to a new menu called "Maintenance".
140
  - Added a feature in the front-end lockout feature to allow people to specify their own message which will be displayed on the front-end to visitors who try to access the site when it is in lock out state.
wp-security-core.php CHANGED
@@ -3,7 +3,7 @@
3
  if (!class_exists('AIO_WP_Security')){
4
 
5
  class AIO_WP_Security{
6
- var $version = '1.8';
7
  var $db_version = '1.2';
8
  var $plugin_url;
9
  var $plugin_path;
3
  if (!class_exists('AIO_WP_Security')){
4
 
5
  class AIO_WP_Security{
6
+ var $version = '1.9';
7
  var $db_version = '1.2';
8
  var $plugin_url;
9
  var $plugin_path;
wp-security.php CHANGED
@@ -1,7 +1,7 @@
1
  <?php
2
  /*
3
  Plugin Name: All In One WP Security
4
- Version: v1.8
5
  Plugin URI: http://www.tipsandtricks-hq.com/
6
  Author: Tips and Tricks HQ, Peter, Ruhul Amin
7
  Author URI: http://www.tipsandtricks-hq.com/
1
  <?php
2
  /*
3
  Plugin Name: All In One WP Security
4
+ Version: v1.9
5
  Plugin URI: http://www.tipsandtricks-hq.com/
6
  Author: Tips and Tricks HQ, Peter, Ruhul Amin
7
  Author URI: http://www.tipsandtricks-hq.com/