Released Version 1.1.4

Author: Rafael Grigorian

CHANGELOG.md

@@ -81,3 +81,8 @@
 
 ## Version 1.1.3
 -   Fixed GH-7, password lifetime issue with Enterprise_Pci module on EE
+
+## Version 1.1.4
+-   Fixed GH-11, Admin Base URL Missing From Admin Email
+-   Fixed GH-12, Email Is Sent To Inactive Admin Users On Ban
+-   Fixed GH-13, Replace 'mt_rand' With 'random_int'

README.md

@@ -3,7 +3,7 @@
 
 ![](https://img.shields.io/badge/Magento-1-orange.svg?style=for-the-badge)
 ![](https://img.shields.io/badge/License-MIT-orange.svg?style=for-the-badge)
-![](https://img.shields.io/badge/Version-1.1.3-orange.svg?style=for-the-badge)
+![](https://img.shields.io/badge/Version-1.1.4-orange.svg?style=for-the-badge)
 ![](https://img.shields.io/badge/Stability-Stable-orange.svg?style=for-the-badge)
 
 <p align="center" >

conf/package.xml

@@ -1,4 +1,4 @@
-<?xml version="1.0"?>
+<?xml version="1.0" ?>
 <package>
 	<name>JetRails_TwoFactor</name>
 	<version></version>
@@ -9,29 +9,8 @@
 	<channel>community</channel>
 	<extends/>
 	<summary>The JetRails 2FA plugin adds an extra layer of security to your Magento store.  User-based 2FA enablement ensures that admin users are following best security practices.</summary>
-	<description>
-		Your Magento storefront is vulnerable. Eliminate your security risk by downloading the JetRails Two-factor authentication module. Two-factor authentication, also known as 2FA, is a critical component for Magento security and is used widely by Magento backend admin users. Authentication is a security process to verify a user's identity. Authentication consists of three factors; something they know (ie. password), something they have (ie. phone), or something they are (ie. fingerprint).
-		With a stock Magento installation a user is only given one method of authentication -- something they know. This usually consists of their administrative username and password. While having one method of authentication is typically secure, it has its limitations. By adding one additional layer of authentication, security is significantly strengthened. Having multiple methods of authentication is known as multi-factor authentication. It is often recommended that you choose at least two out of the three methods of authentication to ensure strong security.
-		This plugin works with "something they know" and "something they have". A Magento admin user that has the JetRails 2FA plugin enabled will not only be authenticated with "something they know", which would be their admin username and password, but they will also authenticate with "something they have", such as their phone or tablet.
-		Once the JetRails 2FA plugin is installed for your Magento store and an admin successfully logs into their account, the JetRails 2FA plugin will prompt the user to set up their 2FA account. The typical user enrollment process takes up to five minutes including installation of the Google Authenticator application on their device. For more information on using the JetRails 2FA plugin, make sure to read the user guide which offers visual step-by-step instructions.
-		2FA has become an industry standard and is implemented using the Time-Based One-Time Password (TOTP) algorithm. In developing this plugin, RFC-6238 was used for reference. Since 2FA gives an extra layer of protection to Magento’s authentication process, it is vital to every Magento installation.
-
-		This plugin comes with the following features and benefits:
-
-		- A Master Administrator can require 2FA to be utilized by specific users.
-		- Usage of 2FA can be enforced and required for log in.
-		- Once you use the 2FA to log in, there is an option to bypass authentication for a pre-configured number of days.
-		- A Master Administrator can oversee every user's authentication process.
-		- In the event of a lost or misplaced 2FA account, backup codes are available as an alternate method for authentication.
-		- In the event of an attempted account breach, prevention protocols are in place via brute-force protection, which will temporarily block the account.
-		- The threshold for the number of failed authentication attempts before a temporary ban is imposed is configurable.
-		- The duration of a user's temporary ban is configurable.
-		- An automatic instantaneous alert will be sent to the account owner and store admins informing them of an attempted breach. Any security warning will be logged with any relevant data such as the offender's IP address.
-		- The 2FA account can be setup for devices (something they have) using the Google Authenticator app, which is available for every platform including iPhone and Android.
-	</description>
-	<notes>
-		- Fixed GH-7, password lifetime issue with Enterprise_Pci module on EE
-	</notes>
+	<description>https://github.com/jetrails/magento-twofactor</description>
+	<notes>Released Version 1.1.4</notes>
 	<authors>
 		<author>
 			<name>Rafael Grigorian</name>

package.json

@@ -1,5 +1,5 @@
 {
-	"version": "1.1.3",
+	"version": "1.1.4",
 	"name": "magento-twofactor",
 	"description": "User based 2FA enablement for admin users in Magento 1.x",
 	"author": "Rafael Grigorian",

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Configure/Edit.php

@@ -4,7 +4,7 @@
 	 * Edit.php - This class exists to simply tell Magento's grid system where to look for the
 	 * proper controller for the configure page.  It also specifies the proper block group within
 	 * the constructor.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Configure
 	 * @author          Rafael Grigorian - JetRails®

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Configure/Edit/Form.php

@@ -3,7 +3,7 @@
 	/**
 	 * Form.php - This class initializes the form, field-set, and form fields that will exist on the
 	 * configure page.  All information is set in the _prepareForm method.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Edit
 	 * @author          Rafael Grigorian - JetRails®

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Manage/Container.php

@@ -4,7 +4,7 @@
 	 * Container.php - This class exists to simply tell Magento's grid system where to look for the
 	 * proper controller for the configure page.  It also specifies the proper block group within
 	 * the constructor.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Manage
 	 * @author          Rafael Grigorian - JetRails®

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Manage/Container/Grid.php

@@ -4,7 +4,7 @@
 	 * Grid.php - This class defines what collection to use for the grid collection.  It also
 	 * defines all the columns for the grid widget.  Additionally it defines all the mass-action
 	 * options for the widget grid.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Container
 	 * @author          Rafael Grigorian - JetRails®

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Renderer/Manage/Address.php

@@ -4,7 +4,7 @@
 	 * Address.php - This class is a renderer class that is used with the grid widget's columns.
 	 * These classes are used to load information from the authentication model using the admin
 	 * user's id.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Manage
 	 * @author          Rafael Grigorian - JetRails®

src/app/code/community/JetRails/TwoFactor/Block/Adminhtml/Renderer/Manage/State.php

@@ -4,7 +4,7 @@
 	 * State.php - This class is a renderer class that is used with the grid widget's columns.
 	 * These classes are used to load information from the authentication model using the admin
 	 * user's id.
-	 * @version         1.1.3
+	 * @version         1.1.4
 	 * @package         JetRails® TwoFactor
 	 * @category        Manage
 	 * @author          Rafael Grigorian - JetRails®