Lubuntu/lubuntu.me
8
0
Fork 0
mirror of https://github.com/lubuntu-team/lubuntu.me.git synced 2025-02-23 08:11:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
lubuntu.me/plugins/all-in-one-wp-security-and-firewall/languages/all-in-one-wp-security-and-firewall.pot
RedWolf 4828353fc7 update plugins and theme
2018-01-26 15:50:15 +01:00

5612 lines
156 KiB
Plaintext
Raw Blame History

msgid ""
msgstr ""
"Project-Id-Version: All In One WP Security\n"
"POT-Creation-Date: 2017-01-17 12:25+1000\n"
"PO-Revision-Date: 2017-01-17 12:25+1000\n"
"Last-Translator: \n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.5.7\n"
"X-Poedit-KeywordsList: __;_e\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-SearchPath-0: .\n"
#: admin/wp-security-admin-init.php:203
msgid "WP Security"
msgstr ""
#: admin/wp-security-admin-init.php:204
#: admin/wp-security-dashboard-menu.php:25
#: admin/wp-security-dashboard-menu.php:61
msgid "Dashboard"
msgstr ""
#: admin/wp-security-admin-init.php:205 admin/wp-security-settings-menu.php:63
msgid "Settings"
msgstr ""
#: admin/wp-security-admin-init.php:206
#: admin/wp-security-user-accounts-menu.php:64
msgid "User Accounts"
msgstr ""
#: admin/wp-security-admin-init.php:207
#: admin/wp-security-user-login-menu.php:62
msgid "User Login"
msgstr ""
#: admin/wp-security-admin-init.php:208
#: admin/wp-security-user-registration-menu.php:57
msgid "User Registration"
msgstr ""
#: admin/wp-security-admin-init.php:209 admin/wp-security-database-menu.php:66
msgid "Database Security"
msgstr ""
#: admin/wp-security-admin-init.php:213
#: admin/wp-security-filesystem-menu.php:62
msgid "Filesystem Security"
msgstr ""
#: admin/wp-security-admin-init.php:215 admin/wp-security-whois-menu.php:55
msgid "WHOIS Lookup"
msgstr ""
#: admin/wp-security-admin-init.php:219
#: admin/wp-security-blacklist-menu.php:55
msgid "Blacklist Manager"
msgstr ""
#: admin/wp-security-admin-init.php:224 admin/wp-security-firewall-menu.php:67
msgid "Firewall"
msgstr ""
#: admin/wp-security-admin-init.php:226
#: admin/wp-security-brute-force-menu.php:69
msgid "Brute Force"
msgstr ""
#: admin/wp-security-admin-init.php:227 admin/wp-security-spam-menu.php:59
msgid "SPAM Prevention"
msgstr ""
#: admin/wp-security-admin-init.php:231 admin/wp-security-filescan-menu.php:57
msgid "Scanner"
msgstr ""
#: admin/wp-security-admin-init.php:233
#: admin/wp-security-maintenance-menu.php:55
msgid "Maintenance"
msgstr ""
#: admin/wp-security-admin-init.php:234
#: admin/wp-security-misc-options-menu.php:59
msgid "Miscellaneous"
msgstr ""
#: admin/wp-security-admin-menu.php:43
msgid "Settings successfully updated."
msgstr ""
#: admin/wp-security-admin-menu.php:50
msgid "The selected record(s) deleted successfully!"
msgstr ""
#: admin/wp-security-blacklist-menu.php:22
msgid "Ban Users"
msgstr ""
#: admin/wp-security-blacklist-menu.php:81
msgid "Nonce check failed for save blacklist settings!"
msgstr ""
#: admin/wp-security-blacklist-menu.php:136
#: admin/wp-security-brute-force-menu.php:659
#: admin/wp-security-firewall-menu.php:1039 admin/wp-security-list-404.php:218
#: admin/wp-security-list-comment-spammer-ip.php:202
#: classes/wp-security-general-init-tasks.php:224
msgid ""
"The plugin was unable to write to the .htaccess file. Please edit file "
"manually."
msgstr ""
#: admin/wp-security-blacklist-menu.php:143
msgid "Ban IPs or User Agents"
msgstr ""
#: admin/wp-security-blacklist-menu.php:146
msgid ""
"The All In One WP Security Blacklist feature gives you the option of banning "
"certain host IP addresses or ranges and also user agents."
msgstr ""
#: admin/wp-security-blacklist-menu.php:147
msgid ""
"This feature will deny total site access for users which have IP addresses "
"or user agents matching those which you have configured in the settings "
"below."
msgstr ""
#: admin/wp-security-blacklist-menu.php:148
msgid ""
"The plugin achieves this by making appropriate modifications to your ."
"htaccess file."
msgstr ""
#: admin/wp-security-blacklist-menu.php:149
msgid ""
"By blocking people via the .htaccess file your are using the most secure "
"first line of defence which denies all access to blacklisted visitors as "
"soon as they hit your hosting server."
msgstr ""
#: admin/wp-security-blacklist-menu.php:156
#: admin/wp-security-firewall-menu.php:889
#, php-format
msgid "You may also be interested in our %s."
msgstr ""
#: admin/wp-security-blacklist-menu.php:157
msgid ""
"This addon allows you to automatically block IP addresses based on their "
"country of origin."
msgstr ""
#: admin/wp-security-blacklist-menu.php:165
msgid "IP Hosts and User Agent Blacklist Settings"
msgstr ""
#: admin/wp-security-blacklist-menu.php:178
#: admin/wp-security-brute-force-menu.php:196
#, php-format
msgid ""
"This feature can lock you out of admin if it doesn't work correctly on your "
"site. You %s before activating this feature."
msgstr ""
#: admin/wp-security-blacklist-menu.php:184
msgid "Enable IP or User Agent Blacklisting"
msgstr ""
#: admin/wp-security-blacklist-menu.php:187
msgid ""
"Check this if you want to enable the banning (or blacklisting) of selected "
"IP addresses and/or user agents specified in the settings below"
msgstr ""
#: admin/wp-security-blacklist-menu.php:191
msgid "Enter IP Addresses:"
msgstr ""
#: admin/wp-security-blacklist-menu.php:195
msgid "Enter one or more IP addresses or IP ranges."
msgstr ""
#: admin/wp-security-blacklist-menu.php:196
#: admin/wp-security-blacklist-menu.php:216
#: admin/wp-security-brute-force-menu.php:375
#: admin/wp-security-brute-force-menu.php:409
#: admin/wp-security-brute-force-menu.php:432
#: admin/wp-security-brute-force-menu.php:453
#: admin/wp-security-brute-force-menu.php:716
#: admin/wp-security-filescan-menu.php:297
#: admin/wp-security-filescan-menu.php:314
#: admin/wp-security-firewall-menu.php:173
#: admin/wp-security-firewall-menu.php:203
#: admin/wp-security-firewall-menu.php:223
#: admin/wp-security-firewall-menu.php:249
#: admin/wp-security-firewall-menu.php:376
#: admin/wp-security-firewall-menu.php:406
#: admin/wp-security-firewall-menu.php:437
#: admin/wp-security-firewall-menu.php:465
#: admin/wp-security-firewall-menu.php:494
#: admin/wp-security-firewall-menu.php:593
#: admin/wp-security-firewall-menu.php:611
#: admin/wp-security-firewall-menu.php:701
#: admin/wp-security-firewall-menu.php:914
#: admin/wp-security-firewall-menu.php:937 admin/wp-security-spam-menu.php:169
#: admin/wp-security-spam-menu.php:342 admin/wp-security-spam-menu.php:384
msgid "More Info"
msgstr ""
#: admin/wp-security-blacklist-menu.php:199
#: admin/wp-security-brute-force-menu.php:719
msgid "Each IP address must be on a new line."
msgstr ""
#: admin/wp-security-blacklist-menu.php:200
msgid ""
"To specify an IP range use a wildcard \"*\" character. Acceptable ways to "
"use wildcards is shown in the examples below:"
msgstr ""
#: admin/wp-security-blacklist-menu.php:201
#: admin/wp-security-brute-force-menu.php:721
msgid "Example 1: 195.47.89.*"
msgstr ""
#: admin/wp-security-blacklist-menu.php:202
#: admin/wp-security-brute-force-menu.php:722
msgid "Example 2: 195.47.*.*"
msgstr ""
#: admin/wp-security-blacklist-menu.php:203
#: admin/wp-security-brute-force-menu.php:723
msgid "Example 3: 195.*.*.*"
msgstr ""
#: admin/wp-security-blacklist-menu.php:210
msgid "Enter User Agents:"
msgstr ""
#: admin/wp-security-blacklist-menu.php:215
msgid "Enter one or more user agent strings."
msgstr ""
#: admin/wp-security-blacklist-menu.php:219
msgid "Each user agent string must be on a new line."
msgstr ""
#: admin/wp-security-blacklist-menu.php:220
msgid "Example 1 - A single user agent string to block:"
msgstr ""
#: admin/wp-security-blacklist-menu.php:222
msgid "Example 2 - A list of more than 1 user agent strings to block"
msgstr ""
#: admin/wp-security-blacklist-menu.php:230
#: admin/wp-security-brute-force-menu.php:215
#: admin/wp-security-brute-force-menu.php:595
#: admin/wp-security-brute-force-menu.php:733
#: admin/wp-security-brute-force-menu.php:795
#: admin/wp-security-database-menu.php:355
#: admin/wp-security-filescan-menu.php:337
#: admin/wp-security-filesystem-menu.php:239
#: admin/wp-security-firewall-menu.php:779
#: admin/wp-security-firewall-menu.php:956
#: admin/wp-security-misc-options-menu.php:169
#: admin/wp-security-misc-options-menu.php:220
#: admin/wp-security-settings-menu.php:542 admin/wp-security-spam-menu.php:184
#: admin/wp-security-spam-menu.php:359 admin/wp-security-spam-menu.php:480
#: admin/wp-security-user-login-menu.php:266
#: admin/wp-security-user-login-menu.php:434
#: admin/wp-security-user-registration-menu.php:151
#: admin/wp-security-user-registration-menu.php:237
msgid "Save Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:26
#: admin/wp-security-dashboard-menu.php:430
#: admin/wp-security-dashboard-menu.php:441
msgid "Rename Login Page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:27
msgid "Cookie Based Brute Force Prevention"
msgstr ""
#: admin/wp-security-brute-force-menu.php:28
#: classes/grade-system/wp-security-feature-item-manager.php:44
msgid "Login Captcha"
msgstr ""
#: admin/wp-security-brute-force-menu.php:29
#: admin/wp-security-brute-force-menu.php:666
msgid "Login Whitelist"
msgstr ""
#: admin/wp-security-brute-force-menu.php:30
msgid "Honeypot"
msgstr ""
#: admin/wp-security-brute-force-menu.php:107
msgid "Please enter a value for your login page slug."
msgstr ""
#: admin/wp-security-brute-force-menu.php:111
msgid "You cannot use the value \"wp-admin\" for your login page slug."
msgstr ""
#: admin/wp-security-brute-force-menu.php:113
msgid "You must use alpha numeric characters for your login page slug."
msgstr ""
#: admin/wp-security-brute-force-menu.php:118
#: admin/wp-security-database-menu.php:272
#: admin/wp-security-filescan-menu.php:175
#: admin/wp-security-firewall-menu.php:846 admin/wp-security-spam-menu.php:220
#: admin/wp-security-spam-menu.php:254
#: admin/wp-security-user-login-menu.php:139
#: admin/wp-security-user-login-menu.php:387
msgid "Attention!"
msgstr ""
#: admin/wp-security-brute-force-menu.php:137
msgid ""
"Could not delete the Cookie-based directives from the .htaccess file. Please "
"check the file permissions."
msgstr ""
#: admin/wp-security-brute-force-menu.php:157
msgid ""
"An effective Brute Force prevention technique is to change the default "
"WordPress login page URL."
msgstr ""
#: admin/wp-security-brute-force-menu.php:158
msgid ""
"Normally if you wanted to login to WordPress you would type your site's home "
"URL followed by wp-login.php."
msgstr ""
#: admin/wp-security-brute-force-menu.php:159
msgid ""
"This feature allows you to change the login URL by setting your own slug and "
"renaming the last portion of the login URL which contains the <strong>wp-"
"login.php</strong> to any string that you like."
msgstr ""
#: admin/wp-security-brute-force-menu.php:160
msgid ""
"By doing this, malicious bots and hackers will not be able to access your "
"login page because they will not know the correct login page URL."
msgstr ""
#: admin/wp-security-brute-force-menu.php:162
msgid ""
"You may also be interested in the following alternative brute force "
"prevention features:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:173
msgid "Your WordPress login page URL has been renamed."
msgstr ""
#: admin/wp-security-brute-force-menu.php:174
msgid "Your current login URL is:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:176
msgid ""
"NOTE: If you already had the Cookie-Based Brute Force Prevention feature "
"active, the plugin has automatically deactivated it because only one of "
"these features can be active at any one time."
msgstr ""
#: admin/wp-security-brute-force-menu.php:183
msgid "Rename Login Page Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:197
msgid ""
"NOTE: If you are hosting your site on WPEngine or a provider which performs "
"server caching, you will need to ask the host support people to NOT cache "
"your renamed login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:202
msgid "Enable Rename Login Page Feature"
msgstr ""
#: admin/wp-security-brute-force-menu.php:205
msgid "Check this if you want to enable the rename login page feature"
msgstr ""
#: admin/wp-security-brute-force-menu.php:209
msgid "Login Page URL"
msgstr ""
#: admin/wp-security-brute-force-menu.php:211
msgid ""
"Enter a string which will represent your secure login page slug. You are "
"enouraged to choose something which is hard to guess and only you will "
"remember."
msgstr ""
#: admin/wp-security-brute-force-menu.php:244
msgid ""
"Settings have not been saved - your secret word must consist only of "
"alphanumeric characters, ie, letters and/or numbers only!"
msgstr ""
#: admin/wp-security-brute-force-menu.php:263
msgid ""
"You have successfully enabled the cookie based brute force prevention feature"
msgstr ""
#: admin/wp-security-brute-force-menu.php:264
msgid ""
"From now on you will need to log into your WP Admin using the following URL:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:266
msgid ""
"It is important that you save this URL value somewhere in case you forget "
"it, OR,"
msgstr ""
#: admin/wp-security-brute-force-menu.php:267
#, php-format
msgid "simply remember to add a \"?%s=1\" to your current site URL address."
msgstr ""
#: admin/wp-security-brute-force-menu.php:273
msgid ""
"You have successfully saved cookie based brute force prevention feature "
"settings."
msgstr ""
#: admin/wp-security-brute-force-menu.php:308
#: admin/wp-security-filesystem-menu.php:283
#: admin/wp-security-firewall-menu.php:124
#: admin/wp-security-firewall-menu.php:337
#: admin/wp-security-firewall-menu.php:558
#: admin/wp-security-firewall-menu.php:746
#: admin/wp-security-settings-menu.php:636 admin/wp-security-spam-menu.php:109
msgid ""
"Could not write to the .htaccess file. Please check the file permissions."
msgstr ""
#: admin/wp-security-brute-force-menu.php:318
msgid "Brute Force Prevention Firewall Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:323
msgid ""
"A Brute Force Attack is when a hacker tries many combinations of usernames "
"and passwords until they succeed in guessing the right combination."
msgstr ""
#: admin/wp-security-brute-force-menu.php:324
msgid ""
"Due to the fact that at any one time there may be many concurrent login "
"attempts occurring on your site via malicious automated robots, this also "
"has a negative impact on your server's memory and performance."
msgstr ""
#: admin/wp-security-brute-force-menu.php:325
msgid ""
"The features in this tab will stop the majority of Brute Force Login Attacks "
"at the .htaccess level thus providing even better protection for your WP "
"login page and also reducing the load on your server because the system does "
"not have to run PHP code to process the login attempts."
msgstr ""
#: admin/wp-security-brute-force-menu.php:332
#, php-format
msgid ""
"Even though this feature should not have any impact on your site's general "
"functionality <strong>you are strongly encouraged to take a %s of your ."
"htaccess file before proceeding</strong>."
msgstr ""
#: admin/wp-security-brute-force-menu.php:333
msgid ""
"If this feature is not used correctly, you can get locked out of your site. "
"A backed up .htaccess file will come in handy if that happens."
msgstr ""
#: admin/wp-security-brute-force-menu.php:334
#, php-format
msgid ""
"To learn more about how to use this feature please watch the following %s."
msgstr ""
#: admin/wp-security-brute-force-menu.php:347
msgid ""
"NOTE: If you already had the Rename Login Page feature active, the plugin "
"has automatically deactivated it because only one of these features can be "
"active at any one time."
msgstr ""
#: admin/wp-security-brute-force-menu.php:355
msgid "Cookie Based Brute Force Login Prevention"
msgstr ""
#: admin/wp-security-brute-force-menu.php:366
msgid ""
"This feature can lock you out of admin if it doesn't work correctly on your "
"site. You <a href=\"https://www.tipsandtricks-hq.com/wordpress-security-and-"
"firewall-plugin#advanced_features_note\" target=\"_blank\">must read this "
"message</a> before activating this feature."
msgstr ""
#: admin/wp-security-brute-force-menu.php:371
#: classes/grade-system/wp-security-feature-item-manager.php:91
msgid "Enable Brute Force Attack Prevention"
msgstr ""
#: admin/wp-security-brute-force-menu.php:374
msgid ""
"Check this if you want to protect your login page from Brute Force Attack."
msgstr ""
#: admin/wp-security-brute-force-menu.php:379
msgid ""
"This feature will deny access to your WordPress login page for all people "
"except those who have a special cookie in their browser."
msgstr ""
#: admin/wp-security-brute-force-menu.php:381
msgid "To use this feature do the following:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:383
msgid "1) Enable the checkbox."
msgstr ""
#: admin/wp-security-brute-force-menu.php:385
msgid ""
"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)."
msgstr ""
#: admin/wp-security-brute-force-menu.php:387
msgid ""
"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."
msgstr ""
#: admin/wp-security-brute-force-menu.php:389
msgid ""
"Any person trying to access your login page who does not have the special "
"cookie in their browser will be automatically blocked."
msgstr ""
#: admin/wp-security-brute-force-menu.php:396
msgid "Secret Word"
msgstr ""
#: admin/wp-security-brute-force-menu.php:398
msgid ""
"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."
msgstr ""
#: admin/wp-security-brute-force-menu.php:402
msgid "Re-direct URL"
msgstr ""
#: admin/wp-security-brute-force-menu.php:406
msgid ""
"Specify a URL to redirect a hacker to when they try to access your WordPress "
"login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:413
msgid ""
"The URL specified here can be any site's URL and does not have to be your "
"own. For example you can be as creative as you like and send hackers to the "
"CIA or NSA home page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:415
msgid ""
"This field will default to: http://127.0.0.1 if you do not enter a value."
msgstr ""
#: admin/wp-security-brute-force-menu.php:417
msgid "Useful Tip:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:419
msgid ""
"It's a good idea to not redirect attempted brute force login attempts to "
"your site because it increases the load on your server."
msgstr ""
#: admin/wp-security-brute-force-menu.php:421
msgid ""
"Redirecting a hacker or malicious bot back to \"http://127.0.0.1\" is ideal "
"because it deflects them back to their own local host and puts the load on "
"their server instead of yours."
msgstr ""
#: admin/wp-security-brute-force-menu.php:428
msgid "My Site Has Posts Or Pages Which Are Password Protected"
msgstr ""
#: admin/wp-security-brute-force-menu.php:431
msgid ""
"Check this if you are using the native WordPress password protection feature "
"for some or all of your blog posts or pages."
msgstr ""
#: admin/wp-security-brute-force-menu.php:436
msgid ""
"In the cases where you are protecting some of your posts or pages using the "
"in-built WordPress password protection feature, a few extra lines of "
"directives and exceptions need to be added to your .htacces file so that "
"people trying to access pages are not automatically blocked."
msgstr ""
#: admin/wp-security-brute-force-menu.php:438
msgid ""
"By enabling this checkbox the plugin will add the necessary rules and "
"exceptions to your .htacces file so that people trying to access these pages "
"are not automatically blocked."
msgstr ""
#: admin/wp-security-brute-force-menu.php:440
msgid "Helpful Tip:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:442
msgid ""
"If you do not use the WordPress password protection feature for your posts "
"or pages then it is highly recommended that you leave this checkbox disabled."
msgstr ""
#: admin/wp-security-brute-force-menu.php:449
msgid "My Site Has a Theme or Plugins Which Use AJAX"
msgstr ""
#: admin/wp-security-brute-force-menu.php:452
msgid "Check this if your site uses AJAX functionality."
msgstr ""
#: admin/wp-security-brute-force-menu.php:457
msgid ""
"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."
msgstr ""
#: admin/wp-security-brute-force-menu.php:459
msgid ""
"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."
msgstr ""
#: admin/wp-security-brute-force-menu.php:474
msgid "The cookie test was successful. You can now enable this feature."
msgstr ""
#: admin/wp-security-brute-force-menu.php:477
msgid "Save Feature Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:484
msgid ""
"The cookie test failed on this server. So this feature cannot be used on "
"this site."
msgstr ""
#: admin/wp-security-brute-force-menu.php:489
msgid ""
"Before using this feature you are required to perform a cookie test first. "
"This is to make sure that your browser cookie is working correctly and that "
"you won't lock yourself out."
msgstr ""
#: admin/wp-security-brute-force-menu.php:491
msgid "Perform Cookie Test"
msgstr ""
#: admin/wp-security-brute-force-menu.php:531
msgid ""
"This feature allows you to add a captcha form on the WordPress login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:532
msgid ""
"Users who attempt to login will also need to enter the answer to a simple "
"mathematical question - if they enter the wrong answer, the plugin will not "
"allow them login even if they entered the correct username and password."
msgstr ""
#: admin/wp-security-brute-force-menu.php:533
msgid ""
"Therefore, adding a captcha form on the login page is another effective yet "
"simple \"Brute Force\" prevention technique."
msgstr ""
#: admin/wp-security-brute-force-menu.php:539
msgid "Login Form Captcha Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:550
msgid "Enable Captcha On Login Page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:553
msgid "Check this if you want to insert a captcha form on the login page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:559
msgid "Custom Login Form Captcha Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:568
msgid "Enable Captcha On Custom Login Form"
msgstr ""
#: admin/wp-security-brute-force-menu.php:571
msgid ""
"Check this if you want to insert captcha on a custom login form generated by "
"the following WP function: wp_login_form()"
msgstr ""
#: admin/wp-security-brute-force-menu.php:577
msgid "Lost Password Form Captcha Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:587
msgid "Enable Captcha On Lost Password Page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:590
msgid ""
"Check this if you want to insert a captcha form on the lost password page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:612
msgid "Nonce check failed for save whitelist settings!"
msgstr ""
#: admin/wp-security-brute-force-menu.php:669
msgid ""
"The All In One WP Security Whitelist feature gives you the option of only "
"allowing certain IP addresses or ranges to have access to your WordPress "
"login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:670
msgid ""
"This feature will deny login access for all IP addresses which are not in "
"your whitelist as configured in the settings below."
msgstr ""
#: admin/wp-security-brute-force-menu.php:671
msgid ""
"The plugin achieves this by writing the appropriate directives to your ."
"htaccess file."
msgstr ""
#: admin/wp-security-brute-force-menu.php:672
msgid ""
"By allowing/blocking IP addresses via the .htaccess file your are using the "
"most secure first line of defence because login access will only be granted "
"to whitelisted IP addresses and other addresses will be blocked as soon as "
"they try to access your login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:680
#, php-format
msgid ""
"Attention: If in addition to enabling the white list feature, you also have "
"one of the %s or %s features enabled, <strong>you will still need to use "
"your secret word or special slug in the URL when trying to access your "
"WordPress login page</strong>."
msgstr ""
#: admin/wp-security-brute-force-menu.php:681
msgid ""
"These features are NOT functionally related. Having both of them enabled on "
"your site means you are creating 2 layers of security."
msgstr ""
#: admin/wp-security-brute-force-menu.php:686
msgid "Login IP Whitelist Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:697
msgid "Enable IP Whitelisting"
msgstr ""
#: admin/wp-security-brute-force-menu.php:700
msgid ""
"Check this if you want to enable the whitelisting of selected IP addresses "
"specified in the settings below"
msgstr ""
#: admin/wp-security-brute-force-menu.php:704
msgid "Your Current IP Address"
msgstr ""
#: admin/wp-security-brute-force-menu.php:707
msgid ""
"You can copy and paste this address in the text box below if you want to "
"include it in your login whitelist."
msgstr ""
#: admin/wp-security-brute-force-menu.php:711
msgid "Enter Whitelisted IP Addresses:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:715
msgid ""
"Enter one or more IP addresses or IP ranges you wish to include in your "
"whitelist. Only the addresses specified here will have access to the "
"WordPress login page."
msgstr ""
#: admin/wp-security-brute-force-menu.php:720
msgid ""
"To specify an IPv4 range use a wildcard \"*\" character. Acceptable ways to "
"use wildcards is shown in the examples below:"
msgstr ""
#: admin/wp-security-brute-force-menu.php:724
msgid ""
"Or you can enter an IPv6 address (NOTE: ranges/wildcards are currently not "
"supported for ipv6)"
msgstr ""
#: admin/wp-security-brute-force-menu.php:725
msgid "Example 4: 4102:0:3ea6:79fd:b:46f8:230f:bb05"
msgstr ""
#: admin/wp-security-brute-force-menu.php:726
msgid "Example 5: 2205:0:1ca2:810d::"
msgstr ""
#: admin/wp-security-brute-force-menu.php:766
msgid ""
"This feature allows you to add a special hidden \"honeypot\" field on the "
"WordPress login page. This will only be visible to robots and not humans."
msgstr ""
#: admin/wp-security-brute-force-menu.php:767
msgid ""
"Since robots usually fill in every input field from a login form, they will "
"also submit a value for the special hidden honeypot field."
msgstr ""
#: admin/wp-security-brute-force-menu.php:768
msgid ""
"The way honeypots work is that a hidden field is placed somewhere inside a "
"form which only robots will submit. If that field contains a value when the "
"form is submitted then a robot has most likely submitted the form and it is "
"consequently dealt with."
msgstr ""
#: admin/wp-security-brute-force-menu.php:769
msgid ""
"Therefore, if the plugin detects that this field has a value when the login "
"form is submitted, then the robot which is attempting to login to your site "
"will be redirected to its localhost address - http://127.0.0.1."
msgstr ""
#: admin/wp-security-brute-force-menu.php:775
msgid "Login Form Honeypot Settings"
msgstr ""
#: admin/wp-security-brute-force-menu.php:786
msgid "Enable Honeypot On Login Page"
msgstr ""
#: admin/wp-security-brute-force-menu.php:789
msgid ""
"Check this if you want to enable the honeypot feature for the login page"
msgstr ""
#: admin/wp-security-dashboard-menu.php:26
msgid "System Info"
msgstr ""
#: admin/wp-security-dashboard-menu.php:27
#: admin/wp-security-dashboard-menu.php:518
msgid "Locked IP Addresses"
msgstr ""
#: admin/wp-security-dashboard-menu.php:28
msgid "Permanent Block List"
msgstr ""
#: admin/wp-security-dashboard-menu.php:29
msgid "AIOWPS Logs"
msgstr ""
#: admin/wp-security-dashboard-menu.php:79
msgid "For information, updates and documentation, please visit the"
msgstr ""
#: admin/wp-security-dashboard-menu.php:79
msgid "AIO WP Security & Firewall Plugin"
msgstr ""
#: admin/wp-security-dashboard-menu.php:79
msgid "Page"
msgstr ""
#: admin/wp-security-dashboard-menu.php:80
msgid "Follow us"
msgstr ""
#: admin/wp-security-dashboard-menu.php:80
msgid ""
"Twitter, Google+ or via Email to stay up to date about the new security "
"features of this plugin."
msgstr ""
#: admin/wp-security-dashboard-menu.php:97
msgid "Security Strength Meter"
msgstr ""
#: admin/wp-security-dashboard-menu.php:128
msgid "Total Achievable Points: "
msgstr ""
#: admin/wp-security-dashboard-menu.php:130
msgid "Current Score of Your Site: "
msgstr ""
#: admin/wp-security-dashboard-menu.php:143
msgid "Security Points Breakdown"
msgstr ""
#: admin/wp-security-dashboard-menu.php:187
msgid "Spread the Word"
msgstr ""
#: admin/wp-security-dashboard-menu.php:192
msgid ""
"We are working hard to make your WordPress site more secure. Please support "
"us, here is how:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:217
msgid "Get To Know The Developers"
msgstr ""
#: admin/wp-security-dashboard-menu.php:221
msgid "Wanna know more about the developers behind this plugin?"
msgstr ""
#: admin/wp-security-dashboard-menu.php:238
msgid "Critical Feature Status"
msgstr ""
#: admin/wp-security-dashboard-menu.php:244
msgid ""
"Below is the current status of the critical features that you should "
"activate on your site to achieve a minimum level of recommended security"
msgstr ""
#: admin/wp-security-dashboard-menu.php:248
msgid "Admin Username"
msgstr ""
#: admin/wp-security-dashboard-menu.php:263
#: admin/wp-security-user-login-menu.php:25
#: classes/grade-system/wp-security-feature-item-manager.php:42
msgid "Login Lockdown"
msgstr ""
#: admin/wp-security-dashboard-menu.php:278
msgid "File Permission"
msgstr ""
#: admin/wp-security-dashboard-menu.php:293
msgid "Basic Firewall"
msgstr ""
#: admin/wp-security-dashboard-menu.php:314
msgid "Last 5 Logins"
msgstr ""
#: admin/wp-security-dashboard-menu.php:332
msgid "No data found!"
msgstr ""
#: admin/wp-security-dashboard-menu.php:336
msgid "Last 5 logins summary:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:340
msgid "User"
msgstr ""
#: admin/wp-security-dashboard-menu.php:341
msgid "Date"
msgstr ""
#: admin/wp-security-dashboard-menu.php:342
msgid "IP"
msgstr ""
#: admin/wp-security-dashboard-menu.php:366
msgid "Maintenance Mode Status"
msgstr ""
#: admin/wp-security-dashboard-menu.php:372
msgid ""
"Maintenance mode is currently enabled. Remember to turn it off when you are "
"done"
msgstr ""
#: admin/wp-security-dashboard-menu.php:374
msgid "Maintenance mode is currently off."
msgstr ""
#: admin/wp-security-dashboard-menu.php:378
msgid "Maintenance Mode"
msgstr ""
#: admin/wp-security-dashboard-menu.php:403
msgid "Cookie Based Brute Prevention"
msgstr ""
#: admin/wp-security-dashboard-menu.php:408
msgid "Cookie-Based Brute Force"
msgstr ""
#: admin/wp-security-dashboard-menu.php:412
#: admin/wp-security-dashboard-menu.php:444
#, php-format
msgid "The %s feature is currently active."
msgstr ""
#: admin/wp-security-dashboard-menu.php:413
#: admin/wp-security-dashboard-menu.php:445
msgid "Your new WordPress login URL is now:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:478
#: admin/wp-security-user-login-menu.php:29
msgid "Logged In Users"
msgstr ""
#: admin/wp-security-dashboard-menu.php:488
msgid "Number of users currently logged in site-wide is:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:489
#: admin/wp-security-dashboard-menu.php:503
#: admin/wp-security-dashboard-menu.php:531
#, php-format
msgid "Go to the %s menu to see more details"
msgstr ""
#: admin/wp-security-dashboard-menu.php:492
msgid "There are no other site-wide users currently logged in."
msgstr ""
#: admin/wp-security-dashboard-menu.php:502
msgid "Number of users currently logged into your site (including you) is:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:506
msgid "There are no other users currently logged in."
msgstr ""
#: admin/wp-security-dashboard-menu.php:527
msgid "There are no IP addresses currently locked out."
msgstr ""
#: admin/wp-security-dashboard-menu.php:530
msgid "Number of temporarily locked out IP addresses: "
msgstr ""
#: admin/wp-security-dashboard-menu.php:576
msgid "Site Info"
msgstr ""
#: admin/wp-security-dashboard-menu.php:580
msgid "Plugin Version"
msgstr ""
#: admin/wp-security-dashboard-menu.php:582
msgid "WP Version"
msgstr ""
#: admin/wp-security-dashboard-menu.php:585
#: admin/wp-security-dashboard-menu.php:589
#: admin/wp-security-dashboard-menu.php:698
msgid "Version"
msgstr ""
#: admin/wp-security-dashboard-menu.php:587
msgid "Table Prefix"
msgstr ""
#: admin/wp-security-dashboard-menu.php:591
msgid "Session Save Path"
msgstr ""
#: admin/wp-security-dashboard-menu.php:594
msgid "Server Name"
msgstr ""
#: admin/wp-security-dashboard-menu.php:596
msgid "Cookie Domain"
msgstr ""
#: admin/wp-security-dashboard-menu.php:599
msgid "Library Present"
msgstr ""
#: admin/wp-security-dashboard-menu.php:601
msgid "Debug File Write Permissions"
msgstr ""
#: admin/wp-security-dashboard-menu.php:607
msgid "PHP Info"
msgstr ""
#: admin/wp-security-dashboard-menu.php:611
msgid "PHP Version"
msgstr ""
#: admin/wp-security-dashboard-menu.php:613
msgid "PHP Memory Usage"
msgstr ""
#: admin/wp-security-dashboard-menu.php:614
msgid " MB"
msgstr ""
#: admin/wp-security-dashboard-menu.php:620
#: admin/wp-security-dashboard-menu.php:629
#: admin/wp-security-dashboard-menu.php:638
#: admin/wp-security-dashboard-menu.php:676
msgid "N/A"
msgstr ""
#: admin/wp-security-dashboard-menu.php:623
msgid "PHP Memory Limit"
msgstr ""
#: admin/wp-security-dashboard-menu.php:632
msgid "PHP Max Upload Size"
msgstr ""
#: admin/wp-security-dashboard-menu.php:641
msgid "PHP Max Post Size"
msgstr ""
#: admin/wp-security-dashboard-menu.php:645
#: admin/wp-security-dashboard-menu.php:655
#: admin/wp-security-dashboard-menu.php:664
msgid "On"
msgstr ""
#: admin/wp-security-dashboard-menu.php:647
#: admin/wp-security-dashboard-menu.php:657
#: admin/wp-security-dashboard-menu.php:666
msgid "Off"
msgstr ""
#: admin/wp-security-dashboard-menu.php:650
msgid "PHP Allow URL fopen"
msgstr ""
#: admin/wp-security-dashboard-menu.php:660
msgid "PHP Allow URL Include"
msgstr ""
#: admin/wp-security-dashboard-menu.php:669
msgid "PHP Display Errors"
msgstr ""
#: admin/wp-security-dashboard-menu.php:679
msgid "PHP Max Script Execution Time"
msgstr ""
#: admin/wp-security-dashboard-menu.php:680
msgid "Seconds"
msgstr ""
#: admin/wp-security-dashboard-menu.php:686
msgid "Active Plugins"
msgstr ""
#: admin/wp-security-dashboard-menu.php:697
#: admin/wp-security-filesystem-menu.php:131
#: admin/wp-security-filesystem-menu.php:150
msgid "Name"
msgstr ""
#: admin/wp-security-dashboard-menu.php:699
msgid "Plugin URL"
msgstr ""
#: admin/wp-security-dashboard-menu.php:737
msgid ""
"This tab displays the list of all IP addresses which are currently "
"temporarily locked out due to the Login Lockdown feature:"
msgstr ""
#: admin/wp-security-dashboard-menu.php:744
msgid "Currently Locked Out IP Addresses and Ranges"
msgstr ""
#: admin/wp-security-dashboard-menu.php:787
msgid "This tab displays the list of all permanently blocked IP addresses."
msgstr ""
#: admin/wp-security-dashboard-menu.php:788
#: admin/wp-security-spam-menu.php:291
msgid ""
"NOTE: This feature does NOT use the .htaccess file to permanently block the "
"IP addresses so it should be compatible with all web servers running "
"WordPress."
msgstr ""
#: admin/wp-security-dashboard-menu.php:794
msgid "Permanently Blocked IP Addresses"
msgstr ""
#: admin/wp-security-dashboard-menu.php:828
msgid "View Logs for All In WP Security & Firewall Plugin"
msgstr ""
#: admin/wp-security-dashboard-menu.php:836
msgid "Log File"
msgstr ""
#: admin/wp-security-dashboard-menu.php:840
msgid "--Select a file--"
msgstr ""
#: admin/wp-security-dashboard-menu.php:851
msgid "Select one of the log files to view the contents"
msgstr ""
#: admin/wp-security-dashboard-menu.php:856
msgid "View Logs"
msgstr ""
#: admin/wp-security-dashboard-menu.php:877
msgid ""
"Error! The file you selected is not a permitted file. You can only view log "
"files created by this plugin."
msgstr ""
#: admin/wp-security-dashboard-menu.php:884
msgid "Log File Contents For"
msgstr ""
#: admin/wp-security-dashboard-menu.php:898
msgid "Log file is empty!"
msgstr ""
#: admin/wp-security-database-menu.php:26
#: admin/wp-security-database-menu.php:31
#: classes/grade-system/wp-security-feature-item-manager.php:63
msgid "DB Backup"
msgstr ""
#: admin/wp-security-database-menu.php:30
#: classes/grade-system/wp-security-feature-item-manager.php:61
msgid "DB Prefix"
msgstr ""
#: admin/wp-security-database-menu.php:94
msgid "Nonce check failed for DB prefix change operation!"
msgstr ""
#: admin/wp-security-database-menu.php:102
msgid ""
"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."
msgstr ""
#: admin/wp-security-database-menu.php:115
msgid "Please enter a value for the DB prefix."
msgstr ""
#: admin/wp-security-database-menu.php:124
msgid ""
"<strong>ERROR</strong>: The table prefix can only contain numbers, letters, "
"and underscores."
msgstr ""
#: admin/wp-security-database-menu.php:133
msgid "Change Database Prefix"
msgstr ""
#: admin/wp-security-database-menu.php:136
msgid ""
"Your WordPress DB is the most important asset of your website because it "
"contains a lot of your site's precious information."
msgstr ""
#: admin/wp-security-database-menu.php:137
msgid ""
"The DB is also a target for hackers via methods such as SQL injections and "
"malicious and automated code which targets certain tables."
msgstr ""
#: admin/wp-security-database-menu.php:138
msgid ""
"One way to add a layer of protection for your DB is to change the default "
"WordPress table prefix from \"wp_\" to something else which will be "
"difficult for hackers to guess."
msgstr ""
#: admin/wp-security-database-menu.php:139
msgid ""
"This feature allows you to easily change the prefix to a value of your "
"choice or to a random value set by this plugin."
msgstr ""
#: admin/wp-security-database-menu.php:145
msgid "DB Prefix Options"
msgstr ""
#: admin/wp-security-database-menu.php:156
#, php-format
msgid "It is recommended that you perform a %s before using this feature"
msgstr ""
#: admin/wp-security-database-menu.php:165
msgid "Current DB Table Prefix"
msgstr ""
#: admin/wp-security-database-menu.php:171
msgid ""
"Your site is currently using the default WordPress DB prefix value of \"wp_"
"\". \n"
" To increase your site's security you should "
"consider changing the DB prefix value to another value."
msgstr ""
#: admin/wp-security-database-menu.php:178
msgid "Generate New DB Table Prefix"
msgstr ""
#: admin/wp-security-database-menu.php:181
msgid ""
"Check this if you want the plugin to generate a random 6 character string "
"for the table prefix"
msgstr ""
#: admin/wp-security-database-menu.php:182
msgid "OR"
msgstr ""
#: admin/wp-security-database-menu.php:184
msgid ""
"Choose your own DB prefix by specifying a string which contains letters and/"
"or numbers and/or underscores. Example: xyz_"
msgstr ""
#: admin/wp-security-database-menu.php:188
msgid "Change DB Prefix"
msgstr ""
#: admin/wp-security-database-menu.php:209
#: admin/wp-security-filesystem-menu.php:87
msgid "Nonce check failed for manual DB backup operation!"
msgstr ""
#: admin/wp-security-database-menu.php:226
msgid ""
"DB Backup was successfully completed! You will receive the backup file via "
"email if you have enabled \"Send Backup File Via Email\", otherwise you can "
"retrieve it via FTP from the following directory:"
msgstr ""
#: admin/wp-security-database-menu.php:228
msgid "Your DB Backup File location: "
msgstr ""
#: admin/wp-security-database-menu.php:235
msgid "DB Backup failed. Please check the permissions of the backup directory."
msgstr ""
#: admin/wp-security-database-menu.php:252
#: admin/wp-security-filescan-menu.php:133
msgid ""
"You entered a non numeric value for the \"backup time interval\" field. It "
"has been set to the default value."
msgstr ""
#: admin/wp-security-database-menu.php:259
msgid ""
"You entered a non numeric value for the \"number of backup files to keep\" "
"field. It has been set to the default value."
msgstr ""
#: admin/wp-security-database-menu.php:266
#: admin/wp-security-user-login-menu.php:118
msgid ""
"You have entered an incorrect email address format. It has been set to your "
"WordPress admin email as default."
msgstr ""
#: admin/wp-security-database-menu.php:299
msgid "Manual Backup"
msgstr ""
#: admin/wp-security-database-menu.php:304
msgid "To create a new DB backup just click on the button below."
msgstr ""
#: admin/wp-security-database-menu.php:306
msgid "Create DB Backup Now"
msgstr ""
#: admin/wp-security-database-menu.php:310
msgid "Automated Scheduled Backups"
msgstr ""
#: admin/wp-security-database-menu.php:322
msgid "Enable Automated Scheduled Backups"
msgstr ""
#: admin/wp-security-database-menu.php:325
msgid ""
"Check this if you want the system to automatically generate backups "
"periodically based on the settings below"
msgstr ""
#: admin/wp-security-database-menu.php:329
msgid "Backup Time Interval"
msgstr ""
#: admin/wp-security-database-menu.php:332
#: admin/wp-security-filescan-menu.php:285
msgid "Hours"
msgstr ""
#: admin/wp-security-database-menu.php:333
#: admin/wp-security-filescan-menu.php:286
msgid "Days"
msgstr ""
#: admin/wp-security-database-menu.php:334
#: admin/wp-security-filescan-menu.php:287
msgid "Weeks"
msgstr ""
#: admin/wp-security-database-menu.php:336
msgid "Set the value for how often you would like an automated backup to occur"
msgstr ""
#: admin/wp-security-database-menu.php:340
msgid "Number of Backup Files To Keep"
msgstr ""
#: admin/wp-security-database-menu.php:342
msgid ""
"Thie field allows you to choose the number of backup files you would like to "
"keep in the backup directory"
msgstr ""
#: admin/wp-security-database-menu.php:346
msgid "Send Backup File Via Email"
msgstr ""
#: admin/wp-security-database-menu.php:349
msgid ""
"Check this if you want the system to email you the backup file after a DB "
"backup has been performed"
msgstr ""
#: admin/wp-security-database-menu.php:351
#: admin/wp-security-user-login-menu.php:262
msgid "Enter an email address"
msgstr ""
#: admin/wp-security-database-menu.php:382
msgid "Error - Could not get tables or no tables found!"
msgstr ""
#: admin/wp-security-database-menu.php:386
msgid "Starting DB prefix change operations....."
msgstr ""
#: admin/wp-security-database-menu.php:388
#, php-format
msgid ""
"Your WordPress system has a total of %s tables and your new DB prefix will "
"be: %s"
msgstr ""
#: admin/wp-security-database-menu.php:394 classes/wp-security-utility.php:279
msgid ""
"Failed to make a backup of the wp-config.php file. This operation will not "
"go ahead."
msgstr ""
#: admin/wp-security-database-menu.php:398
msgid "A backup copy of your wp-config.php file was created successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:425
#, php-format
msgid "%s table name update failed"
msgstr ""
#: admin/wp-security-database-menu.php:437
#, php-format
msgid "Please change the prefix manually for the above tables to: %s"
msgstr ""
#: admin/wp-security-database-menu.php:440
#, php-format
msgid "%s tables had their prefix updated successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:459
msgid "wp-config.php file was updated successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:462
#, php-format
msgid ""
"The \"wp-config.php\" file was not able to be modified. Please modify this "
"file manually using your favourite editor and search \n"
" for variable \"$table_prefix\" and assign the following "
"value to that variable: %s"
msgstr ""
#: admin/wp-security-database-menu.php:474
#: admin/wp-security-database-menu.php:493
#, php-format
msgid "Update of table %s failed: unable to change %s to %s"
msgstr ""
#: admin/wp-security-database-menu.php:478
msgid ""
"The options table records which had references to the old DB prefix were "
"updated successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:497
#, php-format
msgid ""
"The %s table records which had references to the old DB prefix were updated "
"successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:525
#, php-format
msgid ""
"Error updating user_meta table where new meta_key = %s, old meta_key = %s "
"and user_id = %s."
msgstr ""
#: admin/wp-security-database-menu.php:530
msgid ""
"The usermeta table records which had references to the old DB prefix were "
"updated successfully!"
msgstr ""
#: admin/wp-security-database-menu.php:532
msgid "DB prefix change tasks have been completed."
msgstr ""
#: admin/wp-security-database-menu.php:575
msgid "Checking for MySQL tables of type \"view\"....."
msgstr ""
#: admin/wp-security-database-menu.php:592
#, php-format
msgid "Update of the following MySQL view definition failed: %s"
msgstr ""
#: admin/wp-security-database-menu.php:599
#, php-format
msgid "%s view definitions were updated successfully!"
msgstr ""
#: admin/wp-security-filescan-menu.php:23
#: classes/grade-system/wp-security-feature-item-manager.php:108
msgid "File Change Detection"
msgstr ""
#: admin/wp-security-filescan-menu.php:24
msgid "Malware Scan"
msgstr ""
#: admin/wp-security-filescan-menu.php:93
msgid "There have been no file changes since the last scan."
msgstr ""
#: admin/wp-security-filescan-menu.php:103
msgid "Nonce check failed for manual file change detection scan operation!"
msgstr ""
#: admin/wp-security-filescan-menu.php:110
msgid ""
"The plugin has detected that this is your first file change detection scan. "
"The file details from this scan will be used to detect file changes for "
"future scans!"
msgstr ""
#: admin/wp-security-filescan-menu.php:112
msgid "Scan Complete - There were no file changes detected!"
msgstr ""
#: admin/wp-security-filescan-menu.php:167
msgid ""
"The following address was removed because it is not a valid email address: "
msgstr ""
#: admin/wp-security-filescan-menu.php:207
msgid ""
"NEW SCAN COMPLETED: The plugin has detected that you have made changes to "
"the \"File Types To Ignore\" or \"Files To Ignore\" fields.\n"
" In order to ensure that future scan results are "
"accurate, the old scan data has been refreshed."
msgstr ""
#: admin/wp-security-filescan-menu.php:217
msgid ""
"All In One WP Security & Firewall has detected that there was a change in "
"your host's files."
msgstr ""
#: admin/wp-security-filescan-menu.php:219
msgid "View Scan Details & Clear This Message"
msgstr ""
#: admin/wp-security-filescan-menu.php:228
msgid ""
"If given an opportunity hackers can insert their code or files into your "
"system which they can then use to carry out malicious acts on your site."
msgstr ""
#: admin/wp-security-filescan-menu.php:229
msgid ""
"Being informed of any changes in your files can be a good way to quickly "
"prevent a hacker from causing damage to your website."
msgstr ""
#: admin/wp-security-filescan-menu.php:230
msgid ""
"In general, WordPress core and plugin files and file types such as \".php\" "
"or \".js\" should not change often and when they do, it is important that "
"you are made aware when a change occurs and which file was affected."
msgstr ""
#: admin/wp-security-filescan-menu.php:231
msgid ""
"The \"File Change Detection Feature\" will notify you of any file change "
"which occurs on your system, including the addition and deletion of files by "
"performing a regular automated or manual scan of your system's files."
msgstr ""
#: admin/wp-security-filescan-menu.php:232
msgid ""
"This feature also allows you to exclude certain files or folders from the "
"scan in cases where you know that they change often as part of their normal "
"operation. (For example log files and certain caching plugin files may "
"change often and hence you may choose to exclude such files from the file "
"change detection scan)"
msgstr ""
#: admin/wp-security-filescan-menu.php:237
msgid "Manual File Change Detection Scan"
msgstr ""
#: admin/wp-security-filescan-menu.php:243
msgid ""
"To perform a manual file change detection scan click on the button below."
msgstr ""
#: admin/wp-security-filescan-menu.php:246
msgid "Perform Scan Now"
msgstr ""
#: admin/wp-security-filescan-menu.php:250
msgid "View Last Saved File Change Results"
msgstr ""
#: admin/wp-security-filescan-menu.php:256
msgid ""
"Click the button below to view the saved file change results from the last "
"scan."
msgstr ""
#: admin/wp-security-filescan-menu.php:259
msgid "View Last File Change"
msgstr ""
#: admin/wp-security-filescan-menu.php:263
msgid "File Change Detection Settings"
msgstr ""
#: admin/wp-security-filescan-menu.php:275
msgid "Enable Automated File Change Detection Scan"
msgstr ""
#: admin/wp-security-filescan-menu.php:278
msgid ""
"Check this if you want the system to automatically/periodically scan your "
"files to check for file changes based on the settings below"
msgstr ""
#: admin/wp-security-filescan-menu.php:282
msgid "Scan Time Interval"
msgstr ""
#: admin/wp-security-filescan-menu.php:289
msgid "Set the value for how often you would like a scan to occur"
msgstr ""
#: admin/wp-security-filescan-menu.php:293
msgid "File Types To Ignore"
msgstr ""
#: admin/wp-security-filescan-menu.php:296
msgid ""
"Enter each file type or extension on a new line which you wish to exclude "
"from the file change detection scan."
msgstr ""
#: admin/wp-security-filescan-menu.php:300
msgid ""
"You can exclude file types from the scan which would not normally pose any "
"security threat if they were changed. These can include things such as image "
"files."
msgstr ""
#: admin/wp-security-filescan-menu.php:301
msgid ""
"Example: If you want the scanner to ignore files of type jpg, png, and bmp, "
"then you would enter the following:"
msgstr ""
#: admin/wp-security-filescan-menu.php:302
msgid "jpg"
msgstr ""
#: admin/wp-security-filescan-menu.php:303
msgid "png"
msgstr ""
#: admin/wp-security-filescan-menu.php:304
msgid "bmp"
msgstr ""
#: admin/wp-security-filescan-menu.php:310
msgid "Files/Directories To Ignore"
msgstr ""
#: admin/wp-security-filescan-menu.php:313
msgid ""
"Enter each file or directory on a new line which you wish to exclude from "
"the file change detection scan."
msgstr ""
#: admin/wp-security-filescan-menu.php:317
msgid ""
"You can exclude specific files/directories from the scan which would not "
"normally pose any security threat if they were changed. These can include "
"things such as log files."
msgstr ""
#: admin/wp-security-filescan-menu.php:318
msgid ""
"Example: If you want the scanner to ignore certain files in different "
"directories or whole directories, then you would enter the following:"
msgstr ""
#: admin/wp-security-filescan-menu.php:319
msgid "cache/config/master.php"
msgstr ""
#: admin/wp-security-filescan-menu.php:320
msgid "somedirectory"
msgstr ""
#: admin/wp-security-filescan-menu.php:326
msgid "Send Email When Change Detected"
msgstr ""
#: admin/wp-security-filescan-menu.php:329
msgid ""
"Check this if you want the system to email you if a file change was detected"
msgstr ""
#: admin/wp-security-filescan-menu.php:333
msgid "Enter one or more email addresses on a new line."
msgstr ""
#: admin/wp-security-filescan-menu.php:349
msgid "What is Malware?"
msgstr ""
#: admin/wp-security-filescan-menu.php:350
msgid ""
"The word Malware stands for Malicious Software. It can consist of things "
"like trojan horses, adware, worms, spyware and any other undesirable code "
"which a hacker will try to inject into your website."
msgstr ""
#: admin/wp-security-filescan-menu.php:351
msgid ""
"Often when malware code has been inserted into your site you will normally "
"not notice anything out of the ordinary based on appearances, but it can "
"have a dramatic effect on your site's search ranking."
msgstr ""
#: admin/wp-security-filescan-menu.php:352
msgid ""
"This is because the bots and spiders from search engines such as Google have "
"the capability to detect malware when they are indexing the pages on your "
"site, and consequently they can blacklist your website which will in turn "
"affect your search rankings."
msgstr ""
#: admin/wp-security-filescan-menu.php:356
msgid "Scanning For Malware"
msgstr ""
#: admin/wp-security-filescan-menu.php:357
msgid ""
"Due to the constantly changing and complex nature of Malware, scanning for "
"such things using a standalone plugin will not work reliably. This is "
"something best done via an external scan of your site regularly."
msgstr ""
#: admin/wp-security-filescan-menu.php:358
msgid ""
"This is why we have created an easy-to-use scanning service which is hosted "
"off our own server which will scan your site for malware once every day and "
"notify you if it finds anything."
msgstr ""
#: admin/wp-security-filescan-menu.php:359
msgid "When you sign up for this service you will get the following:"
msgstr ""
#: admin/wp-security-filescan-menu.php:361
msgid "Automatic Daily Scan of 1 Website"
msgstr ""
#: admin/wp-security-filescan-menu.php:362
msgid "Automatic Malware & Blacklist Monitoring"
msgstr ""
#: admin/wp-security-filescan-menu.php:363
msgid "Automatic Email Alerting"
msgstr ""
#: admin/wp-security-filescan-menu.php:364
msgid "Site uptime monitoring"
msgstr ""
#: admin/wp-security-filescan-menu.php:365
msgid "Site response time monitoring"
msgstr ""
#: admin/wp-security-filescan-menu.php:366
msgid "We provide advice for malware cleanup"
msgstr ""
#: admin/wp-security-filescan-menu.php:367
msgid "Blacklist Removal"
msgstr ""
#: admin/wp-security-filescan-menu.php:368
msgid "No Contract (Cancel Anytime)"
msgstr ""
#: admin/wp-security-filescan-menu.php:370
#, php-format
msgid "To learn more please %s."
msgstr ""
#: admin/wp-security-filescan-menu.php:390
msgid "Latest File Change Scan Results"
msgstr ""
#: admin/wp-security-filescan-menu.php:399
msgid "The following files were added to your host."
msgstr ""
#: admin/wp-security-filescan-menu.php:402
#: admin/wp-security-filescan-menu.php:423
#: admin/wp-security-filescan-menu.php:447
#: admin/wp-security-settings-menu.php:27
#: admin/wp-security-settings-menu.php:28
msgid "File"
msgstr ""
#: admin/wp-security-filescan-menu.php:403
#: admin/wp-security-filescan-menu.php:424
#: admin/wp-security-filescan-menu.php:448
msgid "File Size"
msgstr ""
#: admin/wp-security-filescan-menu.php:404
#: admin/wp-security-filescan-menu.php:425
#: admin/wp-security-filescan-menu.php:449
msgid "File Modified"
msgstr ""
#: admin/wp-security-filescan-menu.php:420
msgid "The following files were removed from your host."
msgstr ""
#: admin/wp-security-filescan-menu.php:444
msgid "The following files were changed on your host."
msgstr ""
#: admin/wp-security-filesystem-menu.php:26
#: classes/grade-system/wp-security-feature-item-manager.php:67
msgid "File Permissions"
msgstr ""
#: admin/wp-security-filesystem-menu.php:27
msgid "PHP File Editing"
msgstr ""
#: admin/wp-security-filesystem-menu.php:28
msgid "WP File Access"
msgstr ""
#: admin/wp-security-filesystem-menu.php:29
msgid "Host System Logs"
msgstr ""
#: admin/wp-security-filesystem-menu.php:97
#, php-format
msgid "The permissions for %s were succesfully changed to %s"
msgstr ""
#: admin/wp-security-filesystem-menu.php:101
#, php-format
msgid "Unable to change permissions for %s!"
msgstr ""
#: admin/wp-security-filesystem-menu.php:107
msgid "File Permissions Scan"
msgstr ""
#: admin/wp-security-filesystem-menu.php:110
msgid ""
"Your WordPress file and folder permission settings govern the accessability "
"and read/write privileges of the files and folders which make up your WP "
"installation."
msgstr ""
#: admin/wp-security-filesystem-menu.php:111
msgid ""
"Your WP installation already comes with reasonably secure file permission "
"settings for the filesystem."
msgstr ""
#: admin/wp-security-filesystem-menu.php:112
msgid ""
"However, sometimes people or other plugins modify the various permission "
"settings of certain core WP folders or files such that they end up making "
"their site less secure because they chose the wrong permission values."
msgstr ""
#: admin/wp-security-filesystem-menu.php:113
msgid ""
"This feature will scan the critical WP core folders and files and will "
"highlight any permission settings which are insecure."
msgstr ""
#: admin/wp-security-filesystem-menu.php:119
msgid "WP Directory and File Permissions Scan Results"
msgstr ""
#: admin/wp-security-filesystem-menu.php:132
#: admin/wp-security-filesystem-menu.php:151
msgid "File/Folder"
msgstr ""
#: admin/wp-security-filesystem-menu.php:133
#: admin/wp-security-filesystem-menu.php:152
msgid "Current Permissions"
msgstr ""
#: admin/wp-security-filesystem-menu.php:134
#: admin/wp-security-filesystem-menu.php:153
msgid "Recommended Permissions"
msgstr ""
#: admin/wp-security-filesystem-menu.php:135
#: admin/wp-security-filesystem-menu.php:154
msgid "Recommended Action"
msgstr ""
#: admin/wp-security-filesystem-menu.php:192
msgid "Your PHP file editing settings were saved successfully."
msgstr ""
#: admin/wp-security-filesystem-menu.php:196
msgid ""
"Operation failed! Unable to modify or make a backup of wp-config.php file!"
msgstr ""
#: admin/wp-security-filesystem-menu.php:209
#: classes/grade-system/wp-security-feature-item-manager.php:69
msgid "File Editing"
msgstr ""
#: admin/wp-security-filesystem-menu.php:212
msgid ""
"The Wordpress Dashboard by default allows administrators to edit PHP files, "
"such as plugin and theme files."
msgstr ""
#: admin/wp-security-filesystem-menu.php:213
msgid ""
"This is often the first tool an attacker will use if able to login, since it "
"allows code execution."
msgstr ""
#: admin/wp-security-filesystem-menu.php:214
msgid ""
"This feature will disable the ability for people to edit PHP files via the "
"dashboard."
msgstr ""
#: admin/wp-security-filesystem-menu.php:220
msgid "Disable PHP File Editing"
msgstr ""
#: admin/wp-security-filesystem-menu.php:232
msgid "Disable Ability To Edit PHP Files"
msgstr ""
#: admin/wp-security-filesystem-menu.php:235
msgid ""
"Check this if you want to remove the ability for people to edit PHP files "
"via the WP dashboard"
msgstr ""
#: admin/wp-security-filesystem-menu.php:279
msgid ""
"You have successfully saved the Prevent Access to Default WP Files "
"configuration."
msgstr ""
#: admin/wp-security-filesystem-menu.php:288
msgid "WordPress Files"
msgstr ""
#: admin/wp-security-filesystem-menu.php:291
#, php-format
msgid ""
"This feature allows you to prevent access to files such as %s, %s and %s "
"which are delivered with all WP installations."
msgstr ""
#: admin/wp-security-filesystem-menu.php:292
msgid ""
"By preventing access to these files you are hiding some key pieces of "
"information (such as WordPress version info) from potential hackers."
msgstr ""
#: admin/wp-security-filesystem-menu.php:297
msgid "Prevent Access to Default WP Files"
msgstr ""
#: admin/wp-security-filesystem-menu.php:308
msgid "Prevent Access to WP Default Install Files"
msgstr ""
#: admin/wp-security-filesystem-menu.php:311
msgid ""
"Check this if you want to prevent access to readme.html, license.txt and wp-"
"config-sample.php."
msgstr ""
#: admin/wp-security-filesystem-menu.php:315
msgid "Save Setting"
msgstr ""
#: admin/wp-security-filesystem-menu.php:339
msgid "System Logs"
msgstr ""
#: admin/wp-security-filesystem-menu.php:342
msgid ""
"Sometimes your hosting platform will produce error or warning logs in a file "
"called \"error_log\"."
msgstr ""
#: admin/wp-security-filesystem-menu.php:343
msgid ""
"Depending on the nature and cause of the error or warning, your hosting "
"server can create multiple instances of this file in numerous directory "
"locations of your WordPress installation."
msgstr ""
#: admin/wp-security-filesystem-menu.php:344
msgid ""
"By occassionally viewing the contents of these logs files you can keep "
"informed of any underlying problems on your system which you might need to "
"address."
msgstr ""
#: admin/wp-security-filesystem-menu.php:350
msgid "View System Logs"
msgstr ""
#: admin/wp-security-filesystem-menu.php:355
msgid "Enter System Log File Name"
msgstr ""
#: admin/wp-security-filesystem-menu.php:357
msgid "Enter your system log file name. (Defaults to error_log)"
msgstr ""
#: admin/wp-security-filesystem-menu.php:360
msgid "View Latest System Logs"
msgstr ""
#: admin/wp-security-filesystem-menu.php:362
msgid "Loading..."
msgstr ""
#: admin/wp-security-filesystem-menu.php:379
msgid "No system logs were found!"
msgstr ""
#: admin/wp-security-filesystem-menu.php:432
msgid "Set Recommended Permissions"
msgstr ""
#: admin/wp-security-filesystem-menu.php:438
msgid "No Action Required"
msgstr ""
#: admin/wp-security-filesystem-menu.php:478
#, php-format
msgid "Showing latest entries of error_log file: %s"
msgstr ""
#: admin/wp-security-firewall-menu.php:28
msgid "Basic Firewall Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:29
msgid "Additional Firewall Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:30
msgid "6G Blacklist Firewall Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:31
msgid "Internet Bots"
msgstr ""
#: admin/wp-security-firewall-menu.php:32
msgid "Prevent Hotlinks"
msgstr ""
#: admin/wp-security-firewall-menu.php:33
msgid "404 Detection"
msgstr ""
#: admin/wp-security-firewall-menu.php:34
msgid "Custom Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:120
#: admin/wp-security-firewall-menu.php:742 admin/wp-security-spam-menu.php:105
#: admin/wp-security-spam-menu.php:448
#: admin/wp-security-user-registration-menu.php:97
msgid "Settings were successfully saved"
msgstr ""
#: admin/wp-security-firewall-menu.php:129
#: admin/wp-security-firewall-menu.php:563
msgid "Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:136
#, php-format
msgid ""
"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."
msgstr ""
#: admin/wp-security-firewall-menu.php:137
msgid ""
"The features in this tab allow you to activate some basic firewall security "
"protection rules for your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:138
msgid ""
"The firewall functionality is achieved via the insertion of special code "
"into your currently active .htaccess file."
msgstr ""
#: admin/wp-security-firewall-menu.php:149
msgid ""
"Attention: You have enabled the \"Completely Block Access To XMLRPC\" "
"checkbox which means all XMLRPC functionality will be blocked."
msgstr ""
#: admin/wp-security-firewall-menu.php:150
msgid ""
"By leaving this feature enabled you will prevent Jetpack or Wordpress iOS or "
"other apps which need XMLRPC from working correctly on your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:151
msgid ""
"If you still need XMLRPC then uncheck the \"Completely Block Access To XMLRPC"
"\" checkbox and enable only the \"Disable Pingback Functionality From XMLRPC"
"\" checkbox."
msgstr ""
#: admin/wp-security-firewall-menu.php:161
msgid "Basic Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:169
msgid "Enable Basic Firewall Protection"
msgstr ""
#: admin/wp-security-firewall-menu.php:172
msgid "Check this if you want to apply basic firewall protection to your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:176
msgid ""
"This setting will implement the following basic firewall protection "
"mechanisms on your site:"
msgstr ""
#: admin/wp-security-firewall-menu.php:177
msgid "1) Protect your htaccess file by denying access to it."
msgstr ""
#: admin/wp-security-firewall-menu.php:178
msgid "2) Disable the server signature."
msgstr ""
#: admin/wp-security-firewall-menu.php:179
msgid "3) Limit file upload size (10MB)."
msgstr ""
#: admin/wp-security-firewall-menu.php:180
msgid "4) Protect your wp-config.php file by denying access to it."
msgstr ""
#: admin/wp-security-firewall-menu.php:181
msgid ""
"The above firewall features will be applied via your .htaccess file and "
"should not affect your site's overall functionality."
msgstr ""
#: admin/wp-security-firewall-menu.php:182
msgid ""
"You are still advised to take a backup of your active .htaccess file just in "
"case."
msgstr ""
#: admin/wp-security-firewall-menu.php:191
msgid "WordPress XMLRPC & Pingback Vulnerability Protection"
msgstr ""
#: admin/wp-security-firewall-menu.php:199
msgid "Completely Block Access To XMLRPC"
msgstr ""
#: admin/wp-security-firewall-menu.php:202
msgid ""
"Check this if you are not using the WP XML-RPC functionality and you want to "
"completely block external access to XMLRPC."
msgstr ""
#: admin/wp-security-firewall-menu.php:206
msgid ""
"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 "
"in WordPress."
msgstr ""
#: admin/wp-security-firewall-menu.php:207
msgid ""
"Hackers can exploit various vulnerabilities in the WordPress XML-RPC API in "
"a number of ways such as:"
msgstr ""
#: admin/wp-security-firewall-menu.php:208
msgid "1) Denial of Service (DoS) attacks"
msgstr ""
#: admin/wp-security-firewall-menu.php:209
msgid "2) Hacking internal routers."
msgstr ""
#: admin/wp-security-firewall-menu.php:210
msgid "3) Scanning ports in internal networks to get info from various hosts."
msgstr ""
#: admin/wp-security-firewall-menu.php:211
msgid ""
"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."
msgstr ""
#: admin/wp-security-firewall-menu.php:212
msgid ""
"NOTE: You should only enable this feature if you are not currently using the "
"XML-RPC functionality on your WordPress installation."
msgstr ""
#: admin/wp-security-firewall-menu.php:213
msgid ""
"Leave this feature disabled and use the feature below if you want pingback "
"protection but you still need XMLRPC."
msgstr ""
#: admin/wp-security-firewall-menu.php:219
msgid "Disable Pingback Functionality From XMLRPC"
msgstr ""
#: admin/wp-security-firewall-menu.php:222
msgid ""
"If you use Jetpack or WP iOS or other apps which need WP XML-RPC "
"functionality then check this. This will enable protection against WordPress "
"pingback vulnerabilities."
msgstr ""
#: admin/wp-security-firewall-menu.php:226
msgid ""
"NOTE: If you use Jetpack or the Wordpress iOS or other apps then you should "
"enable this feature but leave the \"Completely Block Access To XMLRPC\" "
"checkbox unchecked."
msgstr ""
#: admin/wp-security-firewall-menu.php:227
msgid ""
"The feature will still allow XMLRPC functionality on your site but will "
"disable the pingback methods."
msgstr ""
#: admin/wp-security-firewall-menu.php:228
msgid ""
"This feature will also remove the \"X-Pingback\" header if it is present."
msgstr ""
#: admin/wp-security-firewall-menu.php:237
#: classes/grade-system/wp-security-feature-item-manager.php:81
msgid "Block Accesss to Debug Log File"
msgstr ""
#: admin/wp-security-firewall-menu.php:245
msgid "Block Access to debug.log File"
msgstr ""
#: admin/wp-security-firewall-menu.php:248
msgid ""
"Check this if you want to block access to the debug.log file that WordPress "
"creates when debug logging is enabled."
msgstr ""
#: admin/wp-security-firewall-menu.php:252
msgid ""
"WordPress has an option to turn on the debug logging to a file located in wp-"
"content/debug.log. This file may contain sensitive information."
msgstr ""
#: admin/wp-security-firewall-menu.php:253
msgid ""
"Using this optoin will block external access to this file. You can still "
"access this file by logging into your site via FTP"
msgstr ""
#: admin/wp-security-firewall-menu.php:261
msgid "Save Basic Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:333
msgid ""
"You have successfully saved the Additional Firewall Protection configuration"
msgstr ""
#: admin/wp-security-firewall-menu.php:347
msgid "Additional Firewall Protection"
msgstr ""
#: admin/wp-security-firewall-menu.php:351
#, php-format
msgid ""
"Due to the nature of the code being inserted to the .htaccess file, this "
"feature may break some functionality for certain plugins and you are "
"therefore advised to take a %s of .htaccess before applying this "
"configuration."
msgstr ""
#: admin/wp-security-firewall-menu.php:353
msgid ""
"This feature allows you to activate more advanced firewall settings to your "
"site."
msgstr ""
#: admin/wp-security-firewall-menu.php:354
msgid ""
"The advanced firewall rules are applied via the insertion of special code to "
"your currently active .htaccess file."
msgstr ""
#: admin/wp-security-firewall-menu.php:363
msgid "Listing of Directory Contents"
msgstr ""
#: admin/wp-security-firewall-menu.php:372
#: classes/grade-system/wp-security-feature-item-manager.php:92
msgid "Disable Index Views"
msgstr ""
#: admin/wp-security-firewall-menu.php:375
msgid "Check this if you want to disable directory and file listing."
msgstr ""
#: admin/wp-security-firewall-menu.php:380
msgid ""
"By default, an Apache server will allow the listing of the contents of a "
"directory if it doesn't contain an index.php file."
msgstr ""
#: admin/wp-security-firewall-menu.php:382
msgid "This feature will prevent the listing of contents for all directories."
msgstr ""
#: admin/wp-security-firewall-menu.php:384
msgid ""
"NOTE: In order for this feature to work \"AllowOverride\" of the Indexes "
"directive must be enabled in your httpd.conf file. Ask your hosting provider "
"to check this if you don't have access to httpd.conf"
msgstr ""
#: admin/wp-security-firewall-menu.php:393
msgid "Trace and Track"
msgstr ""
#: admin/wp-security-firewall-menu.php:402
#: classes/grade-system/wp-security-feature-item-manager.php:93
msgid "Disable Trace and Track"
msgstr ""
#: admin/wp-security-firewall-menu.php:405
msgid "Check this if you want to disable trace and track."
msgstr ""
#: admin/wp-security-firewall-menu.php:410
msgid ""
"HTTP Trace attack (XST) can be used to return header requests and grab "
"cookies and other information."
msgstr ""
#: admin/wp-security-firewall-menu.php:412
msgid ""
"This hacking technique is usually used together with cross site scripting "
"attacks (XSS)."
msgstr ""
#: admin/wp-security-firewall-menu.php:414
msgid ""
"Disabling trace and track on your site will help prevent HTTP Trace attacks."
msgstr ""
#: admin/wp-security-firewall-menu.php:423
msgid "Proxy Comment Posting"
msgstr ""
#: admin/wp-security-firewall-menu.php:433
msgid "Forbid Proxy Comment Posting"
msgstr ""
#: admin/wp-security-firewall-menu.php:436
msgid "Check this if you want to forbid proxy comment posting."
msgstr ""
#: admin/wp-security-firewall-menu.php:441
msgid ""
"This setting will deny any requests that use a proxy server when posting "
"comments."
msgstr ""
#: admin/wp-security-firewall-menu.php:442
msgid ""
"By forbidding proxy comments you are in effect eliminating some SPAM and "
"other proxy requests."
msgstr ""
#: admin/wp-security-firewall-menu.php:451
msgid "Bad Query Strings"
msgstr ""
#: admin/wp-security-firewall-menu.php:461
msgid "Deny Bad Query Strings"
msgstr ""
#: admin/wp-security-firewall-menu.php:464
msgid "This will help protect you against malicious queries via XSS."
msgstr ""
#: admin/wp-security-firewall-menu.php:469
msgid ""
"This feature will write rules in your .htaccess file to prevent malicious "
"string attacks on your site using XSS."
msgstr ""
#: admin/wp-security-firewall-menu.php:470
msgid ""
"NOTE: Some of these strings might be used for plugins or themes and hence "
"this might break some functionality."
msgstr ""
#: admin/wp-security-firewall-menu.php:471
#: admin/wp-security-firewall-menu.php:501
msgid ""
"You are therefore strongly advised to take a backup of your active .htaccess "
"file before applying this feature."
msgstr ""
#: admin/wp-security-firewall-menu.php:480
#: classes/grade-system/wp-security-feature-item-manager.php:96
msgid "Advanced Character String Filter"
msgstr ""
#: admin/wp-security-firewall-menu.php:490
msgid "Enable Advanced Character String Filter"
msgstr ""
#: admin/wp-security-firewall-menu.php:493
msgid "This will block bad character matches from XSS."
msgstr ""
#: admin/wp-security-firewall-menu.php:498
msgid ""
"This is an advanced character string filter to prevent malicious string "
"attacks on your site coming from Cross Site Scripting (XSS)."
msgstr ""
#: admin/wp-security-firewall-menu.php:499
msgid ""
"This setting matches for common malicious string patterns and exploits and "
"will produce a 403 error for the hacker attempting the query."
msgstr ""
#: admin/wp-security-firewall-menu.php:500
msgid "NOTE: Some strings for this setting might break some functionality."
msgstr ""
#: admin/wp-security-firewall-menu.php:509
msgid "Save Additional Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:552
msgid "You have successfully saved the 5G/6G Firewall Protection configuration"
msgstr ""
#: admin/wp-security-firewall-menu.php:567
#, php-format
msgid ""
"This feature allows you to activate the %s (or legacy %s) firewall security "
"protection rules designed and produced by %s."
msgstr ""
#: admin/wp-security-firewall-menu.php:568
msgid ""
"The 6G Blacklist is updated and improved version of 5G Blacklist. If you "
"have 5G Blacklist active, you might consider activating 6G Blacklist instead."
msgstr ""
#: admin/wp-security-firewall-menu.php:569
msgid ""
"The 6G Blacklist is a simple, flexible blacklist that helps reduce the "
"number of malicious URL requests that hit your website."
msgstr ""
#: admin/wp-security-firewall-menu.php:570
msgid ""
"The added advantage of applying the 6G firewall to your site is that it has "
"been tested and confirmed by the people at PerishablePress.com to be an "
"optimal and least disruptive set of .htaccess security rules for general WP "
"sites running on an Apache server or similar."
msgstr ""
#: admin/wp-security-firewall-menu.php:571
#, php-format
msgid ""
"Therefore the 6G firewall rules 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."
msgstr ""
#: admin/wp-security-firewall-menu.php:577
msgid "6G Blacklist/Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:589
msgid "Enable 6G Firewall Protection"
msgstr ""
#: admin/wp-security-firewall-menu.php:592
msgid ""
"Check this if you want to apply the 6G Blacklist firewall protection from "
"perishablepress.com to your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:596
msgid ""
"This setting will implement the 6G security firewall protection mechanisms "
"on your site which include the following things:"
msgstr ""
#: admin/wp-security-firewall-menu.php:597
#: admin/wp-security-firewall-menu.php:615
msgid "1) Block forbidden characters commonly used in exploitative attacks."
msgstr ""
#: admin/wp-security-firewall-menu.php:598
#: admin/wp-security-firewall-menu.php:616
msgid "2) Block malicious encoded URL characters such as the \".css(\" string."
msgstr ""
#: admin/wp-security-firewall-menu.php:599
#: admin/wp-security-firewall-menu.php:617
msgid ""
"3) Guard against the common patterns and specific exploits in the root "
"portion of targeted URLs."
msgstr ""
#: admin/wp-security-firewall-menu.php:600
#: admin/wp-security-firewall-menu.php:618
msgid ""
"4) Stop attackers from manipulating query strings by disallowing illicit "
"characters."
msgstr ""
#: admin/wp-security-firewall-menu.php:601
#: admin/wp-security-firewall-menu.php:619
msgid "....and much more."
msgstr ""
#: admin/wp-security-firewall-menu.php:607
msgid "Enable legacy 5G Firewall Protection"
msgstr ""
#: admin/wp-security-firewall-menu.php:610
msgid ""
"Check this if you want to apply the 5G Blacklist firewall protection from "
"perishablepress.com to your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:614
msgid ""
"This setting will implement the 5G security firewall protection mechanisms "
"on your site which include the following things:"
msgstr ""
#: admin/wp-security-firewall-menu.php:625
msgid "Save 5G/6G Firewall Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:656
msgid "The Internet bot settings were successfully saved"
msgstr ""
#: admin/wp-security-firewall-menu.php:660
msgid "Internet Bot Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:667
#, php-format
msgid "%s?"
msgstr ""
#: admin/wp-security-firewall-menu.php:669
msgid ""
"A bot is a piece of software which runs on the Internet and performs "
"automatic tasks. For example when Google indexes your pages it uses "
"automatic bots to achieve this task."
msgstr ""
#: admin/wp-security-firewall-menu.php:670
msgid ""
"A lot of bots are legitimate and non-malicous but not all bots are good and "
"often you will find some which try to impersonate legitimate bots such as "
"\"Googlebot\" but in reality they have nohing to do with Google at all."
msgstr ""
#: admin/wp-security-firewall-menu.php:671
msgid ""
"Although most of the bots out there are relatively harmless sometimes "
"website owners want to have more control over which bots they allow into "
"their site."
msgstr ""
#: admin/wp-security-firewall-menu.php:672
msgid ""
"This feature allows you to block bots which are impersonating as a Googlebot "
"but actually aren't. (In other words they are fake Google bots)"
msgstr ""
#: admin/wp-security-firewall-menu.php:673
msgid ""
"Googlebots have a unique indentity which cannot easily be forged and this "
"feature will indentify any fake Google bots and block them from reading your "
"site's pages."
msgstr ""
#: admin/wp-security-firewall-menu.php:679
msgid ""
"<strong>Attention</strong>: Sometimes non-malicious Internet organizations "
"might have bots which impersonate as a \"Googlebot\"."
msgstr ""
#: admin/wp-security-firewall-menu.php:680
msgid ""
"Just be aware that if you activate this feature the plugin will block all "
"bots which use the \"Googlebot\" string in their User Agent information but "
"are NOT officially from Google (irrespective whether they are malicious or "
"not)."
msgstr ""
#: admin/wp-security-firewall-menu.php:681
msgid ""
"All other bots from other organizations such as \"Yahoo\", \"Bing\" etc will "
"not be affected by this feature."
msgstr ""
#: admin/wp-security-firewall-menu.php:687
#: admin/wp-security-firewall-menu.php:697
#: classes/grade-system/wp-security-feature-item-manager.php:98
msgid "Block Fake Googlebots"
msgstr ""
#: admin/wp-security-firewall-menu.php:700
msgid "Check this if you want to block all fake Googlebots."
msgstr ""
#: admin/wp-security-firewall-menu.php:704
msgid ""
"This feature will check if the User Agent information of a bot contains the "
"string \"Googlebot\"."
msgstr ""
#: admin/wp-security-firewall-menu.php:705
msgid ""
"It will then perform a few tests to verify if the bot is legitimately from "
"Google and if so it will allow the bot to proceed."
msgstr ""
#: admin/wp-security-firewall-menu.php:706
msgid ""
"If the bot fails the checks then the plugin will mark it as being a fake "
"Googlebot and it will block it"
msgstr ""
#: admin/wp-security-firewall-menu.php:713
msgid "Save Internet Bot Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:750
#: admin/wp-security-firewall-menu.php:772
#: classes/grade-system/wp-security-feature-item-manager.php:32
msgid "Prevent Image Hotlinking"
msgstr ""
#: admin/wp-security-firewall-menu.php:753
msgid ""
"A Hotlink is where someone displays an image on their site which is actually "
"located on your site by using a direct link to the source of the image on "
"your server."
msgstr ""
#: admin/wp-security-firewall-menu.php:754
msgid ""
"Due to the fact that the image being displayed on the other person's site is "
"coming from your server, this can cause leaking of bandwidth and resources "
"for you because your server has to present this image for the people viewing "
"it on someone elses's site."
msgstr ""
#: admin/wp-security-firewall-menu.php:755
msgid ""
"This feature will prevent people from directly hotlinking images from your "
"site's pages by writing some directives in your .htaccess file."
msgstr ""
#: admin/wp-security-firewall-menu.php:760
msgid "Prevent Hotlinking"
msgstr ""
#: admin/wp-security-firewall-menu.php:775
msgid "Check this if you want to prevent hotlinking to images on your site."
msgstr ""
#: admin/wp-security-firewall-menu.php:795
msgid "Nonce check failed for delete all 404 event logs operation!"
msgstr ""
#: admin/wp-security-firewall-menu.php:806
msgid "404 Detection Feature - Delete all 404 event logs operation failed!"
msgstr ""
#: admin/wp-security-firewall-menu.php:810
msgid "All 404 event logs were deleted from the DB successfully!"
msgstr ""
#: admin/wp-security-firewall-menu.php:834
#: admin/wp-security-user-login-menu.php:111
msgid ""
"You entered a non numeric value for the lockout time length field. It has "
"been set to the default value."
msgstr ""
#: admin/wp-security-firewall-menu.php:840
msgid ""
"You entered an incorrect format for the \"Redirect URL\" field. It has been "
"set to the default value."
msgstr ""
#: admin/wp-security-firewall-menu.php:875
msgid "404 Detection Configuration"
msgstr ""
#: admin/wp-security-firewall-menu.php:878
msgid ""
"A 404 or Not Found error occurs when somebody tries to access a non-existent "
"page on your website."
msgstr ""
#: admin/wp-security-firewall-menu.php:879
msgid ""
"Typically, most 404 errors happen quite innocently when people have mis-"
"typed a URL or used an old link to page which doesn't exist anymore."
msgstr ""
#: admin/wp-security-firewall-menu.php:880
msgid ""
"However, in some cases you may find many repeated 404 errors which occur in "
"a relatively short space of time and from the same IP address which are all "
"attempting to access a variety of non-existent page URLs."
msgstr ""
#: admin/wp-security-firewall-menu.php:881
msgid ""
"Such behaviour can mean that a hacker might be trying to find a particular "
"page or URL for sinister reasons."
msgstr ""
#: admin/wp-security-firewall-menu.php:882
msgid ""
"This feature allows you to monitor all 404 events which occur on your site, "
"and it also gives you the option of blocking IP addresses for a configured "
"length of time."
msgstr ""
#: admin/wp-security-firewall-menu.php:883
msgid ""
"If you want to temporarily block an IP address, simply click the \"Temp Block"
"\" link for the applicable IP entry in the \"404 Event Logs\" table below."
msgstr ""
#: admin/wp-security-firewall-menu.php:890
msgid ""
"This addon allows you to automatically and permanently block IP addresses "
"based on how many 404 errors they produce."
msgstr ""
#: admin/wp-security-firewall-menu.php:898
msgid "404 Detection Options"
msgstr ""
#: admin/wp-security-firewall-menu.php:910
msgid "Enable 404 IP Detection and Lockout"
msgstr ""
#: admin/wp-security-firewall-menu.php:913
msgid "Check this if you want to enable the lockout of selected IP addresses."
msgstr ""
#: admin/wp-security-firewall-menu.php:918
msgid ""
"When you enable this checkbox, all 404 events on your site will be logged in "
"the table below. You can monitor these events and select some IP addresses "
"listed in the table below and block them for a specified amount of time. All "
"IP addresses you select to be blocked from the \"404 Event Logs\" table "
"section will be unable to access your site during the time specified."
msgstr ""
#: admin/wp-security-firewall-menu.php:926
msgid "Enable 404 Event Logging"
msgstr ""
#: admin/wp-security-firewall-menu.php:929
msgid "Check this if you want to enable the logging of 404 events"
msgstr ""
#: admin/wp-security-firewall-menu.php:934
msgid "Time Length of 404 Lockout (min)"
msgstr ""
#: admin/wp-security-firewall-menu.php:936
msgid ""
"Set the length of time for which a blocked IP address will be prevented from "
"visiting your site"
msgstr ""
#: admin/wp-security-firewall-menu.php:941
msgid ""
"You can lock any IP address which is recorded in the \"404 Event Logs\" "
"table section below."
msgstr ""
#: admin/wp-security-firewall-menu.php:943
msgid ""
"To temporarily lock an IP address, hover over the ID column and click the "
"\"Temp Block\" link for the applicable IP entry."
msgstr ""
#: admin/wp-security-firewall-menu.php:950
msgid "404 Lockout Redirect URL"
msgstr ""
#: admin/wp-security-firewall-menu.php:952
msgid "A blocked visitor will be automatically redirected to this URL."
msgstr ""
#: admin/wp-security-firewall-menu.php:961
msgid "404 Event Logs"
msgstr ""
#: admin/wp-security-firewall-menu.php:983
#: admin/wp-security-firewall-menu.php:992
msgid "Delete All 404 Event Logs"
msgstr ""
#: admin/wp-security-firewall-menu.php:989
msgid "Click this button if you wish to purge all 404 event logs from the DB."
msgstr ""
#: admin/wp-security-firewall-menu.php:1047
msgid "Custom .htaccess Rules Settings"
msgstr ""
#: admin/wp-security-firewall-menu.php:1054
msgid ""
"This feature can be used to apply your own custom .htaccess rules and "
"directives."
msgstr ""
#: admin/wp-security-firewall-menu.php:1055
msgid ""
"It is useful for when you want to tweak our existing firewall rules or when "
"you want to add your own."
msgstr ""
#: admin/wp-security-firewall-menu.php:1056
msgid ""
"NOTE: This feature can only used if your site is hosted in an apache or "
"similar web server."
msgstr ""
#: admin/wp-security-firewall-menu.php:1062
msgid ""
"<strong>Warning</strong>: Only use this feature if you know what you are "
"doing."
msgstr ""
#: admin/wp-security-firewall-menu.php:1063
msgid ""
"Incorrect .htaccess rules or directives can break or prevent access to your "
"site."
msgstr ""
#: admin/wp-security-firewall-menu.php:1064
msgid ""
"It is your responsibility to ensure that you are entering the correct code!"
msgstr ""
#: admin/wp-security-firewall-menu.php:1065
msgid ""
"If you break your site you will need to access your server via FTP or "
"something similar and then edit your .htaccess file and delete the changes "
"you made."
msgstr ""
#: admin/wp-security-firewall-menu.php:1071
msgid "Custom .htaccess Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:1075
msgid "Enable Custom .htaccess Rules"
msgstr ""
#: admin/wp-security-firewall-menu.php:1078
msgid ""
"Check this if you want to enable custom rules entered in the text box below"
msgstr ""
#: admin/wp-security-firewall-menu.php:1082
msgid "Enter Custom .htaccess Rules:"
msgstr ""
#: admin/wp-security-firewall-menu.php:1086
msgid "Enter your custom .htaccess rules/directives."
msgstr ""
#: admin/wp-security-firewall-menu.php:1091
msgid "Save Custom Rules"
msgstr ""
#: admin/wp-security-list-404.php:118 admin/wp-security-list-404.php:126
#: admin/wp-security-list-404.php:133
#: admin/wp-security-list-acct-activity.php:83
#: admin/wp-security-list-comment-spammer-ip.php:92
#: admin/wp-security-list-locked-ip.php:90
#: admin/wp-security-list-locked-ip.php:101
#: admin/wp-security-list-login-fails.php:82
#: admin/wp-security-list-permanent-blocked-ip.php:93
#: admin/wp-security-list-registered-users.php:101
#: admin/wp-security-list-registered-users.php:112
#: admin/wp-security-list-registered-users.php:123
msgid "Please select some records using the checkboxes"
msgstr ""
#: admin/wp-security-list-404.php:155 admin/wp-security-list-404.php:193
msgid ""
"Could not process the request because the IP addresses for the selected "
"entries could not be found!"
msgstr ""
#: admin/wp-security-list-404.php:164
msgid "The selected IP addresses are now temporarily blocked!"
msgstr ""
#: admin/wp-security-list-404.php:169
msgid "The selected IP address is now temporarily blocked!"
msgstr ""
#: admin/wp-security-list-404.php:171
msgid "The selected entry is not a valid IP address!"
msgstr ""
#: admin/wp-security-list-404.php:216
msgid ""
"The selected IP addresses have been added to the blacklist and will be "
"permanently blocked!"
msgstr ""
#: admin/wp-security-list-404.php:256
msgid "Nonce check failed for delete selected 404 event logs operation!"
msgstr ""
#: admin/wp-security-list-acct-activity.php:114
#: admin/wp-security-list-login-fails.php:114
msgid "The selected entries were deleted successfully!"
msgstr ""
#: admin/wp-security-list-acct-activity.php:126
msgid "Nonce check failed for delete selected account activity logs operation!"
msgstr ""
#: admin/wp-security-list-acct-activity.php:134
#: admin/wp-security-list-login-fails.php:134
msgid "The selected entry was deleted successfully!"
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:127
#: admin/wp-security-list-comment-spammer-ip.php:176
msgid "Nonce check failed for delete selected blocked IP operation!"
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:134
msgid "The selected IP addresses are now permanently blocked!"
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:190
msgid ""
"The selected IP addresses were saved in the blacklist configuration settings."
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:198
msgid ""
"The .htaccess file was successfully modified to include the selected IP "
"addresses."
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:209
msgid ""
"NOTE: The .htaccess file was not modified because you have disabled the "
"\"Enable IP or User Agent Blacklisting\" check box."
msgstr ""
#: admin/wp-security-list-comment-spammer-ip.php:210
#, php-format
msgid ""
"To block these IP addresses you will need to enable the above flag in the %s "
"menu"
msgstr ""
#: admin/wp-security-list-locked-ip.php:128
msgid "The selected IP entries were unlocked successfully!"
msgstr ""
#: admin/wp-security-list-locked-ip.php:137
msgid "Nonce check failed for unlock IP operation!"
msgstr ""
#: admin/wp-security-list-locked-ip.php:145
msgid "The selected IP entry was unlocked successfully!"
msgstr ""
#: admin/wp-security-list-locked-ip.php:179
msgid "Nonce check failed for delete lockdown record operation!"
msgstr ""
#: admin/wp-security-list-logged-in-users.php:84
msgid "Nonce check failed for force user logout operation!"
msgstr ""
#: admin/wp-security-list-logged-in-users.php:95
msgid "The selected user was logged out successfully!"
msgstr ""
#: admin/wp-security-list-login-fails.php:126
msgid "Nonce check failed for delete failed login record operation!"
msgstr ""
#: admin/wp-security-list-permanent-blocked-ip.php:123
msgid "Nonce check failed for unblock IP operation!"
msgstr ""
#: admin/wp-security-list-registered-users.php:48
msgid "blocked"
msgstr ""
#: admin/wp-security-list-registered-users.php:157
#: admin/wp-security-list-registered-users.php:187
msgid "Your account is now active"
msgstr ""
#: admin/wp-security-list-registered-users.php:158
msgid "Your account with user ID:"
msgstr ""
#: admin/wp-security-list-registered-users.php:158
#: admin/wp-security-list-registered-users.php:188
msgid " is now active"
msgstr ""
#: admin/wp-security-list-registered-users.php:171
msgid "The selected accounts were approved successfully!"
msgstr ""
#: admin/wp-security-list-registered-users.php:175
msgid "The following accounts failed to update successfully: "
msgstr ""
#: admin/wp-security-list-registered-users.php:183
msgid "The selected account was approved successfully!"
msgstr ""
#: admin/wp-security-list-registered-users.php:188
msgid "Your account with username: "
msgstr ""
#: admin/wp-security-list-registered-users.php:220
msgid "The selected accounts were deleted successfully!"
msgstr ""
#: admin/wp-security-list-registered-users.php:228
msgid "Nonce check failed for delete registered user account operation!"
msgstr ""
#: admin/wp-security-list-registered-users.php:236
msgid "The selected account was deleted successfully!"
msgstr ""
#: admin/wp-security-list-registered-users.php:262
msgid ""
"The selected IP addresses were successfully added to the permanent block "
"list!"
msgstr ""
#: admin/wp-security-list-registered-users.php:263
#: admin/wp-security-list-registered-users.php:280
#: admin/wp-security-spam-menu.php:319
msgid "View Blocked IPs"
msgstr ""
#: admin/wp-security-list-registered-users.php:272
msgid "Nonce check failed for block IP operation of registered user!"
msgstr ""
#: admin/wp-security-list-registered-users.php:279
msgid "The selected IP was successfully added to the permanent block list!"
msgstr ""
#: admin/wp-security-maintenance-menu.php:22
msgid "Visitor Lockout"
msgstr ""
#: admin/wp-security-maintenance-menu.php:89
msgid "Site lockout feature settings saved!"
msgstr ""
#: admin/wp-security-maintenance-menu.php:94
msgid "General Visitor Lockout"
msgstr ""
#: admin/wp-security-maintenance-menu.php:100
msgid ""
"This feature allows you to put your site into \"maintenance mode\" by "
"locking down the front-end to all visitors except logged in users with super "
"admin privileges."
msgstr ""
#: admin/wp-security-maintenance-menu.php:101
msgid ""
"Locking your site down to general visitors can be useful if you are "
"investigating some issues on your site or perhaps you might be doing some "
"maintenance and wish to keep out all traffic for security reasons."
msgstr ""
#: admin/wp-security-maintenance-menu.php:106
msgid "Enable Front-end Lockout"
msgstr ""
#: admin/wp-security-maintenance-menu.php:109
msgid ""
"Check this if you want all visitors except those who are logged in as "
"administrator to be locked out of the front-end of your site."
msgstr ""
#: admin/wp-security-maintenance-menu.php:113
msgid "Enter a Message:"
msgstr ""
#: admin/wp-security-maintenance-menu.php:125
msgid ""
"Enter a message you wish to display to visitors when your site is in "
"maintenance mode."
msgstr ""
#: admin/wp-security-maintenance-menu.php:132
msgid "Save Site Lockout Settings"
msgstr ""
#: admin/wp-security-misc-options-menu.php:24
msgid "Copy Protection"
msgstr ""
#: admin/wp-security-misc-options-menu.php:25
msgid "Frames"
msgstr ""
#: admin/wp-security-misc-options-menu.php:26
msgid "Users Enumeration"
msgstr ""
#: admin/wp-security-misc-options-menu.php:91
msgid "Copy Protection feature settings saved!"
msgstr ""
#: admin/wp-security-misc-options-menu.php:96
msgid "Disable The Ability To Copy Text"
msgstr ""
#: admin/wp-security-misc-options-menu.php:102
msgid ""
"This feature allows you to disable the ability to select and copy text from "
"your front end."
msgstr ""
#: admin/wp-security-misc-options-menu.php:103
msgid ""
"When admin user is logged in, the feature is automatically disabled for his "
"session."
msgstr ""
#: admin/wp-security-misc-options-menu.php:108
msgid "Enable Copy Protection"
msgstr ""
#: admin/wp-security-misc-options-menu.php:111
msgid ""
"Check this if you want to disable the \"Right Click\", \"Text Selection\" "
"and \"Copy\" option on the front end of your site."
msgstr ""
#: admin/wp-security-misc-options-menu.php:118
msgid "Save Copy Protection Settings"
msgstr ""
#: admin/wp-security-misc-options-menu.php:142
msgid "Frame Display Prevention feature settings saved!"
msgstr ""
#: admin/wp-security-misc-options-menu.php:147
msgid "Prevent Your Site From Being Displayed In a Frame"
msgstr ""
#: admin/wp-security-misc-options-menu.php:153
msgid ""
"This feature allows you to prevent other sites from displaying any of your "
"content via a frame or iframe."
msgstr ""
#: admin/wp-security-misc-options-menu.php:154
msgid ""
"When enabled, this feature will set the \"X-Frame-Options\" paramater to "
"\"sameorigin\" in the HTTP header."
msgstr ""
#: admin/wp-security-misc-options-menu.php:159
msgid "Enable iFrame Protection"
msgstr ""
#: admin/wp-security-misc-options-menu.php:162
msgid ""
"Check this if you want to stop other sites from displaying your content in a "
"frame or iframe."
msgstr ""
#: admin/wp-security-misc-options-menu.php:193
msgid "Users Enumeration Prevention feature settings saved!"
msgstr ""
#: admin/wp-security-misc-options-menu.php:198
msgid "Prevent Users Enumeration"
msgstr ""
#: admin/wp-security-misc-options-menu.php:204
msgid ""
"This feature allows you to prevent external users/bots from fetching the "
"user info with urls like \"/?author=1\"."
msgstr ""
#: admin/wp-security-misc-options-menu.php:205
msgid ""
"When enabled, this feature will print a \"forbidden\" error rather than the "
"user information."
msgstr ""
#: admin/wp-security-misc-options-menu.php:210
msgid "Disable Users Enumeration"
msgstr ""
#: admin/wp-security-misc-options-menu.php:213
msgid "Check this if you want to stop users enumeration."
msgstr ""
#: admin/wp-security-settings-menu.php:26
msgid "General Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:29
msgid "WP Version Info"
msgstr ""
#: admin/wp-security-settings-menu.php:30
msgid "Import/Export"
msgstr ""
#: admin/wp-security-settings-menu.php:98
msgid "All the security features have been disabled successfully!"
msgstr ""
#: admin/wp-security-settings-menu.php:102
#: admin/wp-security-settings-menu.php:129
msgid ""
"Could not write to the .htaccess file. Please restore your .htaccess file "
"manually using the restore functionality in the \".htaccess File\"."
msgstr ""
#: admin/wp-security-settings-menu.php:107
msgid ""
"Could not write to the wp-config.php. Please restore your wp-config.php file "
"manually using the restore functionality in the \"wp-config.php File\"."
msgstr ""
#: admin/wp-security-settings-menu.php:125
msgid "All firewall rules have been disabled successfully!"
msgstr ""
#: admin/wp-security-settings-menu.php:154
msgid "WP Security Plugin"
msgstr ""
#: admin/wp-security-settings-menu.php:156
msgid ""
"Thank you for using our WordPress security plugin. There are a lot of "
"security features in this plugin."
msgstr ""
#: admin/wp-security-settings-menu.php:157
msgid ""
"Go through each menu items and enable the security options to add more "
"security to your site. Start by activating the basic features first."
msgstr ""
#: admin/wp-security-settings-menu.php:158
msgid ""
"It is a good practice to take a backup of your .htaccess file, database and "
"wp-config.php file before activating the security features. This plugin has "
"options that you can use to backup those resources easily."
msgstr ""
#: admin/wp-security-settings-menu.php:161
msgid "Backup your database"
msgstr ""
#: admin/wp-security-settings-menu.php:162
msgid "Backup .htaccess file"
msgstr ""
#: admin/wp-security-settings-menu.php:163
msgid "Backup wp-config.php file"
msgstr ""
#: admin/wp-security-settings-menu.php:170
msgid "Disable Security Features"
msgstr ""
#: admin/wp-security-settings-menu.php:176
msgid ""
"If you think that some plugin functionality on your site is broken due to a "
"security feature you enabled in this plugin, then use the following option "
"to turn off all the security features of this plugin."
msgstr ""
#: admin/wp-security-settings-menu.php:180
msgid "Disable All Security Features"
msgstr ""
#: admin/wp-security-settings-menu.php:187
#: admin/wp-security-settings-menu.php:197
msgid "Disable All Firewall Rules"
msgstr ""
#: admin/wp-security-settings-menu.php:193
msgid ""
"This feature will disable all firewall rules which are currently active in "
"this plugin and it will also delete these rules from your .htacess file. Use "
"it if you think one of the firewall rules is causing an issue on your site."
msgstr ""
#: admin/wp-security-settings-menu.php:204
msgid "Debug Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:210
msgid "This setting allows you to enable/disable debug for this plugin."
msgstr ""
#: admin/wp-security-settings-menu.php:216
msgid "Enable Debug"
msgstr ""
#: admin/wp-security-settings-menu.php:219
msgid ""
"Check this if you want to enable debug. You should keep this option disabled "
"after you have finished debugging the issue."
msgstr ""
#: admin/wp-security-settings-menu.php:220
msgid "Please note that the log files are reset on every plugin update."
msgstr ""
#: admin/wp-security-settings-menu.php:224
msgid "Save Debug Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:253
msgid ""
"Your .htaccess file was successfully backed up! Using an FTP program go to "
"the \"/wp-content/aiowps_backups\" directory to save a copy of the file to "
"your computer."
msgstr ""
#: admin/wp-security-settings-menu.php:259
msgid ""
"htaccess file rename failed during backup. Please check your root directory "
"for the backup file using FTP."
msgstr ""
#: admin/wp-security-settings-menu.php:265
msgid "htaccess backup failed."
msgstr ""
#: admin/wp-security-settings-menu.php:280
msgid "Please choose a .htaccess to restore from."
msgstr ""
#: admin/wp-security-settings-menu.php:296
msgid ""
"htaccess file restore failed. Please attempt to restore the .htaccess "
"manually using FTP."
msgstr ""
#: admin/wp-security-settings-menu.php:300
msgid "Your .htaccess file has successfully been restored!"
msgstr ""
#: admin/wp-security-settings-menu.php:306
msgid ""
"htaccess Restore operation failed! Please check the contents of the file you "
"are trying to restore from."
msgstr ""
#: admin/wp-security-settings-menu.php:312
msgid ".htaccess File Operations"
msgstr ""
#: admin/wp-security-settings-menu.php:315
msgid ""
"Your \".htaccess\" file is a key component of your website's security and it "
"can be modified to implement various levels of protection mechanisms."
msgstr ""
#: admin/wp-security-settings-menu.php:316
msgid ""
"This feature allows you to backup and save your currently active .htaccess "
"file should you need to re-use the the backed up file in the future."
msgstr ""
#: admin/wp-security-settings-menu.php:317
msgid ""
"You can also restore your site's .htaccess settings using a backed up ."
"htaccess file."
msgstr ""
#: admin/wp-security-settings-menu.php:331
msgid "Save the current .htaccess file"
msgstr ""
#: admin/wp-security-settings-menu.php:335
msgid ""
"Click the button below to backup and save the currently active .htaccess "
"file."
msgstr ""
#: admin/wp-security-settings-menu.php:336
msgid "Backup .htaccess File"
msgstr ""
#: admin/wp-security-settings-menu.php:340
msgid "Restore from a backed up .htaccess file"
msgstr ""
#: admin/wp-security-settings-menu.php:346
msgid ".htaccess file to restore from"
msgstr ""
#: admin/wp-security-settings-menu.php:352
msgid ""
"After selecting your file, click the button below to restore your site using "
"the backed up htaccess file (htaccess_backup.txt)."
msgstr ""
#: admin/wp-security-settings-menu.php:358
msgid "Restore .htaccess File"
msgstr ""
#: admin/wp-security-settings-menu.php:391
msgid "Please choose a wp-config.php file to restore from."
msgstr ""
#: admin/wp-security-settings-menu.php:407
msgid ""
"wp-config.php file restore failed. Please attempt to restore this file "
"manually using FTP."
msgstr ""
#: admin/wp-security-settings-menu.php:411
msgid "Your wp-config.php file has successfully been restored!"
msgstr ""
#: admin/wp-security-settings-menu.php:417
msgid ""
"wp-config.php Restore operation failed! Please check the contents of the "
"file you are trying to restore from."
msgstr ""
#: admin/wp-security-settings-menu.php:423
msgid "wp-config.php File Operations"
msgstr ""
#: admin/wp-security-settings-menu.php:426
msgid ""
"Your \"wp-config.php\" file is one of the most important in your WordPress "
"installation. It is a primary configuration file and contains crucial things "
"such as details of your database and other critical components."
msgstr ""
#: admin/wp-security-settings-menu.php:427
msgid ""
"This feature allows you to backup and save your currently active wp-config."
"php file should you need to re-use the the backed up file in the future."
msgstr ""
#: admin/wp-security-settings-menu.php:428
msgid ""
"You can also restore your site's wp-config.php settings using a backed up wp-"
"config.php file."
msgstr ""
#: admin/wp-security-settings-menu.php:442
msgid "Save the current wp-config.php file"
msgstr ""
#: admin/wp-security-settings-menu.php:446
msgid ""
"Click the button below to backup and download the contents of the currently "
"active wp-config.php file."
msgstr ""
#: admin/wp-security-settings-menu.php:447
msgid "Backup wp-config.php File"
msgstr ""
#: admin/wp-security-settings-menu.php:452
msgid "Restore from a backed up wp-config file"
msgstr ""
#: admin/wp-security-settings-menu.php:458
msgid "wp-config file to restore from"
msgstr ""
#: admin/wp-security-settings-menu.php:464
msgid ""
"After selecting your file click the button below to restore your site using "
"the backed up wp-config file (wp-config.php.backup.txt)."
msgstr ""
#: admin/wp-security-settings-menu.php:470
msgid "Restore wp-config File"
msgstr ""
#: admin/wp-security-settings-menu.php:509
msgid "WP Generator Meta Tag & Version Info"
msgstr ""
#: admin/wp-security-settings-menu.php:512
msgid ""
"Wordpress generator automatically adds some meta information inside the "
"\"head\" tags of every page on your site's front end. Below is an example of "
"this:"
msgstr ""
#: admin/wp-security-settings-menu.php:514
msgid ""
"The above meta information shows which version of WordPress your site is "
"currently running and thus can help hackers or crawlers scan your site to "
"see if you have an older version of WordPress or one with a known exploit."
msgstr ""
#: admin/wp-security-settings-menu.php:515
msgid ""
"There are also other ways wordpress reveals version info such as during "
"style and script loading. An example of this is:"
msgstr ""
#: admin/wp-security-settings-menu.php:517
msgid ""
"This feature will allow you to remove the WP generator meta info and other "
"version info from your site's pages."
msgstr ""
#: admin/wp-security-settings-menu.php:523
msgid "WP Generator Meta Info"
msgstr ""
#: admin/wp-security-settings-menu.php:535
msgid "Remove WP Generator Meta Info"
msgstr ""
#: admin/wp-security-settings-menu.php:538
msgid ""
"Check this if you want to remove the version and meta info produced by WP "
"from all pages"
msgstr ""
#: admin/wp-security-settings-menu.php:568
msgid "Please choose a file to import your settings from."
msgstr ""
#: admin/wp-security-settings-menu.php:600
msgid "Import AIOWPS settings from "
msgstr ""
#: admin/wp-security-settings-menu.php:606
#: admin/wp-security-settings-menu.php:650
msgid ""
"The deletion of the import file failed. Please delete this file manually via "
"the media menu for security purposes."
msgstr ""
#: admin/wp-security-settings-menu.php:608
#: admin/wp-security-settings-menu.php:652
msgid ""
"The file you uploaded was also deleted for security purposes because it "
"contains security settings details."
msgstr ""
#: admin/wp-security-settings-menu.php:623
msgid "Your AIOWPS settings were successfully imported via file input."
msgstr ""
#: admin/wp-security-settings-menu.php:624
msgid ""
"The deletion of the import file failed. Please delete this file manually via "
"the media menu for security purposes because it contains security settings "
"details."
msgstr ""
#: admin/wp-security-settings-menu.php:626
msgid ""
"Your AIOWPS settings were successfully imported. The file you uploaded was "
"also deleted for security purposes because it contains security settings "
"details."
msgstr ""
#: admin/wp-security-settings-menu.php:629
msgid "Your AIOWPS settings were successfully imported via text entry."
msgstr ""
#: admin/wp-security-settings-menu.php:644
msgid ""
"The contents of your settings file appear invalid. Please check the contents "
"of the file you are trying to import settings from."
msgstr ""
#: admin/wp-security-settings-menu.php:661
msgid "Export or Import Your AIOWPS Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:664
msgid ""
"This section allows you to export or import your All In One WP Security & "
"Firewall settings."
msgstr ""
#: admin/wp-security-settings-menu.php:665
msgid ""
"This can be handy if you wanted to save time by applying the settings from "
"one site to another site."
msgstr ""
#: admin/wp-security-settings-menu.php:666
msgid ""
"NOTE: Before importing, it is your responsibility to know what settings you "
"are trying to import. Importing settings blindly can cause you to be locked "
"out of your site."
msgstr ""
#: admin/wp-security-settings-menu.php:667
msgid ""
"For Example: If a settings item relies on the domain URL then it may not "
"work correctly when imported into a site with a different domain."
msgstr ""
#: admin/wp-security-settings-menu.php:673
#: admin/wp-security-settings-menu.php:682
msgid "Export AIOWPS Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:679
msgid ""
"To export your All In One WP Security & Firewall settings click the button "
"below."
msgstr ""
#: admin/wp-security-settings-menu.php:686
#: admin/wp-security-settings-menu.php:711
msgid "Import AIOWPS Settings"
msgstr ""
#: admin/wp-security-settings-menu.php:692
msgid ""
"Use this section to import your All In One WP Security & Firewall settings "
"from a file. Alternatively, copy/paste the contents of your import file into "
"the textarea below."
msgstr ""
#: admin/wp-security-settings-menu.php:693
msgid "Import File"
msgstr ""
#: admin/wp-security-settings-menu.php:699
msgid ""
"After selecting your file, click the button below to apply the settings to "
"your site."
msgstr ""
#: admin/wp-security-settings-menu.php:705
msgid "Copy/Paste Import Data"
msgstr ""
#: admin/wp-security-spam-menu.php:24
msgid "Comment SPAM"
msgstr ""
#: admin/wp-security-spam-menu.php:25
msgid "Comment SPAM IP Monitoring"
msgstr ""
#: admin/wp-security-spam-menu.php:26
msgid "BuddyPress"
msgstr ""
#: admin/wp-security-spam-menu.php:114
msgid "Comment SPAM Settings"
msgstr ""
#: admin/wp-security-spam-menu.php:119
msgid "Add Captcha To Comments Form"
msgstr ""
#: admin/wp-security-spam-menu.php:123
msgid ""
"This feature will add a simple math captcha field in the WordPress comments "
"form."
msgstr ""
#: admin/wp-security-spam-menu.php:124
msgid ""
"Adding a captcha field in the comment form is a simple way of greatly "
"reducing SPAM comments from bots without using .htaccess rules."
msgstr ""
#: admin/wp-security-spam-menu.php:133
msgid "Enable Captcha On Comment Forms"
msgstr ""
#: admin/wp-security-spam-menu.php:136
msgid "Check this if you want to insert a captcha field on the comment forms"
msgstr ""
#: admin/wp-security-spam-menu.php:143
msgid "Block Spambot Comments"
msgstr ""
#: admin/wp-security-spam-menu.php:147
msgid ""
"A large portion of WordPress blog comment SPAM is mainly produced by "
"automated bots and not necessarily by humans. "
msgstr ""
#: admin/wp-security-spam-menu.php:148
msgid ""
"This feature will greatly minimize the useless and unecessary traffic and "
"load on your server resulting from SPAM comments by blocking all comment "
"requests which do not originate from your domain."
msgstr ""
#: admin/wp-security-spam-menu.php:149
msgid ""
"In other words, if the comment was not submitted by a human who physically "
"submitted the comment on your site, the request will be blocked."
msgstr ""
#: admin/wp-security-spam-menu.php:165
msgid "Block Spambots From Posting Comments"
msgstr ""
#: admin/wp-security-spam-menu.php:168
msgid ""
"Check this if you want to apply a firewall rule which will block comments "
"originating from spambots."
msgstr ""
#: admin/wp-security-spam-menu.php:172
msgid ""
"This feature will implement a firewall rule to block all comment attempts "
"which do not originate from your domain."
msgstr ""
#: admin/wp-security-spam-menu.php:173
msgid ""
"A legitimate comment is one which is submitted by a human who physically "
"fills out the comment form and clicks the submit button. For such events, "
"the HTTP_REFERRER is always set to your own domain."
msgstr ""
#: admin/wp-security-spam-menu.php:174
msgid ""
"A comment submitted by a spambot is done by directly calling the comments."
"php file, which usually means that the HTTP_REFERRER value is not your "
"domain and often times empty."
msgstr ""
#: admin/wp-security-spam-menu.php:175
msgid ""
"This feature will check and block comment requests which are not referred by "
"your domain thus greatly reducing your overall blog SPAM and PHP requests "
"done by the server to process these comments."
msgstr ""
#: admin/wp-security-spam-menu.php:210
msgid ""
"You entered a non numeric value for the minimum number of spam comments "
"field. It has been set to the default value."
msgstr ""
#: admin/wp-security-spam-menu.php:213
msgid ""
"You must enter an integer greater than zero for minimum number of spam "
"comments field. It has been set to the default value."
msgstr ""
#: admin/wp-security-spam-menu.php:242
msgid "Nonce check failed for list SPAM comment IPs!"
msgstr ""
#: admin/wp-security-spam-menu.php:248
msgid ""
"You entered a non numeric value for the minimum SPAM comments per IP field. "
"It has been set to the default value."
msgstr ""
#: admin/wp-security-spam-menu.php:260
#, php-format
msgid ""
"Displaying results for IP addresses which have posted a minimum of %s SPAM "
"comments"
msgstr ""
#: admin/wp-security-spam-menu.php:275
msgid "Auto Block SPAMMER IPs"
msgstr ""
#: admin/wp-security-spam-menu.php:280
#, php-format
msgid ""
"This feature has detected that %s is not active. It is highly recommended "
"that you activate the Akismet plugin to make the most of this feature."
msgstr ""
#: admin/wp-security-spam-menu.php:289
msgid ""
"This feature allows you to automatically and permanently block IP addresses "
"which have exceeded a certain number of comments labelled as SPAM."
msgstr ""
#: admin/wp-security-spam-menu.php:290
msgid ""
"Comments are usually labelled as SPAM either by the Akismet plugin or "
"manually by the WP administrator when they mark a comment as \"spam\" from "
"the WordPress Comments menu."
msgstr ""
#: admin/wp-security-spam-menu.php:304
msgid "You currently have no IP addresses permanently blocked due to SPAM."
msgstr ""
#: admin/wp-security-spam-menu.php:317
msgid "Spammer IPs Added To Permanent Block List Today: "
msgstr ""
#: admin/wp-security-spam-menu.php:318
msgid "All Time Total: "
msgstr ""
#: admin/wp-security-spam-menu.php:332
msgid "Enable Auto Block of SPAM Comment IPs"
msgstr ""
#: admin/wp-security-spam-menu.php:335
msgid ""
"Check this box if you want this plugin to automatically block IP addresses "
"which submit SPAM comments."
msgstr ""
#: admin/wp-security-spam-menu.php:339
msgid "Minimum number of SPAM comments"
msgstr ""
#: admin/wp-security-spam-menu.php:341
msgid ""
"Specify the minimum number of SPAM comments for an IP address before it is "
"permanently blocked."
msgstr ""
#: admin/wp-security-spam-menu.php:345
msgid ""
"Example 1: Setting this value to \"1\" will block ALL IP addresses which "
"were used to submit at least one SPAM comment."
msgstr ""
#: admin/wp-security-spam-menu.php:346
msgid ""
"Example 2: Setting this value to \"5\" will block only those IP addresses "
"which were used to submit 5 SPAM comments or more on your site."
msgstr ""
#: admin/wp-security-spam-menu.php:364
msgid "List SPAMMER IP Addresses"
msgstr ""
#: admin/wp-security-spam-menu.php:368
msgid ""
"This section displays a list of the IP addresses of the people or bots who "
"have left SPAM comments on your site."
msgstr ""
#: admin/wp-security-spam-menu.php:369
msgid ""
"This information can be handy for identifying the most persistent IP "
"addresses or ranges used by spammers."
msgstr ""
#: admin/wp-security-spam-menu.php:370
msgid ""
"By inspecting the IP address data coming from spammers you will be in a "
"better position to determine which addresses or address ranges you should "
"block by adding them to your blacklist."
msgstr ""
#: admin/wp-security-spam-menu.php:371
msgid ""
"To add one or more of the IP addresses displayed in the table below to your "
"blacklist, simply click the \"Block\" link for the individual row or select "
"more than one address\n"
" using the checkboxes and then choose the \"block"
"\" option from the Bulk Actions dropdown list and click the \"Apply\" button."
msgstr ""
#: admin/wp-security-spam-menu.php:381
msgid "Minimum number of SPAM comments per IP"
msgstr ""
#: admin/wp-security-spam-menu.php:383
msgid ""
"This field allows you to list only those IP addresses which have been used "
"to post X or more SPAM comments."
msgstr ""
#: admin/wp-security-spam-menu.php:387
msgid ""
"Example 1: Setting this value to \"0\" or \"1\" will list ALL IP addresses "
"which were used to submit SPAM comments."
msgstr ""
#: admin/wp-security-spam-menu.php:388
msgid ""
"Example 2: Setting this value to \"5\" will list only those IP addresses "
"which were used to submit 5 SPAM comments or more on your site."
msgstr ""
#: admin/wp-security-spam-menu.php:395
msgid "Find IP Addresses"
msgstr ""
#: admin/wp-security-spam-menu.php:399
msgid "SPAMMER IP Address Results"
msgstr ""
#: admin/wp-security-spam-menu.php:405 classes/wp-security-utility.php:225
msgid ""
"The plugin has detected that you are using a Multi-Site WordPress "
"installation."
msgstr ""
#: admin/wp-security-spam-menu.php:406
msgid "Only the \"superadmin\" can block IP addresses from the main site."
msgstr ""
#: admin/wp-security-spam-menu.php:407
msgid ""
"Take note of the IP addresses you want blocked and ask the superadmin to add "
"these to the blacklist using the \"Blacklist Manager\" on the main site."
msgstr ""
#: admin/wp-security-spam-menu.php:452
msgid "BuddyPress SPAM Settings"
msgstr ""
#: admin/wp-security-spam-menu.php:457
msgid "Add Captcha To BuddyPress Registration Form"
msgstr ""
#: admin/wp-security-spam-menu.php:461
msgid ""
"This feature will add a simple math captcha field in the BuddyPress "
"registration form."
msgstr ""
#: admin/wp-security-spam-menu.php:462
msgid ""
"Adding a captcha field in the registration form is a simple way of greatly "
"reducing SPAM signups from bots without using .htaccess rules."
msgstr ""
#: admin/wp-security-spam-menu.php:472
msgid "Enable Captcha On BuddyPress Registration Form"
msgstr ""
#: admin/wp-security-spam-menu.php:475
msgid ""
"Check this if you want to insert a captcha field on the BuddyPress "
"registration forms"
msgstr ""
#: admin/wp-security-spam-menu.php:484
msgid ""
"BuddyPress is not active! In order to use this feature you will need to have "
"BuddyPress installed and activated."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:29
msgid "WP Username"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:30
msgid "Display Name"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:31
#: other-includes/wp-security-rename-login-feature.php:915
msgid "Password"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:86
msgid "Admin User Security"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:89
msgid ""
"By default, WordPress sets the administrator username to \"admin\" at "
"installation time."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:90
msgid ""
"A lot of hackers try to take advantage of this information by attempting "
"\"Brute Force Login Attacks\" where they repeatedly try to guess the "
"password by using \"admin\" for username."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:91
msgid ""
"From a security perspective, changing the default \"admin\" user name is one "
"of the first and smartest things you should do on your site."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:92
msgid ""
"This feature will allow you to change your default \"admin\" user name to a "
"more secure name of your choosing."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:99
msgid "List of Administrator Accounts"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:108
#: classes/grade-system/wp-security-feature-item-manager.php:36
msgid "Change Admin Username"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:116
msgid ""
"Your site currently has an account which uses the default \"admin\" "
"username. \n"
" It is highly recommended that you change this name to "
"something else. \n"
" Use the following field to change the admin username."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:124
msgid "New Admin Username"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:126
msgid "Choose a new username for admin."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:130
msgid "Change Username"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:132
msgid ""
"NOTE: If you are currently logged in as \"admin\" you will be automatically "
"logged out after changing your username and will be required to log back in."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:139
msgid "No action required! "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:141
msgid ""
"Your site does not have any account which uses the default \"admin\" "
"username. "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:142
msgid "This is good security practice."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:154
msgid "Display Name Security"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:157
msgid ""
"When you submit a post or answer a comment, WordPress will usually display "
"your \"nickname\"."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:158
msgid ""
"By default the nickname is set to the login (or user) name of your account."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:159
msgid ""
"From a security perspective, leaving your nickname the same as your user "
"name is bad practice because it gives a hacker at least half of your "
"account's login credentials."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:160
msgid ""
"Therefore to further tighten your site's security you are advised to change "
"your <strong>nickname</strong> and <strong>Display name</strong> to be "
"different from your <strong>Username</strong>."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:166
msgid "Modify Accounts With Identical Login Name & Display Name"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:175
msgid ""
"Your site currently has the following accounts which have an identical login "
"name and display name."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:176
msgid "Click on the link to edit the settings of that particular user account"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:191
msgid "No action required."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:192
msgid ""
"Your site does not have a user account where the display name is identical "
"to the username."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:203
msgid "Password Tool"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:206
msgid ""
"Poor password selection is one of the most common weak points of many sites "
"and is usually the first thing a hacker will try to exploit when attempting "
"to break into your site."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:207
msgid ""
"Many people fall into the trap of using a simple word or series of numbers "
"as their password. Such a predictable and simple password would take a "
"competent hacker merely minutes to guess your password by using a simple "
"script which cycles through the easy and most common combinations."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:208
msgid ""
"The longer and more complex your password is the harder it is for hackers to "
"\"crack\" because more complex passwords require much greater computing "
"power and time."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:209
msgid ""
"This section contains a useful password strength tool which you can use to "
"check whether your password is sufficiently strong enough."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:214
msgid "Password Strength Tool"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:219
msgid "Start typing a password."
msgstr ""
#: admin/wp-security-user-accounts-menu.php:222
msgid "It would take a desktop PC approximately"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:223
msgid "1 sec"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:223
msgid "to crack your password!"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:228
msgid "Password Strength"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:244
msgid "Nonce check failed on admin username change operation!"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:251
msgid "Username "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:251
msgid " already exists. Please enter another value. "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:268
msgid "The database update operation of the user account failed!"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:297
msgid "You entered an invalid username. Please enter another value. "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:301
msgid "Please enter a value for your username. "
msgstr ""
#: admin/wp-security-user-accounts-menu.php:308
msgid "Username Successfully Changed!"
msgstr ""
#: admin/wp-security-user-accounts-menu.php:328
msgid "Account Login Name"
msgstr ""
#: admin/wp-security-user-login-menu.php:26
#: admin/wp-security-user-login-menu.php:325
msgid "Failed Login Records"
msgstr ""
#: admin/wp-security-user-login-menu.php:27
#: classes/grade-system/wp-security-feature-item-manager.php:51
msgid "Force Logout"
msgstr ""
#: admin/wp-security-user-login-menu.php:28
#: admin/wp-security-user-login-menu.php:459
msgid "Account Activity Logs"
msgstr ""
#: admin/wp-security-user-login-menu.php:97
msgid ""
"You entered a non numeric value for the max login attempts field. It has "
"been set to the default value."
msgstr ""
#: admin/wp-security-user-login-menu.php:104
msgid ""
"You entered a non numeric value for the login retry time period field. It "
"has been set to the default value."
msgstr ""
#: admin/wp-security-user-login-menu.php:176
msgid "Login Lockdown Configuration"
msgstr ""
#: admin/wp-security-user-login-menu.php:180
msgid "One of the ways hackers try to compromise sites is via a "
msgstr ""
#: admin/wp-security-user-login-menu.php:180
msgid "Brute Force Login Attack"
msgstr ""
#: admin/wp-security-user-login-menu.php:180
msgid ""
"This is where attackers use repeated login attempts until they guess the "
"password."
msgstr ""
#: admin/wp-security-user-login-menu.php:181
msgid ""
"Apart from choosing strong passwords, monitoring and blocking IP addresses "
"which are involved in repeated login failures in a short period of time is a "
"very effective way to stop these types of attacks."
msgstr ""
#: admin/wp-security-user-login-menu.php:182
#, php-format
msgid ""
"You may also want to checkout our %s feature for another secure way to "
"protect against these types of attacks."
msgstr ""
#: admin/wp-security-user-login-menu.php:187
msgid "Login Lockdown Options"
msgstr ""
#: admin/wp-security-user-login-menu.php:198
msgid "Enable Login Lockdown Feature"
msgstr ""
#: admin/wp-security-user-login-menu.php:201
msgid ""
"Check this if you want to enable the login lockdown feature and apply the "
"settings below"
msgstr ""
#: admin/wp-security-user-login-menu.php:205
msgid "Allow Unlock Requests"
msgstr ""
#: admin/wp-security-user-login-menu.php:208
msgid ""
"Check this if you want to allow users to generate an automated unlock "
"request link which will unlock their account"
msgstr ""
#: admin/wp-security-user-login-menu.php:212
msgid "Max Login Attempts"
msgstr ""
#: admin/wp-security-user-login-menu.php:214
msgid ""
"Set the value for the maximum login retries before IP address is locked out"
msgstr ""
#: admin/wp-security-user-login-menu.php:218
msgid "Login Retry Time Period (min)"
msgstr ""
#: admin/wp-security-user-login-menu.php:220
msgid ""
"If the maximum number of failed login attempts for a particular IP address "
"occur within this time period the plugin will lock out that address"
msgstr ""
#: admin/wp-security-user-login-menu.php:224
msgid "Time Length of Lockout (min)"
msgstr ""
#: admin/wp-security-user-login-menu.php:226
msgid ""
"Set the length of time for which a particular IP address will be prevented "
"from logging in"
msgstr ""
#: admin/wp-security-user-login-menu.php:230
msgid "Display Generic Error Message"
msgstr ""
#: admin/wp-security-user-login-menu.php:233
msgid ""
"Check this if you want to show a generic error message when a login attempt "
"fails"
msgstr ""
#: admin/wp-security-user-login-menu.php:237
msgid "Instantly Lockout Invalid Usernames"
msgstr ""
#: admin/wp-security-user-login-menu.php:240
msgid ""
"Check this if you want to instantly lockout login attempts with usernames "
"which do not exist on your system"
msgstr ""
#: admin/wp-security-user-login-menu.php:244
msgid "Instantly Lockout Specific Usernames"
msgstr ""
#: admin/wp-security-user-login-menu.php:253
msgid ""
"Insert one username per line. Existing usernames are not blocked even if "
"present in the list."
msgstr ""
#: admin/wp-security-user-login-menu.php:257
msgid "Notify By Email"
msgstr ""
#: admin/wp-security-user-login-menu.php:260
msgid ""
"Check this if you want to receive an email when someone has been locked out "
"due to maximum failed login attempts"
msgstr ""
#: admin/wp-security-user-login-menu.php:270
msgid "Currently Locked Out IP Address Ranges"
msgstr ""
#: admin/wp-security-user-login-menu.php:275
#, php-format
msgid ""
"To see a list of all locked IP addresses and ranges go to the %s tab in the "
"dashboard menu."
msgstr ""
#: admin/wp-security-user-login-menu.php:291
msgid "Nonce check failed for delete all failed login records operation!"
msgstr ""
#: admin/wp-security-user-login-menu.php:300
msgid "User Login Feature - Delete all failed login records operation failed!"
msgstr ""
#: admin/wp-security-user-login-menu.php:304
msgid "All records from the Failed Logins table were deleted successfully!"
msgstr ""
#: admin/wp-security-user-login-menu.php:319
msgid "This tab displays the failed login attempts for your site."
msgstr ""
#: admin/wp-security-user-login-menu.php:320
msgid ""
"The information below can be handy if you need to do security investigations "
"because it will show you the IP range, username and ID (if applicable) and "
"the time/date of the failed login attempt."
msgstr ""
#: admin/wp-security-user-login-menu.php:341
#: admin/wp-security-user-login-menu.php:350
msgid "Delete All Failed Login Records"
msgstr ""
#: admin/wp-security-user-login-menu.php:347
msgid ""
"Click this button if you wish to delete all failed login records in one go."
msgstr ""
#: admin/wp-security-user-login-menu.php:375
msgid ""
"You entered a non numeric value for the logout time period field. It has "
"been set to the default value."
msgstr ""
#: admin/wp-security-user-login-menu.php:403
msgid ""
"Setting an expiry period for your WP administration session is a simple way "
"to protect against unauthorized access to your site from your computer."
msgstr ""
#: admin/wp-security-user-login-menu.php:404
msgid ""
"This feature allows you to specify a time period in minutes after which the "
"admin session will expire and the user will be forced to log back in."
msgstr ""
#: admin/wp-security-user-login-menu.php:409
msgid "Force User Logout Options"
msgstr ""
#: admin/wp-security-user-login-menu.php:421
msgid "Enable Force WP User Logout"
msgstr ""
#: admin/wp-security-user-login-menu.php:424
msgid ""
"Check this if you want to force a wp user to be logged out after a "
"configured amount of time"
msgstr ""
#: admin/wp-security-user-login-menu.php:428
msgid "Logout the WP User After XX Minutes"
msgstr ""
#: admin/wp-security-user-login-menu.php:430
msgid ""
"(Minutes) The user will be forced to log back in after this time period has "
"elapased."
msgstr ""
#: admin/wp-security-user-login-menu.php:453
msgid ""
"This tab displays the login activity for WordPress admin accounts registered "
"with your site."
msgstr ""
#: admin/wp-security-user-login-menu.php:454
msgid ""
"The information below can be handy if you need to do security investigations "
"because it will show you the last 50 recent login events by username, IP "
"address and time/date."
msgstr ""
#: admin/wp-security-user-login-menu.php:497
msgid "Nonce check failed for users logged in list!"
msgstr ""
#: admin/wp-security-user-login-menu.php:505
msgid "Refresh Logged In User Data"
msgstr ""
#: admin/wp-security-user-login-menu.php:509
msgid "Refresh Data"
msgstr ""
#: admin/wp-security-user-login-menu.php:515
msgid "This tab displays all users who are currently logged into your site."
msgstr ""
#: admin/wp-security-user-login-menu.php:516
msgid ""
"If you suspect there is a user or users who are logged in which should not "
"be, you can block them by inspecting the IP addresses from the data below "
"and adding them to your blacklist."
msgstr ""
#: admin/wp-security-user-login-menu.php:517
msgid ""
"You can also instantly log them out by clicking on the \"Force Logout\" link "
"when you hover over the row in the User Id column."
msgstr ""
#: admin/wp-security-user-login-menu.php:522
msgid "Currently Logged In Users"
msgstr ""
#: admin/wp-security-user-registration-menu.php:23
msgid "Manual Approval"
msgstr ""
#: admin/wp-security-user-registration-menu.php:24
#: classes/grade-system/wp-security-feature-item-manager.php:57
msgid "Registration Captcha"
msgstr ""
#: admin/wp-security-user-registration-menu.php:117
msgid "User Registration Settings"
msgstr ""
#: admin/wp-security-user-registration-menu.php:121
msgid "Manually Approve New Registrations"
msgstr ""
#: admin/wp-security-user-registration-menu.php:125
msgid ""
"If your site allows people to create their own accounts via the WordPress "
"registration form, then you can minimize SPAM or bogus registrations by "
"manually approving each registration."
msgstr ""
#: admin/wp-security-user-registration-menu.php:126
msgid ""
"This feature will automatically set a newly registered account to \"pending"
"\" until the administrator activates it. Therefore undesirable registrants "
"will be unable to log in without your express approval."
msgstr ""
#: admin/wp-security-user-registration-menu.php:127
msgid ""
"You can view all accounts which have been newly registered via the handy "
"table below and you can also perform bulk activation/deactivation/deletion "
"tasks on each account."
msgstr ""
#: admin/wp-security-user-registration-menu.php:143
msgid "Enable manual approval of new registrations"
msgstr ""
#: admin/wp-security-user-registration-menu.php:146
msgid ""
"Check this if you want to automatically disable all newly registered "
"accounts so that you can approve them manually."
msgstr ""
#: admin/wp-security-user-registration-menu.php:155
msgid "Approve Registered Users"
msgstr ""
#: admin/wp-security-user-registration-menu.php:200
msgid ""
"This feature allows you to add a captcha form on the WordPress registration "
"page."
msgstr ""
#: admin/wp-security-user-registration-menu.php:201
msgid ""
"Users who attempt to register will also need to enter the answer to a simple "
"mathematical question - if they enter the wrong answer, the plugin will not "
"allow them to register."
msgstr ""
#: admin/wp-security-user-registration-menu.php:202
msgid ""
"Therefore, adding a captcha form on the registration page is another "
"effective yet simple SPAM registration prevention technique."
msgstr ""
#: admin/wp-security-user-registration-menu.php:207
msgid "Registration Page Captcha Settings"
msgstr ""
#: admin/wp-security-user-registration-menu.php:214
msgid ""
"The core default behaviour for WordPress Multi Site regarding user "
"registration is that all users are registered via the main site."
msgstr ""
#: admin/wp-security-user-registration-menu.php:215
msgid ""
"Therefore, if you would like to add a captcha form to the registration page "
"for a Multi Site, please go to \"Registration Captcha\" settings on the main "
"site."
msgstr ""
#: admin/wp-security-user-registration-menu.php:230
msgid "Enable Captcha On Registration Page"
msgstr ""
#: admin/wp-security-user-registration-menu.php:233
msgid ""
"Check this if you want to insert a captcha form on the WordPress user "
"registration page (if you allow user registration)."
msgstr ""
#: admin/wp-security-whois-menu.php:22
msgid "WhoIS Lookup"
msgstr ""
#: admin/wp-security-whois-menu.php:75
msgid "WHOIS Lookup Information"
msgstr ""
#: admin/wp-security-whois-menu.php:78
msgid ""
"This feature allows you to look up more detailed information about an IP "
"address or domain name by querying the WHOIS API."
msgstr ""
#: admin/wp-security-whois-menu.php:84
msgid "Perform a WHOIS Lookup for an IP or Domain Name"
msgstr ""
#: admin/wp-security-whois-menu.php:90
msgid "Enter IP Address or Domain Name"
msgstr ""
#: admin/wp-security-whois-menu.php:92
msgid ""
"Enter an IP address or domain name. Example: 111.11.12.13 OR some-domain-"
"name.com"
msgstr ""
#: admin/wp-security-whois-menu.php:96
msgid "Perform IP or Domain Lookup"
msgstr ""
#: admin/wp-security-whois-menu.php:117
msgid "WHOIS lookup successfully completed. Please see the results below:"
msgstr ""
#: admin/wp-security-whois-menu.php:129
msgid ""
"You have entered an incorrectly formatted IP address or domain name. Please "
"try again."
msgstr ""
#: admin/general/wp-security-list-table.php:178
msgid "No items found."
msgstr ""
#: admin/general/wp-security-list-table.php:281
msgid "Bulk Actions"
msgstr ""
#: admin/general/wp-security-list-table.php:291
msgid "Apply"
msgstr ""
#: admin/general/wp-security-list-table.php:365
msgid "Show all dates"
msgstr ""
#: admin/general/wp-security-list-table.php:378
#, php-format
msgid "%1$s %2$d"
msgstr ""
#: admin/general/wp-security-list-table.php:394
msgid "List View"
msgstr ""
#: admin/general/wp-security-list-table.php:395
msgid "Excerpt View"
msgstr ""
#: admin/general/wp-security-list-table.php:421
#, php-format
msgid "%s pending"
msgstr ""
#: admin/general/wp-security-list-table.php:653
msgid "Select All"
msgstr ""
#: classes/wp-security-backup.php:235
msgid "All In One WP Security - Site Database Backup"
msgstr ""
#: classes/wp-security-backup.php:237
msgid "Attached is your latest DB backup file for site URL"
msgstr ""
#: classes/wp-security-backup.php:237
msgid " generated on"
msgstr ""
#: classes/wp-security-captcha.php:17
#: classes/wp-security-general-init-tasks.php:366
msgid "Please enter an answer in digits:"
msgstr ""
#: classes/wp-security-captcha.php:98
msgid "one"
msgstr ""
#: classes/wp-security-captcha.php:99
msgid "two"
msgstr ""
#: classes/wp-security-captcha.php:100
msgid "three"
msgstr ""
#: classes/wp-security-captcha.php:101
msgid "four"
msgstr ""
#: classes/wp-security-captcha.php:102
msgid "five"
msgstr ""
#: classes/wp-security-captcha.php:103
msgid "six"
msgstr ""
#: classes/wp-security-captcha.php:104
msgid "seven"
msgstr ""
#: classes/wp-security-captcha.php:105
msgid "eight"
msgstr ""
#: classes/wp-security-captcha.php:106
msgid "nine"
msgstr ""
#: classes/wp-security-captcha.php:107
msgid "ten"
msgstr ""
#: classes/wp-security-captcha.php:108
msgid "eleven"
msgstr ""
#: classes/wp-security-captcha.php:109
msgid "twelve"
msgstr ""
#: classes/wp-security-captcha.php:110
msgid "thirteen"
msgstr ""
#: classes/wp-security-captcha.php:111
msgid "fourteen"
msgstr ""
#: classes/wp-security-captcha.php:112
msgid "fifteen"
msgstr ""
#: classes/wp-security-captcha.php:113
msgid "sixteen"
msgstr ""
#: classes/wp-security-captcha.php:114
msgid "seventeen"
msgstr ""
#: classes/wp-security-captcha.php:115
msgid "eighteen"
msgstr ""
#: classes/wp-security-captcha.php:116
msgid "nineteen"
msgstr ""
#: classes/wp-security-captcha.php:117
msgid "twenty"
msgstr ""
#: classes/wp-security-file-scan.php:60
msgid "All In One WP Security - File change detected!"
msgstr ""
#: classes/wp-security-file-scan.php:62
msgid "A file change was detected on your system for site URL"
msgstr ""
#: classes/wp-security-file-scan.php:62
msgid ". Scan was generated on"
msgstr ""
#: classes/wp-security-file-scan.php:63
msgid "A summary of the scan results is shown below:"
msgstr ""
#: classes/wp-security-file-scan.php:66
msgid "Login to your site to view the scan details."
msgstr ""
#: classes/wp-security-file-scan.php:295
msgid ""
"Starting DB scan.....please wait while the plugin scans your database......."
msgstr ""
#: classes/wp-security-file-scan.php:299
msgid "Scanning options table........."
msgstr ""
#: classes/wp-security-file-scan.php:368
#, php-format
msgid "%s and option_id: %s"
msgstr ""
#: classes/wp-security-file-scan.php:371
#, php-format
msgid ""
"Deletion of known pharma hack entry for option_name %s failed. Please delete "
"this entry manually!"
msgstr ""
#: classes/wp-security-file-scan.php:373
#, php-format
msgid ""
"The options table entry with known pharma hack for option_id %s with "
"option_name %s was successfully deleted"
msgstr ""
#: classes/wp-security-file-scan.php:387
#, php-format
msgid "Possible suspicious entry found (for option_id: %s) - %s "
msgstr ""
#: classes/wp-security-file-scan.php:396
msgid "No suspicious entries found in options table"
msgstr ""
#: classes/wp-security-file-scan.php:400
msgid "Scanning posts table........."
msgstr ""
#: classes/wp-security-file-scan.php:440
#, php-format
msgid ""
"Possible suspicious entry found (for Post ID: %s) in the following column - "
"%s "
msgstr ""
#: classes/wp-security-file-scan.php:449
msgid "No suspicious entries found in posts table"
msgstr ""
#: classes/wp-security-file-scan.php:453
msgid "Scanning links table........."
msgstr ""
#: classes/wp-security-file-scan.php:492 classes/wp-security-file-scan.php:543
#: classes/wp-security-file-scan.php:571 classes/wp-security-file-scan.php:599
#: classes/wp-security-file-scan.php:648
#, php-format
msgid "Possible suspicious entry - %s "
msgstr ""
#: classes/wp-security-file-scan.php:501
msgid "No suspicious entries found in links table"
msgstr ""
#: classes/wp-security-file-scan.php:505
msgid "Scanning comments table........."
msgstr ""
#: classes/wp-security-file-scan.php:552
msgid "No suspicious entries found in comments table"
msgstr ""
#: classes/wp-security-file-scan.php:556
msgid "Scanning postmeta table........."
msgstr ""
#: classes/wp-security-file-scan.php:580
msgid "No suspicious entries found in postmeta table"
msgstr ""
#: classes/wp-security-file-scan.php:584
msgid "Scanning usermeta table........."
msgstr ""
#: classes/wp-security-file-scan.php:608
msgid "No suspicious entries found in usermeta table"
msgstr ""
#: classes/wp-security-file-scan.php:612
msgid "Scanning users table........."
msgstr ""
#: classes/wp-security-file-scan.php:657
msgid "No suspicious entries found in users table"
msgstr ""
#: classes/wp-security-file-scan.php:664
msgid ""
"The plugin has detected that there are some potentially suspicious entries "
"in your database."
msgstr ""
#: classes/wp-security-file-scan.php:665
msgid ""
"Please verify the results listed below to confirm whether the entries "
"detected are genuinely suspicious or if they are false positives."
msgstr ""
#: classes/wp-security-file-scan.php:670 classes/wp-security-file-scan.php:685
msgid "Disclaimer:"
msgstr ""
#: classes/wp-security-file-scan.php:671
msgid ""
"Even though this database scan has revealed some suspicious entries, this "
"does not necessarily mean that other parts of your DB or site are also not "
"compromised."
msgstr ""
#: classes/wp-security-file-scan.php:672 classes/wp-security-file-scan.php:687
msgid ""
"Please note that database scan performed by this feature is basic and looks "
"for common malicious entries. Since hackers are continually evolving their "
"methods this scan is not meant to be a guaranteed catch-all for malware."
msgstr ""
#: classes/wp-security-file-scan.php:673 classes/wp-security-file-scan.php:688
#, php-format
msgid ""
"It is your responsibility to do the due diligence and perform a robust %s on "
"your site if you wish to be more certain that your site is clean."
msgstr ""
#: classes/wp-security-file-scan.php:680
msgid "DB Scan was completed successfully. No suspicious entries found."
msgstr ""
#: classes/wp-security-file-scan.php:686
msgid ""
"Even though the database scan has not revealed any suspicious entries, this "
"does not necessarily mean that your site is actually completely clean or not "
"compromised."
msgstr ""
#: classes/wp-security-file-scan.php:725
msgid "The following files were added to your host"
msgstr ""
#: classes/wp-security-file-scan.php:727 classes/wp-security-file-scan.php:736
#: classes/wp-security-file-scan.php:746
msgid "modified on: "
msgstr ""
#: classes/wp-security-file-scan.php:734
msgid "The following files were removed from your host"
msgstr ""
#: classes/wp-security-file-scan.php:744
msgid "The following files were changed on your host"
msgstr ""
#: classes/wp-security-general-init-tasks.php:395
#: classes/wp-security-general-init-tasks.php:478
#: classes/wp-security-user-login.php:75
#: classes/wp-security-user-registration.php:78
#: classes/wp-security-user-registration.php:108
msgid "<strong>ERROR</strong>: Your answer was incorrect - please try again."
msgstr ""
#: classes/wp-security-general-init-tasks.php:407
msgid "Enter something special:"
msgstr ""
#: classes/wp-security-general-init-tasks.php:434
msgid "Please enter an answer in the CAPTCHA field."
msgstr ""
#: classes/wp-security-general-init-tasks.php:447
msgid ""
"Error: You entered an incorrect CAPTCHA answer. Please go back and try again."
msgstr ""
#: classes/wp-security-general-init-tasks.php:505
msgid "Your CAPTCHA answer was incorrect - please try again."
msgstr ""
#: classes/wp-security-general-init-tasks.php:534
msgid "Your registration is pending approval."
msgstr ""
#: classes/wp-security-process-renamed-login-page.php:106
msgid "Not available."
msgstr ""
#: classes/wp-security-user-login.php:39
msgid ""
"<strong>ERROR</strong>: Access from your IP address has been blocked for "
"security reasons. Please contact the administrator."
msgstr ""
#: classes/wp-security-user-login.php:45
msgid "Service Temporarily Unavailable"
msgstr ""
#: classes/wp-security-user-login.php:118
msgid ""
"<strong>ACCOUNT PENDING</strong>: Your account is currently not active. An "
"administrator needs to activate your account before you can login."
msgstr ""
#: classes/wp-security-user-login.php:175
msgid "<strong>ERROR</strong>: Invalid login credentials."
msgstr ""
#: classes/wp-security-user-login.php:300
msgid "Site Lockout Notification"
msgstr ""
#: classes/wp-security-user-login.php:301
msgid ""
"A lockdown event has occurred due to too many failed login attempts or "
"invalid username:"
msgstr ""
#: classes/wp-security-user-login.php:302
msgid "Username:"
msgstr ""
#: classes/wp-security-user-login.php:303
msgid "IP Address:"
msgstr ""
#: classes/wp-security-user-login.php:304
msgid "IP Range:"
msgstr ""
#: classes/wp-security-user-login.php:305
msgid ""
"Log into your site's WordPress administration panel to see the duration of "
"the lockout or to unlock the user."
msgstr ""
#: classes/wp-security-user-login.php:377
msgid "Unlock Request Notification"
msgstr ""
#: classes/wp-security-user-login.php:379
#, php-format
msgid ""
"You have requested for the account with email address %s to be unlocked. "
"Please click the link below to unlock your account:"
msgstr ""
#: classes/wp-security-user-login.php:380
#, php-format
msgid "Unlock link: %s"
msgstr ""
#: classes/wp-security-user-login.php:381
msgid ""
"After clicking the above link you will be able to login to the WordPress "
"administration panel."
msgstr ""
#: classes/wp-security-user-login.php:538
#, php-format
msgid ""
"Your session has expired because it has been over %d minutes since your last "
"login."
msgstr ""
#: classes/wp-security-user-login.php:539
#: classes/wp-security-user-login.php:543
msgid "Please log back in to continue."
msgstr ""
#: classes/wp-security-user-login.php:542
msgid "You were logged out because you just changed the \"admin\" username."
msgstr ""
#: classes/wp-security-user-login.php:571
msgid "Request Unlock"
msgstr ""
#: classes/wp-security-user-registration.php:62
#: classes/wp-security-user-registration.php:93
msgid ""
"<strong>ERROR</strong>: You are not allowed to register because your IP "
"address is currently locked!"
msgstr ""
#: classes/wp-security-utility-ip-address.php:74
#: classes/wp-security-utility-ip-address.php:89
#: classes/wp-security-utility-ip-address.php:108
#: classes/wp-security-utility-ip-address.php:123
#: classes/wp-security-utility-ip-address.php:138
msgid " is not a valid ip address format."
msgstr ""
#: classes/wp-security-utility-ip-address.php:146
msgid "You cannot ban your own IP address: "
msgstr ""
#: classes/wp-security-utility.php:226
msgid ""
"This feature can only be configured by the \"superadmin\" on the main site."
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:29
msgid "Remove WP Generator Meta Tag"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:38
msgid "Change Display Name"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:45
msgid "Custom Login Captcha"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:47
msgid "Lost Password Captcha"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:49
msgid "Login IP Whitelisting"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:55
msgid "Registration Approval"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:71
msgid "WordPress Files Access"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:75
msgid "IP and User Agent Blacklisting"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:79
msgid "Enable Basic Firewall"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:80
msgid "Enable Pingback Vulnerability Protection"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:82
msgid "Enable IP blocking for 404 detection"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:86
msgid "Enable Rename Login Page"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:88
msgid "Enable Login Honeypot"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:94
msgid "Forbid Proxy Comments"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:95
msgid "Deny Bad Queries"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:97
msgid "5G/6G Blacklist"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:100
msgid "Block Spambots"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:102
msgid "Comment Captcha"
msgstr ""
#: classes/grade-system/wp-security-feature-item-manager.php:104
msgid "BuddyPress Registration Captcha"
msgstr ""
#: classes/grade-system/wp-security-feature-item.php:28
msgid "Basic"
msgstr ""
#: classes/grade-system/wp-security-feature-item.php:31
msgid "Intermediate"
msgstr ""
#: classes/grade-system/wp-security-feature-item.php:34
msgid "Advanced"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:99
msgid "https://wordpress.org/"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:100
#: other-includes/wp-security-unlock-request.php:14
msgid "Powered by WordPress"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:217
#, php-format
msgid "&larr; Back to %s"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:282
msgid "<strong>ERROR</strong>: Enter a username or e-mail address."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:286
msgid ""
"<strong>ERROR</strong>: There is no user registered with that email address."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:303
msgid "<strong>ERROR</strong>: Invalid username or e-mail."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:341
msgid "Password reset is not allowed for this user"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:367
msgid "Someone requested that the password be reset for the following account:"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:369
#, php-format
msgid "Username: %s"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:370
msgid "If this was a mistake, just ignore this email and nothing will happen."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:371
msgid "To reset your password, visit the following address:"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:383
#, php-format
msgid "[%s] Password Reset"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:408
msgid "The e-mail could not be sent."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:408
msgid "Possible reason: your host may have disabled the mail() function."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:530
msgid ""
"Your password reset link appears to be invalid. Please request a new link "
"below."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:532
msgid "Your password reset link has expired. Please request a new link below."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:553
msgid "Lost Password"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:553
msgid ""
"Please enter your username or email address. You will receive a link to "
"create a new password via email."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:561
msgid "Username or E-mail:"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:576
#: other-includes/wp-security-rename-login-feature.php:639
#: other-includes/wp-security-rename-login-feature.php:685
#: other-includes/wp-security-rename-login-feature.php:767
msgid "Log in"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:579
#: other-includes/wp-security-rename-login-feature.php:688
#: other-includes/wp-security-rename-login-feature.php:945
msgid "Register"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:624
msgid "The passwords do not match."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:639
msgid "Password Reset"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:639
msgid "Your password has been reset."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:647
msgid "Reset Password"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:647
msgid "Enter your new password below."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:654
msgid "New password"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:659
msgid "Strength indicator"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:663
msgid "Confirm new password"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:740
msgid "Registration Form"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:740
msgid "Register For This Site"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:745
msgid "Username"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:749
msgid "E-mail"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:760
msgid "Registration confirmation will be e-mailed to you."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:768
#: other-includes/wp-security-rename-login-feature.php:951
msgid "Lost your password?"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:808
#, php-format
msgid ""
"<strong>ERROR</strong>: Cookies are blocked due to unexpected output. For "
"help, please see <a href=\"%1$s\">this documentation</a> or try the <a href="
"\"%2$s\">support forums</a>."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:809
#: other-includes/wp-security-rename-login-feature.php:813
msgid "https://codex.wordpress.org/Cookies"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:809
msgid "https://wordpress.org/support/"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:812
#, php-format
msgid ""
"<strong>ERROR</strong>: Cookies are blocked or not supported by your "
"browser. You must <a href=\"%s\">enable cookies</a> to use WordPress."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:831
msgid "You have logged in successfully."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:865
msgid ""
"Session expired. Please log in again. You will not move away from this page."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:869
msgid "You are now logged out."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:871
msgid "User registration is currently not allowed."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:873
msgid "Check your e-mail for the confirmation link."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:875
msgid "Check your e-mail for your new password."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:877
msgid "Registration complete. Please check your e-mail."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:879
msgid ""
"<strong>You have successfully updated WordPress!</strong> Please log back in "
"to see what&#8217;s new."
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:896
msgid "Log In"
msgstr ""
#: other-includes/wp-security-rename-login-feature.php:911
msgid "Username or Email"
msgstr ""
#: other-includes/wp-security-unlock-request.php:13
msgid "http://wordpress.org/"
msgstr ""
#: other-includes/wp-security-unlock-request.php:33
msgid "ERROR: Unable to process your request!"
msgstr ""
#: other-includes/wp-security-unlock-request.php:50
msgid "Please enter a valid email address"
msgstr ""
#: other-includes/wp-security-unlock-request.php:62
msgid "User account not found!"
msgstr ""
#: other-includes/wp-security-unlock-request.php:77
msgid "Error: No locked entry was found in the DB with your IP address range!"
msgstr ""
#: other-includes/wp-security-unlock-request.php:82
msgid "An email has been sent to you with the unlock instructions."
msgstr ""
#: other-includes/wp-security-unlock-request.php:100
msgid ""
"You are here because you have been locked out due to too many incorrect "
"login attempts."
msgstr ""
#: other-includes/wp-security-unlock-request.php:101
msgid ""
"Please enter your email address and you will receive an email with "
"instructions on how to unlock yourself."
msgstr ""
#: other-includes/wp-security-unlock-request.php:107
msgid "Email Address"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink