Skip to content
Bernhard Froehler edited this page Nov 13, 2017 · 48 revisions

Changes 1.4.1 -> 1.5.0

To be done

Changes 1.4.0 -> 1.4.1

To be done

Changes 1.3.0 -> 1.4.0

To be done

Changes 1.2.0 -> 1.3.0

In the plugin (bfstop)

File language/[en-GB]/[en-GB].plg_system_bfstop.ini, added lines:

PASSWORD_RESET_RECOMMENDED="It was noticed that one or more of your login attempts have recently failed. When trying again, you will soon be blocked. It is therefore recommended that you use the <a href="%1$s">functionality to reset your password</a>!"
BLOCKED_CLIENT_IP="Your IP address is: %s."

File language/[en-GB]/[en-GB].plg_system_bfstop.sys.ini, added lines:

NOTIFY_USE_PASSWORD_REMINDER_LABEL="Password reset reminder"
NOTIFY_USE_PASSWORD_REMINDER_DESC="Whether and when to show a reminder about using the password reminder functionality on a failed login"
REMINDER_NOTIFY_ALWAYS="Always"
REMINDER_NOTIFY_1LEFT="When 1 attempt left"
REMINDER_NOTIFY_2LEFT="When 2 attempts left"
BLOCKED_MSG_SHOWIP_LABEL="Show IP"
BLOCKED_MSG_SHOWIP_DESC="When blocked, show the user his IP address (as perceived by the server)"

Changes 1.2.0beta1 -> 1.2.0

In the component (com_bfstop), file admlang/[en-GB]/[en-GB].com_bfstop.ini:

Removed lines (done for all languages already):

COM_BFSTOP_DESC_IPADDRESS="The IP address to be blocked"
COM_BFSTOP_DESC_CRDATE="The start date/time of blocking"

Added lines (distinguish between blocked/whitelisted IP address/date, and add hint on how to specify a subnet):

COM_BFSTOP_DESC_BLOCK_IPADDRESS="The IP address (or subnet) to be blocked. Subnets are specified in CIDR suffix notation, i.e. in the form <subnet address>/<mask bits>, e.g. '192.168.0.0/24'. Be careful when entering a subnet, so not to block your own IP!"
COM_BFSTOP_DESC_BLOCK_CRDATE="The start date/time of blocking"
COM_BFSTOP_DESC_WHITELIST_IPADDRESS="The IP address (or subnet) for which the access to this site shall always be allowed (this disables all blocks or checks done by the plugin). Subnets are specified in CIDR suffix notation, i.e. in the form <subnet address>/<mask bits>, e.g. '192.168.0.0/24'"
COM_BFSTOP_DESC_WHITELIST_CRDATE="The start date/time of whitelisting. Currently unused."

Changes 1.1.0/1.1.1 -> 1.2.0beta1

In the plugin (bfstop), file [en-GB].plg_system_bfstop.sys.ini:

Added lines:

BLOCK_1WEEK="1 Week"
BLOCK_30DAYS="30 Days"
NOTIFICATION_FIELDSET_LABEL="Notification"
GROUP_NOTIFICATION_ENABLED_LABEL="User group notification"
GROUP_NOTIFICATION_ENABLED_DESC="If enabled, the whole user group selected below will be notified in case of failed logins/banned IPs"
USERGROUP_LABEL="User group"
USERGROUP_DESC="Choose a user group from which to notify every member about failed logins and banned IPs (if activated above). Probably you will want to create a dedicated group for this, or use a group which holds only your most experienced administrators, like the default 'Super Users' group."

Changed lines (adapted to reflect that now multiple addresses can be entered):

EMAIL_ADDRESS_LABEL="Email Address(es)"
EMAIL_ADDRESS_DESC="Enter the Email Address(es) where you would like to have notifications to be sent. If you want to specify more than one address, separate them by the semicolon character (;)."

In the component (com_bfstop), file admlang/[en-GB]/{en-GB].com_bfstop.ini

Changed line (to reflect the fact that mostly missing to select a user or a group or specifying an email addresses in the plugin settings would make sending fail):

TEST_NOTIFICATION_FAILED="Sending the test notification failed! Please check your eMail configuration in the Joomla! configuration; also check that you have entered a (correct) email address and/or have chosen a user or group in the plugin configuration."

Removed lines (should already be done for all languages):

EMAIL_SOURCE_LABEL
EMAIL_SOURCE_DESC
SELECTEDUSERS
CUSTOMEMAILADDRESS

Changes 1.0.0 -> 1.1.0

In the plugin (bfstop):

Added lines in [en-GB].plg_system_bfstop.sys.ini:

DELETE_OLD_ENTRIES_LABEL="Delete old entries"
DELETE_OLD_ENTRIES_DESC="Delete entries older than the number of weeks given in this field (set to 0 to disable deletion of old entries)."
ADAPTIVE_DELAY_LABEL="Adaptive Delay"
ADAPTIVE_DELAY_DESC="Adapt delay to the current rate of failed logins. Will increase the delay whenever there is an increased number of logins as a countermeasure for distributed attacks."
ADAPTIVE_DELAY_MAX_LABEL="Maximum delay"
ADAPTIVE_DELAY_MAX_DESC="The maximum delay for the response on failed login attempts when adaptive delay is turned on"
ADAPTIVE_DELAY_THRSH_MIN_LABEL="Minimum threshold"
ADAPTIVE_DELAY_THRSH_MIN_DESC="The threshold at which the adaptive delay starts to kick in (measured in number of failed logins in the last hour)"
ADAPTIVE_DELAY_THRSH_MAX_LABEL="Maximum threshold"
ADAPTIVE_DELAY_THRSH_MAX_DESC="The threshold at which the adaptive delay reaches the maximum delay (measured in number of failed logins in the last hour)"
DELAY_FIELDSET_LABEL="Delay"

Changed line in [en-GB].plg_system_bfstop.ini (the line prefixed with "-" is the old entry, which was replaced by the one with prefix "+"):

-BLOCKED_IP_ADDRESS_BODY="Blocked IP Addresss %1$s because there were too many unsuccessful login attempts in a short time on %2$s. These are the attempts:\n\n%3$s"
+BLOCKED_IP_ADDRESS_BODY="Blocked IP Addresss %1$s because there were too many unsuccessful login attempts in a short time on %2$s. These are all the attempts from that address that were recorded:\n\n%3$s\n\nNotice: This might be more than those causing the block; there might have been attempts further back, which already caused a temporary block then, or which were further apart than what is considered for blocking!"

In the component (com_bfstop):

New lines in admlang[en-GB].com_bfstop.ini:

COM_BFSTOP_HEADING_IPINFO="Information for IP Address %s"
COM_BFSTOP_SUBMENU_WHITELIST="Whitelist"
COM_BFSTOP_HEADING_WHITELIST="Brute Force Stop: Whitelist"
COM_BFSTOP_WHITELIST_DELETE_CONFIRM="Are you sure you want to delete the marked IP-Address(es)?"

Changes 0.9.11 -> 1.0.0beta1

In the plugin: language/en-GB/en-GB.plg_system_bfstop.sys.ini:

+USE_HTTP_ERROR_LABEL="Use HTTP Error"
+USE_HTTP_ERROR_DESC="If enabled, bfstop will send a status code 403 (Forbidden) if the users' IP address is blocked"

In the component: admlang/en-GB/en-GB.com_bfstop.ini:

+BLOCKED_PERMANENTLY="Blocked permanently" 

Changes 0.9.11beta1 -> 0.9.11

en-GB.plg_system_bfstop.sys.ini (Please check the file here for the actual content: [https://github.com/codeling/bfstop/blob/master/language/en-GB/en-GB.plg_system_bfstop.sys.ini]):

-LOGGING_ENABLED_LABEL="Logging"
-LOGGING_ENABLED_DESC="Determines whether a Logfile about the activities of the plugin should be created (this should only be necessary in case of a problem; the logfile can be found in the logs directory under the name plg_system_bfstop.log.php)"
+LOGLEVEL_LABEL="Logging"
+LOGLEVEL_DESC="Determines whether a Logfile about the activities of the plugin should be created (this should only be necessary in case of a problem; the logfile can be found in the logs directory under the name plg_system_bfstop.log.php). You can also configure how detailed the log should be; e.g. set to ERROR to only get information about every malfunction into the logfile."
+FATAL="Fatal error"
+INFO="Informational message"
+DEBUG="Detailed information"

admlang/en-GB/en-GB.com_bfstop.ini (Please check the file here for the actual content: https://github.com/codeling/com_bfstop/blob/master/admlang/en-GB/en-GB.com_bfstop.ini ):

-STILL_BLOCKED="Still Blocked"
-UNBLOCKED_STATE="Entsperrt am %s"
-UNBLOCK_LINK_CAPTION="-> Unblock now"
+BLOCKED_UNTIL="Blocked until %s"
+BLOCK_EXPIRED_AT="Block expired at %s"
-UNBLOCK_INVALIDID="Invalid id: %d."
+UNBLOCK_INVALIDID="Invalid id(s): %s."
+UNBLOCKED_STATE="Unblocked at %s"
+SETTINGS_VIEW_HINT="Here you can check whether the notification configuration of the bfstop plugin is working. To do so now, click the button in the toolbar; a test email will then be sent!"

Changes 0.9.10 -> 0.9.11beta1

administrator/language/xx-XX/xx-XX.plg_system.bfstop.sys.ini:

MAX_BLOCKS_BEFORE_LABEL="Permanent after"
MAX_BLOCKS_BEFORE_DESC="Determines after how many blocked attempts a permanent block will be set up. Blocks which were removed (i.e. unblocked) by token do also count; only those done via the backend will be ignored."
MAX_BLOCK_NEVER="Never"
ENABLED_FOR_ORIGIN_LABEL="Active for"
ENABLED_FOR_ORIGIN_DESC="Determines for which parts of the Joomla! system the plugin should be active. If set to only either frontend or backend, the respective other part will not be considered for any functionality (e.g. if configured only for backend, then failed login attempts in frontend will not be logged; but also successful logins in frontend won't reset the failed login counter). Please note that a block always affects the whole site, no matter what is entered here!"
ENABLED_FOR_FRONTEND="Only Frontend"
ENABLED_FOR_BACKEND="Only Backend"
ENABLED_FOR_BOTH="Frontend and Backend"

administrator/language/xx-XX/xx-XX.plg_system.bfstop.ini:

FAILED_LOGIN_ATTEMPT (added first parameter site name)
BLOCKED_IP_ADDRESS_BODY (added second parameter site URL)
BLOCKED_IP_ADDRESS_SUBJECT (added first parameter site name)

administrator/language/xx-XX/xx-XX.com_bfstop.ini:

COM_BFSTOP_HEADING_DATE (moved from COM_BFSTOP_HEADING_CRDATE, so probably no change required)
COM_BFSTOP_HEADING_DURATION="Duration"
COM_BFSTOP_HEADING_USERNAME="Username"
COM_BFSTOP_HEADING_ERROR="Error"
COM_BFSTOP_HEADING_ORIGIN="Origin"
COM_BFSTOP_SUBMENU_BLOCKLIST="Blocked IPs"
COM_BFSTOP_SUBMENU_FAILEDLOGINLIST="Failed Logins"
COM_BFSTOP_SUBMENU_SETTINGS="Settings"
COM_BFSTOP_HEADING_BLOCKLIST="Brute Force Stop: Blocked IPs"
COM_BFSTOP_HEADING_FAILEDLOGINLIST="Brute Force Stop: Failed Logins"
WARNING_ADMIN_USER_EXISTS="Superuser is using the default username 'admin'. This is a security risk; attackers know that this username exists in many Joomla!-Installations, therefore it is used very commonly in many attacks. To increase security it is recommended to change the username for the Superuser! See also: <a href='http://docs.joomla.org/Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F' target='_blank'>Joomla! Security and Performance FAQ: Why should I immediately change the name of the default admin user after a new install?</a>"
COM_BFSTOP_BLOCK_NEW="Add"
COM_BFSTOP_BLOCK_EDIT="Edit"
COM_BFSTOP_BLOCK_DETAILS="Details"
COM_BFSTOP_UNBLOCK="Unblock"
COM_BFSTOP_DESC_IPADDRESS="The IP address to be blocked"
COM_BFSTOP_DESC_CRDATE="The start date/time of blocking"
COM_BFSTOP_DESC_DURATION="The duration of the block"
TEST_MAIL_BODY="This is a test notification for site %s from Brute Force Stop (bfstop) Joomla! plugin."
TEST_MAIL_SUBJECT="%s: Test Notification"
TEST_NOTIFICATION="Test Notification"
TEST_MAIL_SENT="Sent Message (subject='%s', body='%s') to %s."
TEST_NOTIFICATION_SUCCESS="Sending the test notification seems to have been successful. Please check that you also received an eMail to the abovementioned address!"
TEST_NOTIFICATION_FAILED="Sending the test notification failed! Please check your eMail configuration in the Joomla! configuration!"

Where xx-XX is to be replaced by the respective language shortcut, e.g. en-GB for british english.