# Translation of Plugins - Acunetix Secure WordPress - Development (trunk) in Aragonese
# This file is distributed under the same license as the Plugins - Acunetix Secure WordPress - Development (trunk) package.
msgid ""
msgstr ""
"PO-Revision-Date: +0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: GlotPress/4.0.3\n"
"Language: an_ES\n"
"Project-Id-Version: Plugins - Acunetix Secure WordPress - Development (trunk)\n"

#. Author URI of the plugin/theme
msgid "http://www.acunetix.com/"
msgstr ""

#. Author of the plugin/theme
msgid "Acunetix"
msgstr ""

#. Description of the plugin/theme
msgid "The Acunetix Secure WordPress plugin is the ultimate must-have tool when it comes to WordPress security. The plugin is free and monitors your website for security weaknesses that hackers might exploit and tells you how to easily fix them."
msgstr ""

#. Plugin URI of the plugin/theme
msgid "http://www.acunetix.com/websitesecurity/wordpress-security-plugin/"
msgstr ""

#. Plugin Name of the plugin/theme
msgid "Acunetix Secure WordPress"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:103
msgid ""
"Our suggested permissions are still secure but more permissive in order not to break some servers' setups.\n"
"            If your existent file permissions are more restrictive, ex: 0750 instead of the suggested 0755 then you have no reason to\n"
"            change it to the suggested 0755 permissions."
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:70
msgid "Not Found"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:50
msgid "Suggested permissions"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:49
msgid "Current permissions"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:48
msgid "Path"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:47
msgid "Name"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:37
msgid "There are currently no files set for scanning!"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:30
msgid "Failed"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:30
msgid "Successful changes"
msgstr ""

#: res/pages/tpl/box-scan-results-file.php:28
msgid "No changes applied. You are running PHP on a Windows server thus chmod cannot be used"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:230
msgid "Start Renaming"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:229
msgid "Allowed characters: all latin alphanumeric as well as the <strong>_</strong> (underscore)."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:228
msgid "Change the current: <input type=\"text\" name=\"newPrefixInput\" value=\"%s\" size=\"20\" maxlength=\"15\"/> table prefix to something different."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:206
msgid "An error has occurred and the tables could not be updated!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:203
msgid "The <strong>wp-config</strong> file could not be updated! You have to manually update the <strong>$table_prefix</strong> variable to the one you have specified"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:200
msgid "The <strong>wp-config</strong> file has been successfully updated!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:193
msgid "All tables have been successfully updated!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:183
msgid "Internal Error: We couldn't retrieve the list of tables from the database! Please inform the plug-in author about this error! Thank you!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:174
msgid "No change! Please select a different table prefix value."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:170
msgid "You used some characters disallowed in Table names. The sanitized prefix will be used instead"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:164
msgid ""
"The User which is used to access your Wordpress Database, hasn't enough rights (is missing the <code>ALTER</code> right) to alter the Table structure.\n"
"                            Please visit the <a href=\"http://www.websitedefender.com/category/faq/\" target=_blank\">WebsiteDefender WP Security Scan WordPress plugin documentation</a> website for more information.\n"
"                            If the user <code>has ALTER</code> rights and the tool is still not working, please <a href=\"http://www.websitedefender.com/support/\" target=\"_blank\">contact us</a> for assistance!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:150
msgid "An internal error has occurred (empty $wpdb). Please inform the plug-in author about this error. Thank you!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:140
msgid "Please correct the following errors"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:116
msgid "Your currently used User to access the Wordpress Database <code>holds too many rights</code>. We suggest that you limit his rights or to use another User with more limited rights instead, to increase your website's Security."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:108
msgid ""
"It is a security risk to have your files <strong>writable</strong>!\n"
"                    Please make sure that <strong>after</strong> running this script, the <code>wp-config.php</code> file's permissions are set to 0644 or to a more restrictive one. See: <a href=\"http://codex.wordpress.org/Changing_File_Permissions\" target=\"_blank\">http://codex.wordpress.org/Changing_File_Permissions</a> for more information."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:88
#: res/pages/tpl/box-database-change-prefix.php:142
msgid "The <strong>wp-config</strong> file <strong>MUST</strong> be writable!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:83
#: res/pages/tpl/box-database-change-prefix.php:141
msgid "The User used to access the database must have <strong>ALTER</strong> rights in order to perform this action!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:70
msgid "In order to alter the <code>wp-config.php</code> file we need the <strong>file</strong> function which seems to be blacklisted by your server administrator!"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:56
msgid "The database user you're using to connect to database must have <strong>ALTER</strong> rights."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:55
msgid "The <code>wp-config.php</code> file must be <strong>writable</strong>."
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:53
msgid "Before running this script"
msgstr ""

#: res/pages/tpl/box-database-change-prefix.php:52
msgid "Change your database table prefix to avoid zero-day SQL Injection attacks."
msgstr ""

#: res/pages/tpl/box-database-backup.php:57
msgid "<strong>Important</strong>: The <code title=\"%s\">backups</code> directory <strong>MUST</strong> be writable in order to use this feature!"
msgstr ""

#: res/pages/tpl/box-database-backup.php:50
msgid "Backup now!"
msgstr ""

#: res/pages/tpl/box-database-backup.php:40
msgid "A possible error might be that you didn't set up writing permissions for the backups directory!"
msgstr ""

#: res/pages/tpl/box-database-backup.php:39
msgid "The database could not be backed up!"
msgstr ""

#: res/pages/tpl/box-database-backup.php:33
msgid "Download backup file"
msgstr ""

#: res/pages/tpl/box-database-backup.php:32
msgid "Database successfully backed up!"
msgstr ""

#: res/pages/tpl/box-database-backup.php:7
msgid "<strong>Please backup your database before using this tool!</strong>"
msgstr ""

#: res/pages/tpl/box-database-backup.php:6
msgid "Your WordPress database contains every post, every comment and every link you have on your blog. If your database gets erased or corrupted, you stand to lose everything you have written. There are many reasons why this could happen and not all are things you can control. But what you can do is <strong>back up your data</strong>."
msgstr ""

#: res/pages/tpl/box-available-backups.php:20
msgid "Click to download"
msgstr ""

#: res/pages/tpl/box-available-backups.php:13
msgid "You don't have any backup files yet!"
msgstr ""

#: res/pages/settings.php:97
msgid "Show the RSS widget in the dashboard"
msgstr ""

#: res/pages/settings.php:19 res/pages/settings.php:22
#: res/pages/tpl/box-scan-results-file.php:18
#: res/pages/tpl/box-scan-results-file.php:21
msgid "Invalid request."
msgstr ""

#: res/pages/scanner.php:31
msgid "File Scan Report"
msgstr ""

#: res/pages/scanner.php:22
msgid "WordPress Scan Report"
msgstr ""

#: res/pages/scanner.php:14
msgid "Server Report"
msgstr ""

#: res/pages/scanner.php:8
msgid "This page displays various information after scanning your WordPress website"
msgstr ""

#: res/pages/scanner.php:4
msgid "WordPress Scanner"
msgstr ""

#: res/pages/live_traffic.php:215
msgid "Loading data..."
msgstr ""

#: res/pages/live_traffic.php:156
msgid "Live Traffic"
msgstr ""

#: res/pages/database.php:51
msgid "Change Database Prefix"
msgstr ""

#: res/pages/database.php:33
msgid "Database Backup Files"
msgstr ""

#: res/pages/database.php:18
msgid "Backup Database"
msgstr ""

#: res/pages/database.php:4
msgid "Database Tools"
msgstr ""

#: res/pages/dashboard.php:117
msgid "No alerts found."
msgstr ""

#: res/pages/dashboard.php:99 res/pages/dashboard.php:109
msgid "Solution"
msgstr ""

#: res/pages/dashboard.php:96 res/pages/dashboard.php:106
msgid "Description"
msgstr ""

#: res/pages/dashboard.php:83
msgid "Previous alerts"
msgstr ""

#: res/pages/dashboard.php:71
msgid "Click to expand/collapse"
msgstr ""

#: res/pages/dashboard.php:56
msgid "Title"
msgstr ""

#: res/pages/dashboard.php:54
msgid "Severity"
msgstr ""

#: res/pages/dashboard.php:48
msgid "Current Alerts"
msgstr ""

#: res/pages/dashboard.php:40
msgid "Informational"
msgstr ""

#: res/pages/dashboard.php:39
msgid "Low"
msgstr ""

#: res/pages/dashboard.php:38
msgid "Medium"
msgstr ""

#: res/pages/dashboard.php:37
msgid "Critical"
msgstr ""

#: res/pages/dashboard.php:36
msgid "All Severity Levels"
msgstr ""

#: res/pages/blog.php:41
msgid "Posted on "
msgstr ""

#: res/pages/blog.php:36
msgid "There are no entries for this feed!"
msgstr ""

#: res/pages/blog.php:12
msgid "Follow us on Facebook"
msgstr ""

#: res/pages/blog.php:11
msgid "Follow us on Twitter"
msgstr ""

#: res/pages/about.php:50
msgid "Support"
msgstr ""

#: res/pages/about.php:47
msgid "Acunetix on Facebook"
msgstr ""

#: res/pages/about.php:44
msgid "Acunetix on Twitter"
msgstr ""

#: res/pages/about.php:41
msgid "Acunetix blog"
msgstr ""

#: res/pages/about.php:37
msgid "Get involved"
msgstr ""

#: res/pages/about.php:30
msgid "Turns off PHP error reporting."
msgstr ""

#: res/pages/about.php:29
msgid "Turns off database error reporting (if enabled)."
msgstr ""

#: res/pages/about.php:28
msgid "Provides a tool to easily backup your WordPress database."
msgstr ""

#: res/pages/about.php:27
msgid "Provides a tool for changing the database prefix."
msgstr ""

#: res/pages/about.php:26
msgid "Provides a Live Traffic tool to monitor your website activity in real time."
msgstr ""

#: res/pages/about.php:25
msgid "Provides file permissions security checks."
msgstr ""

#: res/pages/about.php:24
msgid "Provides various information after scanning your WordPress blog."
msgstr ""

#: res/pages/about.php:23
msgid "Removes version on URLs from scripts and stylesheets."
msgstr ""

#: res/pages/about.php:22
msgid "Removes theme-update information for non-admins (only WP 2.8 and higher)."
msgstr ""

#: res/pages/about.php:21
msgid "Removes plugin-update information for non-admins."
msgstr ""

#: res/pages/about.php:20
msgid "Removes core update information for non-admins."
msgstr ""

#: res/pages/about.php:19
msgid "Removes Windows Live Writer meta tag."
msgstr ""

#: res/pages/about.php:18
msgid "Removes Really Simple Discovery meta tag."
msgstr ""

#: res/pages/about.php:17
msgid "Removes the wp-version from everyone but administrators."
msgstr ""

#: res/pages/about.php:16
msgid "Adds index.php to the wp-content, wp-content/plugins, wp-content/themes and wp-content/uploads directories to prevent directory listings."
msgstr ""

#: res/pages/about.php:15
msgid "Removes error-information on login-page."
msgstr ""

#: res/inc/swpa-functions.php:16
msgid "Every 8 hours"
msgstr ""

#: res/inc/SwpaWatch.php:62
msgid "<p>This alert is generated every time an administrator's password is updated.</p>"
msgstr ""

#: res/inc/SwpaWatch.php:61
msgid "Administrator (%s) password updated"
msgstr ""

#: res/inc/SwpaUtil.php:542 res/pages/blog.php:53
msgid "Follow us on RSS"
msgstr ""

#: res/inc/SwpaUtil.php:518
msgid "There are no entries for this rss feed!"
msgstr ""

#: res/inc/SwpaUtil.php:503 res/pages/blog.php:28
msgid "An error has occurred while trying to load the rss feed!"
msgstr ""

#: res/inc/SwpaUtil.php:395
msgid "Changing database prefix"
msgstr ""

#: res/inc/SwpaUtil.php:392
msgid "Changing values in table <strong>%susermeta</strong>: <span style=\"color:#ff0000;\">Failed</span>"
msgstr ""

#: res/inc/SwpaUtil.php:383
msgid "Changing value: %suser_roles in table <strong>%soptions</strong>: <span style=\"color:#ff0000;\">Failed</span>"
msgstr ""

#: res/inc/SwpaUtil.php:245
msgid "Could not retrieve the list of tables from the database!"
msgstr ""

#: res/inc/SwpaUtil.php:230
msgid "Error: Could not select the database!"
msgstr ""

#: res/inc/SwpaUtil.php:227
msgid "Error: Cannot connect to database!"
msgstr ""

#: res/inc/SwpaUtil.php:221
msgid "The %s directory <strong>MUST</strong> be writable for this feature to work!"
msgstr ""

#: res/inc/SwpaSecurity.php:702
msgid "The content of the readme.html file from the root directory has been deleted."
msgstr ""

#: res/inc/SwpaSecurity.php:697
msgid "<p>We have encountered an error while trying to delete the content of this file, thus you will have to manually delete it or make it inaccessible from your visitors by setting the file permissions to <strong>0440</strong> or lower.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:694
msgid "The content of the <strong>\"%s\"</strong> file from the <strong>\"%s\"</strong> directory could not be deleted."
msgstr ""

#: res/inc/SwpaSecurity.php:682
msgid ""
"<p>This plugin can automatically delete its content (assuming the file exists) if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.r\n"
"                    You can also delete this file manually by connecting to your website through an FTP connection.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:680 res/inc/SwpaSecurity.php:695
#: res/inc/SwpaSecurity.php:703
msgid ""
"<p>A default WordPress installation contains a readme.html file. This file is a simple html file that does not contain executable content that can be exploited by hackers or malicious users.r\n"
"                        Still, this file can provide hackers the version of your WordPress installation, therefore it is important to either delete this file or make it inaccessible for your visitors.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:679
msgid "Clearing the content of the <strong>\"%s\"</strong> file from the <strong>\"%s\"</strong> directory is disabled."
msgstr ""

#: res/inc/SwpaSecurity.php:655
msgid "WordPress version displayed in links only for administrator users."
msgstr ""

#: res/inc/SwpaSecurity.php:644
msgid "<p>This plugin can automatically hide the WordPress version from links if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:641 res/inc/SwpaSecurity.php:656
msgid ""
"<p>By default, WordPress will display the current version in links to javascript scripts or stylesheets.r\n"
"                    Therefore, if anyone has access to this information it might be a security risk because if a hacker knows which version of WordPress a website is running,r\n"
"                    it can make it easier for him to target a known WordPress security issue.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:640
msgid "WordPress version is displayed in links for all users"
msgstr ""

#: res/inc/SwpaSecurity.php:507 res/inc/SwpaSecurity.php:545
#: res/inc/SwpaSecurity.php:583 res/inc/SwpaSecurity.php:621
msgid ""
"<p>This plugin can automatically create an empty <strong>index.php</strong> file in the following directories: wp-content, wp-content/plugins, wp-content/themes and wp-content/uploads ifr\n"
"                            the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:503 res/inc/SwpaSecurity.php:521
#: res/inc/SwpaSecurity.php:533 res/inc/SwpaSecurity.php:541
#: res/inc/SwpaSecurity.php:559 res/inc/SwpaSecurity.php:571
#: res/inc/SwpaSecurity.php:579 res/inc/SwpaSecurity.php:597
#: res/inc/SwpaSecurity.php:609 res/inc/SwpaSecurity.php:617
msgid "<strong>\"%s\"</strong> directory is not secure from directory listing."
msgstr ""

#: res/inc/SwpaSecurity.php:496 res/inc/SwpaSecurity.php:504
#: res/inc/SwpaSecurity.php:522 res/inc/SwpaSecurity.php:534
#: res/inc/SwpaSecurity.php:542 res/inc/SwpaSecurity.php:560
#: res/inc/SwpaSecurity.php:572 res/inc/SwpaSecurity.php:580
#: res/inc/SwpaSecurity.php:598 res/inc/SwpaSecurity.php:610
#: res/inc/SwpaSecurity.php:618
msgid ""
"<p>A directory listing provides an attacker with the complete index of all the resources located inside of the directory.r\n"
"                            The specific risks and consequences vary depending on which files are listed and accessible.r\n"
"                            Therefore, it is important to protect your directories by having an empty index.php or index.htm file inside them.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:483 res/inc/SwpaSecurity.php:495
msgid "<strong>\"%s\"</strong> directory is secure from directory listing."
msgstr ""

#: res/inc/SwpaSecurity.php:464
msgid "Directory listing check is enabled."
msgstr ""

#: res/inc/SwpaSecurity.php:456
msgid ""
"<p>This plugin can automatically create an empty <strong>index.php</strong> file in the following directories: wp-content, wp-content/plugins, wp-content/themes and wp-content/uploads ifr\n"
"                    the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:453 res/inc/SwpaSecurity.php:465
#: res/inc/SwpaSecurity.php:484
msgid ""
"<p>A directory listing provides an attacker with the complete index of all the resources located inside of the directory.r\n"
"                    The specific risks and consequences vary depending on which files are listed and accessible.r\n"
"                    Therefore, it is important to protect your directories by having an empty index.php or index.htm file inside them.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:452
msgid "Directory listing check is disabled. This option should be enabled."
msgstr ""

#: res/inc/SwpaSecurity.php:436
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the blog administratorr\n"
"                       needs to be informed about an event that has occurred inside WordPress, it could be about an available update for ther\n"
"                       WordPress platform, a plugin or a theme that was updated or needs an update or to be configured, etc.</p>r\n"
"                <p>Currently, these notifications are displayed only to administrator users.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:435
msgid "WordPress admin notifications are only displayed to administrator users."
msgstr ""

#: res/inc/SwpaSecurity.php:420
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the blog administratorr\n"
"                       needs to be informed about an event that has occurred inside WordPress, it could be about an available update for ther\n"
"                       WordPress platform, a plugin or a theme that was updated or needs an update or to be configured, etc.</p>r\n"
"                    <p>These notifications should only be viewed by the website's administrators and not visible to any other users registered with that website.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:419
msgid "WordPress admin notifications are displayed to all users."
msgstr ""

#: res/inc/SwpaSecurity.php:405
msgid "<p>Currently, these errors are hidden to all users.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:404
msgid "WordPress login errors are not displayed."
msgstr ""

#: res/inc/SwpaSecurity.php:392
msgid ""
"<p>Every time a failed login is encountered, the WordPress platform generates an error message that is displayed to the user.r\n"
"                        This is a potential security risk because it let's the user know of his mistake (be it a wrong user name or password) thus making yourr\n"
"                        WordPress website more vulnerable to attacks.</p>r\n"
"                    <p>We strongly recommend you to hide these login error messages from all users to ensure a better security of your blog.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:391
msgid "WordPress login errors are displayed."
msgstr ""

#: res/inc/SwpaSecurity.php:376
msgid "Themes update notifications are only displayed to administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:358
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the blog administratorr\n"
"                        needs to be informed about an available update for a theme.</p>r\n"
"                    <p>These notifications should only be viewed by the website's administrators and not visible to any other users registered with that website.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:357
msgid "Themes update notifications are displayed to all users."
msgstr ""

#: res/inc/SwpaSecurity.php:343 res/inc/SwpaSecurity.php:377
msgid "<p>Currently, these notifications are only displayed to administrator users.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:342
msgid "Plugins update notifications are only displayed to administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:318
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the blog administratorr\n"
"                        needs to be informed about an available update for a plugin.</p>r\n"
"                    <p>These notifications should only be viewed by the website's administrators and not visible to any other users registered with that website.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:317
msgid "Plugins update notifications are displayed to all users"
msgstr ""

#: res/inc/SwpaSecurity.php:302
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the website was updated or needs an update.</p>r\n"
"                <p>Currently, these notifications are only displayed to administrator users.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:301
msgid "Core update notifications are only displayed to administrator users."
msgstr ""

#: res/inc/SwpaSecurity.php:283 res/inc/SwpaSecurity.php:321
#: res/inc/SwpaSecurity.php:361 res/inc/SwpaSecurity.php:396
#: res/inc/SwpaSecurity.php:424
msgid "<p>This plugin can automatically hide these notifications if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:281
msgid ""
"<p>These notifications are displayed at the top of the screen by the WordPress platform whenever the website was updated or needs an update.</p>r\n"
"                    <p>These notifications should only be viewed by the website's administrators and not visible to any other users registered with that website.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:280
msgid "Core update notifications are displayed to all users"
msgstr ""

#: res/inc/SwpaSecurity.php:258
msgid ""
"<p>By default, WordPress hides database errors, but there are times when a plugin might enable them thus it is very important to have this type of errors turned offr\n"
"                        so if there is an error during a connection to the database the user will not get access to the error message generated during that request.</p>r\n"
"                        <p>As regarding the PHP errors, with the <strong>display_error</strong> PHP configuration directive enabled, untrusted sources can see detailed web application environmentr\n"
"                        error messages which include sensitive information that can be used to craft further attacks.</p>r\n"
"                        <p>Attackers will do anything to collect information in order to design their attack in a more sophisticated way to eventually hack your website or web application, and causingr\n"
"                        errors to display is a common starting point. Website errors can always occur, but they should be suppressed from being displayed back to the public.</p>r\n"
"                        <p>Therefore we highly recommend you to have the <strong>\"%s\"</strong> option checked on the plugin's settings page to ensure PHP andr\n"
"                        database errors will be hidden from all users. For more information, please check the following <a href=\"%s\" target=\"%s\">article</a>.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:257
msgid "Error reporting, PHP and database, is enabled only for administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:242
msgid "<p>This plugin can do this automatically if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:233
msgid ""
"<p>By default, WordPress hides database errors, but there are times when a plugin might enable them thus it is very important to have this type of errors turned offr\n"
"                            so if there is an error during a connection to the database the user will not get access to the error message generated during that request.</p>r\n"
"                            <p>As regarding the PHP errors, with the <strong>display_error</strong> PHP configuration directive enabled, untrusted sources can see detailed web application environmentr\n"
"                            error messages which include sensitive information that can be used to craft further attacks.</p>r\n"
"                            <p>Attackers will do anything to collect information in order to design their attack in a more sophisticated way to eventually hack your website or web application, and causingr\n"
"                            errors to display is a common starting point. Website errors can always occur, but they should be suppressed from being displayed back to the public.</p>r\n"
"                            <p>Therefore we highly recommend you to have the <strong>\"%s\"</strong> option checked on the plugin's settings page to ensure PHP andr\n"
"                            database errors will be hidden from all users. For more information, please check the following <a href=\"%s\" target=\"%s\">article</a>.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:232
msgid "The check for PHP and database error reporting is disabled"
msgstr ""

#: res/inc/SwpaSecurity.php:214
msgid "WordPress Windows Live Writer tag is only displayed on frontend for administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:203
msgid "<p>This plugin can automatically hide the wlw meta tag if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:199 res/inc/SwpaSecurity.php:215
msgid ""
"<p>By default, WordPress creates the wlw meta tag to allow bloggers to publish their articles using the <strong>\"%s\"</strong> application.r\n"
"                        It is recommended to hide this meta tag from all visitors. If the option <strong>\"%s\"</strong> is checked on the plugin's settings page, this meta tagr\n"
"                        will still be available for administrator users to use the <strong>\"%s\"</strong> application to publish their blog posts.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:198
msgid "WordPress Windows Live Writer tag is displayed on frontend for all users"
msgstr ""

#: res/inc/SwpaSecurity.php:181
msgid "WordPress Really Simple Discovery tag is only displayed on frontend to administrator users."
msgstr ""

#: res/inc/SwpaSecurity.php:170
msgid "<p>This plugin can automatically hide the rsd meta tag if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:167 res/inc/SwpaSecurity.php:182
msgid ""
"<p>By default, WordPress creates the <strong>rsd meta tag</strong> to allow bloggers to consume services like Flickr using the <a href=\"%s\" target=\"%s\">XML-RPC</a> protocol.r\n"
"                            If you don't use such services it is recommended to hide this meta tag.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:166
msgid "WordPress Really Simple Discovery tag is displayed on frontend to all users"
msgstr ""

#: res/inc/SwpaSecurity.php:151
msgid ""
"<p>By default, WordPress creates a few meta tags, among which is the currently installed version, that give a hacker the knowledge about your WordPress installation.r\n"
"                At the moment, all WordPress's defaults meta tags are hidden for all users but administrators.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:150
msgid "WordPress meta tags are only displayed on frontend to administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:110
msgid "<p>This plugin can automatically hide your WordPress's default meta tags if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:109
msgid "<p>By default, WordPress creates a few meta tags, among which is the currently installed version, that give a hacker the knowledge about your WordPress installation. At the moment, these meta tags are available for anyone to see, which is a potentially security risk.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:108
msgid "WordPress meta tags are displayed on frontend to all users"
msgstr ""

#: res/inc/SwpaSecurity.php:47 res/inc/SwpaSecurity.php:91
msgid "WordPress version is only displayed to administrator users"
msgstr ""

#: res/inc/SwpaSecurity.php:29
msgid "<p>This plugin can automatically hide your WordPress version from frontend, backend and rss feeds if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:27 res/inc/SwpaSecurity.php:48
#: res/inc/SwpaSecurity.php:92
msgid ""
"<p>Displaying your WordPress version on frontend and in the backend's footer to all visitorsr\n"
"                        and users of your website is a security risk because if a hacker knows which version of WordPress a website is running, it can make it easier for him to target a known WordPress security issue.</p>"
msgstr ""

#: res/inc/SwpaSecurity.php:26
msgid "WordPress version is displayed for all users"
msgstr ""

#: res/inc/SwpaPlugin.php:20 res/pages/about.php:3 res/pages/about.php:8
msgid "About"
msgstr ""

#: res/inc/SwpaPlugin.php:19 res/pages/settings.php:65
#: res/pages/settings.php:71
msgid "Settings"
msgstr ""

#: res/inc/SwpaPlugin.php:18
msgid "Blog"
msgstr ""

#: res/inc/SwpaPlugin.php:17
msgid "Live traffic"
msgstr ""

#: res/inc/SwpaPlugin.php:16
msgid "Scanner"
msgstr ""

#: res/inc/SwpaPlugin.php:15
msgid "Database"
msgstr ""

#: res/inc/SwpaPlugin.php:14 res/pages/dashboard.php:24
msgid "Dashboard"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:201
msgid "Agent"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:200 res/pages/dashboard.php:55
msgid "Date"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:199
msgid "requested"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:192
msgid "coming from"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:182
msgid "Opens in a new tab"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:157
msgid "Invalid request - forceload"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:155
msgid "Invalid request - lastID"
msgstr ""

#: res/inc/SwpaLiveTraffic.php:153
msgid "Invalid request - nonce"
msgstr ""

#: res/inc/SwpaInfo.php:243
msgid "PHP XML support"
msgstr ""

#: res/inc/SwpaInfo.php:242
msgid "PHP IPTC support"
msgstr ""

#: res/inc/SwpaInfo.php:241
msgid "PHP Exif support"
msgstr ""

#: res/inc/SwpaInfo.php:240
msgid "PHP Max Script Execute Time"
msgstr ""

#: res/inc/SwpaInfo.php:239
msgid "PHP Max Post Size"
msgstr ""

#: res/inc/SwpaInfo.php:238
msgid "PHP Max Upload Size"
msgstr ""

#: res/inc/SwpaInfo.php:237
msgid "PHP Memory Limit"
msgstr ""

#: res/inc/SwpaInfo.php:236
msgid "PHP Allow URL fopen"
msgstr ""

#: res/inc/SwpaInfo.php:235
msgid "PHP Safe Mode"
msgstr ""

#: res/inc/SwpaInfo.php:234
msgid "SQL Mode"
msgstr ""

#: res/inc/SwpaInfo.php:228
msgid "MYSQL Version"
msgstr ""

#: res/inc/SwpaInfo.php:227
msgid "PHP Version"
msgstr ""

#: res/inc/SwpaInfo.php:226
msgid "Memory usage"
msgstr ""

#: res/inc/SwpaInfo.php:225
msgid "Server"
msgstr ""

#: res/inc/SwpaInfo.php:224
msgid "Operating System"
msgstr ""

#: res/inc/SwpaInfo.php:220
msgid "XML (eXtensible Markup Language) is a data format for structured document interchange on the Web. It is a standard defined by the World Wide Web Consortium (W3C)."
msgstr ""

#: res/inc/SwpaInfo.php:216
msgid ""
"IPTC data is a method of storing textual information in images defined by the International Press Telecommunications Council.r\n"
"            It was developed for press photographers who need to attach information to images when they are submitting them electronically but it is useful for all photographers.r\n"
"            It provides a standard way of storing information such as captions, keywords, location. Because the information is stored in the image in a standard way this informationr\n"
"            can be accessed by other IPTC aware applications."
msgstr ""

#: res/inc/SwpaInfo.php:214
msgid ""
"PHP exif extension enables you to work with image meta data. For example, you may use exif functions to read meta data of pictures taken from digital cameras by working withr\n"
"            information stored in the headers of the JPEG and TIFF images."
msgstr ""

#: res/inc/SwpaInfo.php:212
msgid ""
"PHP max_execution_time option sets the maximum time in seconds a script is allowed to run before it is terminated by the parser.r\n"
"            This helps prevent poorly written scripts from tying up the server."
msgstr ""

#: res/inc/SwpaInfo.php:210
msgid ""
"PHP post_max_size option limits the maximum size of the POST request that PHP will process. Attackers may attempt to send grossly oversized POST requests to exhaust your system resources;r\n"
"            by setting a realistic value here you can mitigate some of the damage by those attacks."
msgstr ""

#: res/inc/SwpaInfo.php:208
msgid ""
"PHP upload_max_filesize option limits the maximum size of files that PHP will accept through uploads. Attackers may attempt to send grossly oversized files to exhaust your system resources;r\n"
"            by setting a realistic value here you can mitigate some of the damage by those attacks."
msgstr ""

#: res/inc/SwpaInfo.php:205
msgid ""
"PHP memory_limit option sets the maximum amount of memory in bytes that a script is allowed to allocate.r\n"
"            By enabling a realistic memory_limit you can protect your applications from certain types of Denial of Service attacks, and also from bugs inr\n"
"            applications (such as infinite loops, poor use of image based functions, or other memory intensive mistakes)."
msgstr ""

#: res/inc/SwpaInfo.php:203
msgid ""
"PHP allow_url_fopen option, if enabled (allows PHP's file functions - such as 'file_get_contents()' and the 'include' and 'require' statements),r\n"
"            can retrieve data from remote locations, like an FTP or web site, which may pose a security risk."
msgstr ""

#: res/inc/SwpaInfo.php:200
msgid ""
"The PHP Safe Mode (safe_mode) is an attempt to solve the shared-server security problem.r\n"
"            It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren'tr\n"
"            very realistic, many people, especially ISP's, use safe mode for now."
msgstr ""

#: res/inc/SwpaInfo.php:194
msgid ""
"SQL Mode (sql_mode) is a MySQL system variable. By means of this variable the MySQL Server SQL Mode is controlled.r\n"
"            Many operational characteristics of MySQL Server can be configured by setting the SQL Mode.r\n"
"            By setting the SQL Mode appropriately, a client program can instruct the server how strict or forgiving to be about accepting input data, enable or disable behaviors relating to standard SQL conformance,r\n"
"            or provide better compatibility with other database systems. By default, the server uses a sql_mode value of  ''  (the empty string), which enables no restrictions.r\n"
"            Thus, the server operates in forgiving mode (non-strict mode) by default. In non-strict mode, the MySQL server converts erroneous input values to the closest legalr\n"
"            values (as determined from column definitions) and continues on its way."
msgstr ""

#: res/inc/SwpaInfo.php:188 res/inc/SwpaInfo.php:190 res/inc/SwpaInfo.php:192
#: res/pages/tpl/box-database-change-prefix.php:42
#: res/pages/tpl/box-database-change-prefix.php:48
msgid "No"
msgstr ""

#: res/inc/SwpaInfo.php:187 res/inc/SwpaInfo.php:189 res/inc/SwpaInfo.php:191
#: res/pages/tpl/box-database-change-prefix.php:40
#: res/pages/tpl/box-database-change-prefix.php:46
msgid "Yes"
msgstr ""

#: res/inc/SwpaInfo.php:185
msgid " MByte"
msgstr ""

#: res/inc/SwpaInfo.php:178 res/inc/SwpaInfo.php:180 res/inc/SwpaInfo.php:182
#: res/inc/SwpaInfo.php:184 res/inc/SwpaInfo.php:186
msgid "N/A"
msgstr ""

#: res/inc/SwpaInfo.php:174 res/inc/SwpaInfo.php:176
msgid "Off"
msgstr ""

#: res/inc/SwpaInfo.php:173 res/inc/SwpaInfo.php:175
msgid "On"
msgstr ""

#: res/inc/SwpaInfo.php:171
msgid "Not set"
msgstr ""

#: res/inc/SwpaInfo.php:158
msgid "The <code>index.php</code> file <code>was not found</code> in the uploads directory! You should create one in order to prevent directory listings."
msgstr ""

#: res/inc/SwpaInfo.php:156
msgid "The <code>index.php</code> file <code>was found</code> in the uploads directory."
msgstr ""

#: res/inc/SwpaInfo.php:148
msgid "The <code>index.php</code> file <code>was not found</code> in the themes directory! You should create one in order to prevent directory listings."
msgstr ""

#: res/inc/SwpaInfo.php:145
msgid "The <code>index.php</code> file <code>was found</code> in the themes directory."
msgstr ""

#: res/inc/SwpaInfo.php:134
msgid "The <code>index.php</code> file <code>was found</code> in the plugins directory."
msgstr ""

#: res/inc/SwpaInfo.php:126
msgid "The <code>index.php</code> file <code>was not found</code> in the wp-content directory! You should create one in order to prevent directory listings."
msgstr ""

#: res/inc/SwpaInfo.php:123
msgid "The <code>index.php</code> file <code>was found</code> in the wp-content directory."
msgstr ""

#: res/inc/SwpaInfo.php:114
msgid "Your currently used User to access the WordPress Database is missing the following rights to interact with the database: %s"
msgstr ""

#: res/inc/SwpaInfo.php:109
msgid "Your currently used User to access the WordPress Database holds the appropriate rights to interact with the database."
msgstr ""

#: res/inc/SwpaInfo.php:102
msgid ""
"Your currently used User to access the WordPress Database <code>holds too many rights</code>.r\n"
"                We suggest that you limit his rights (to only %s) or to use another User with more limited rights instead, to increase your website's Security."
msgstr ""

#: res/inc/SwpaInfo.php:89
msgid "The <code>.htaccess</code> file was not found in the <code>wp-admin</code> directory."
msgstr ""

#: res/inc/SwpaInfo.php:85
msgid "The <code>.htaccess</code> file was found in the <code>wp-admin</code> directory."
msgstr ""

#: res/inc/SwpaInfo.php:78
msgid "User <code>admin</code> was found! You should change it in order to avoid user enumeration attacks."
msgstr ""

#: res/inc/SwpaInfo.php:75
msgid "User <code>admin</code> was not found."
msgstr ""

#: res/inc/SwpaInfo.php:65
msgid "Startup errors <code>are displayed</code>."
msgstr ""

#: res/inc/SwpaInfo.php:62
msgid "Startup errors <code>are not</code> displayed."
msgstr ""

#: res/inc/SwpaInfo.php:54
msgid "The Wordpress version <code>is</code> hidden for all users but administrators."
msgstr ""

#: res/inc/SwpaInfo.php:48
msgid "Your database prefix is not <code>wp_</code>."
msgstr ""

#: res/inc/SwpaInfo.php:45 res/inc/SwpaInfo.php:90
msgid "read more"
msgstr ""

#: res/inc/SwpaInfo.php:44
msgid "Your database prefix should not be <code>wp_</code>."
msgstr ""

#: res/inc/SwpaInfo.php:35
msgid "An error has occurred while trying to retrieve the status of your Wordpress version."
msgstr ""

#: res/inc/SwpaInfo.php:15 res/inc/SwpaInfo.php:23
msgid "You have the latest version of Wordpress."
msgstr ""

#: res/inc/SwpaCheck.php:279
msgid ""
"<p>A default WordPress installation contains a readme.html file.r\n"
"                        This file is a simple html file that does not contain executable content that can be exploited by hackers or malicious users.r\n"
"                        Still, this file can provide hackers the version of your WordPress installation, therefore it is important to either delete this file or make it inaccessible for your visitors.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:278
msgid "The <strong>readme.html</strong> file was not found in the root directory"
msgstr ""

#: res/inc/SwpaCheck.php:269
msgid ""
"<p>A default WordPress installation contains a readme.html file.r\n"
"                            This file is a simple html file that does not contain executable content that can be exploited by hackers or malicious users.r\n"
"                            Still, this file can provide hackers the version of your WordPress installation, therefore it is important to either delete this file or make it inaccessible for your visitors.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:268
msgid "The <strong>readme.html</strong> file is not accessible."
msgstr ""

#: res/inc/SwpaCheck.php:259
msgid "The <strong>readme.html</strong> file is either empty or not accessible."
msgstr ""

#: res/inc/SwpaCheck.php:253
msgid ""
"<p>This plugin can automatically delete its content if the option <strong>\"%s\"</strong> is checked on the plugin's settings page.r\n"
"                                You can also delete this file manually by connecting to your website through an FTP connection.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:250 res/inc/SwpaCheck.php:260
msgid ""
"<p>A default WordPress installation contains a readme.html file.r\n"
"                                This file is a simple html file that does not contain executable content that can be exploited by hackers or malicious users.r\n"
"                                Still, this file can provide hackers the version of your WordPress installation, therefore it is important to either delete this file or make it inaccessible for your visitors.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:249
msgid "The <strong>readme.html</strong> file was found in the root directory"
msgstr ""

#: res/inc/SwpaCheck.php:226
msgid "<p>Please refer to this <a href=\"%s\" target=\"%s\">article</a> for more information on how to create an .htaccess file.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:223 res/inc/SwpaCheck.php:233
msgid ""
"<p>An .htaccess file is a configuration file which provides the ability to specify configuration settings for a specific directory in a website.r\n"
"                    The .htaccess file can include one or more configuration settings which apply only for the directory in which the .htaccess file has been placed.r\n"
"                    So while web servers have their own main configuration settings file, the .htaccess file can be used to override their main configuration settings.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:203
msgid ""
"<p>This plugin can automatically create an empty <strong>\"%s\"</strong> file in the following directories: wp-content, wp-content/plugins, wp-content/themes and wp-content/uploads if ther\n"
"                        option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:201
msgid ""
"<p>A directory listing provides an attacker with the complete index of all the resources located inside of the directory. The specific risks and consequences vary depending on which files are listed and accessible.</p>r\n"
"                        <p>Therefore, it is important to protect your directories by having an empty index.php or index.htm file inside them.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:145 res/inc/SwpaCheck.php:166
#: res/inc/SwpaCheck.php:187 res/inc/SwpaCheck.php:210
#: res/inc/SwpaCheck.php:232
msgid "The <strong>\"%s\"</strong> file was found in the <strong>\"%s\"</strong> directory"
msgstr ""

#: res/inc/SwpaCheck.php:138 res/inc/SwpaCheck.php:159
#: res/inc/SwpaCheck.php:180
msgid ""
"<p>This plugin can automatically create an empty <strong>\"%s\"</strong> file in the following directories: wp-content, wp-content/plugins, wp-content/themes and wp-content/uploads ifr\n"
"                            the option <strong>\"%s\"</strong> is checked on the plugin's settings page.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:136 res/inc/SwpaCheck.php:146
#: res/inc/SwpaCheck.php:157 res/inc/SwpaCheck.php:167
#: res/inc/SwpaCheck.php:178 res/inc/SwpaCheck.php:188
#: res/inc/SwpaCheck.php:211
msgid ""
"<p>A directory listing provides an attacker with the complete index of all the resources located inside of the directory. The specific risks and consequences vary depending on which files are listed and accessible.</p>r\n"
"                    <p>Therefore, it is important to protect your directories by having an empty index.php or index.htm file inside them.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:135 res/inc/SwpaCheck.php:156
#: res/inc/SwpaCheck.php:177 res/inc/SwpaCheck.php:200
#: res/inc/SwpaCheck.php:222
msgid "The <strong>\"%s\"</strong> file was not found in the <strong>\"%s\"</strong> directory"
msgstr ""

#: res/inc/SwpaCheck.php:116
msgid ""
"<p>It is recommended to update your WordPress installation as soon as possible. More information on updating WordPress manually and automaticallyr\n"
"                                    can be found on the official <a href=\"%s\" target=\"%s\">WordPress site</a>.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:113
msgid ""
"<p>The latest WordPress version is usually more stable and secure, and is only released to include new features or fix technical and WordPress security bugs;r\n"
"                                    making it an important part of your website administration to keep up to date since some fixes might resolve security issues.<p>r\n"
"                                <p>Running an older WordPress version could put your blog security at risk, allowing a hacker to exploit known vulnerabilities for your specific version and take full control over your web server.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:112
msgid "An updated version of WordPress is available: <strong>%s</strong>"
msgstr ""

#: res/inc/SwpaCheck.php:93 res/inc/SwpaCheck.php:105
msgid ""
"<p>The latest WordPress version is usually more stable and secure, and is only released to include new features or fix technical and WordPress security bugs;r\n"
"                            making it an important part of your website administration to keep up to date since some fixes might resolve security issues.<p>r\n"
"                        <p>Running an older WordPress version could put your blog security at risk, allowing a hacker to exploit known vulnerabilities for your specific version and take full control over your web server.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:92 res/inc/SwpaCheck.php:104
msgid "You have the latest version of WordPress installed"
msgstr ""

#: res/inc/SwpaCheck.php:73
msgid ""
"<p>The majority of reported WordPress database security attacks were performed by exploiting SQL Injection vulnerabilities.r\n"
"                        By renaming the WordPress database table prefixes you are securing your WordPress blog and website from zero day SQL injections attacks.</p>r\n"
"                    <p>Therefore by renaming the WordPress database table prefixes, you are automatically enforcing your WordPress database security against such dangerous attacks because the attacker would not be able to guess the table names.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:72
msgid "The default WordPress database prefix is not used"
msgstr ""

#: res/inc/SwpaCheck.php:65
msgid "<p>This plugin can automatically <a href=\"%s\">do this</a> for you, but if you want to do it manually then please read this <a href=\"%s\" target=\"%s\">article</a> first.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:60
msgid ""
"<p>The majority of reported WordPress database security attacks were performed by exploiting SQL Injection vulnerabilities.r\n"
"                        By renaming the WordPress database table prefixes you are securing your WordPress blog and website from zero day SQL injections attacks.</p>r\n"
"                    <p>Therefore by renaming the WordPress database table prefixes, you are automatically enforcing your WordPress database security against such dangerous attacksr\n"
"                        because the attacker would not be able to guess the table names.</p>r\n"
"                    <p>We recommend to use difficult to guess prefixes, like long random strings which include both letters and numbers.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:59
msgid "The default WordPress database prefix (<strong>%s</strong>) is used"
msgstr ""

#: res/inc/SwpaCheck.php:38
msgid ""
"<p>Do not make the following change unless you are comfortable working with PHPMyAdmin and MySQL. If not, ask someone who is familiar with WordPress and MySQL to assist you. </p>r\n"
"                            <p>Also, it is of utmost importance to backup your whole blog - including the database - before making any of the changes described below.</p>r\n"
"                            <p>To change your WordPress default admin username, navigate to your web host's MySQL administration tool (probably PHPMyAdmin) and browse to your WordPress database.r\n"
"                            Locate the users table, in which you will find a user_login column. One of the rows will contain admin in the field.r\n"
"                            Change this to a complex and hard-to-guess name, which ideally consists of alpha-numeric characters.</p>r\n"
"                            <p><strong>IMPORTANT:</strong> Even if the username is hard to guess, you will still need a very strong password.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:33
msgid ""
"<p>One well known and dangerous WordPress security vulnerability is User Enumeration, in which a malicious user is able to enumerater\n"
"                            a valid WordPress user account to launch a brute force attack against it.</p>r\n"
"                            <p>In order to help deter this type of attack, you should change your default <a href=\"%s\" target=\"%s\">WordPress administrator</a>r\n"
"                            username to something more difficult to guess.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:32
msgid "The default user <strong>\"%s\"</strong> was found"
msgstr ""

#: res/inc/SwpaCheck.php:19
msgid ""
"<p>One well known and dangerous WordPress security vulnerability is User Enumeration, in which ar\n"
"                            malicious user is able to enumerate a valid WordPress user account to launch a brute force attack against it.r\n"
"                            In order to help deter this type of attack, it is important not to have the default <a href=\"%s\" target=\"%s\">WordPress administrator</a>r\n"
"                            username enabled on your blog.</p>"
msgstr ""

#: res/inc/SwpaCheck.php:18
msgid "User <strong>\"%s\"</strong> (with administrative rights) was not found"
msgstr ""