PluginProbe
Loginizer / 1.0.1
Loginizer v1.0.1
2.1.0 2.0.9 2.0.8 1.9.8 1.9.9 2.0.0 2.0.1 2.0.2 2.0.3 2.0.4 2.0.5 2.0.6 2.0.7 trunk 1.0 1.0.1 1.0.2 1.1.0 1.1.1 1.2.0 1.3.0 1.3.1 1.3.2 1.3.3 1.3.4 All 74 releases
← All changes | readme.txt +6 -62 1.3.1 → 1.0.1 View file →
@@ -1,10 +1,10 @@
1 1 === Loginizer ===
2 2 Contributors: loginizer
3 -Tags: access, admin, Loginizer, login, logs, ban ip, failed login, ip, whitelist ip, blacklist ip, failed attempts, lockouts, hack, authentication, login, security
3 +Tags: Loginizer, login, logs, ban ip, failed login, ip, whitelist ip, blacklist ip, failed attempts, lockouts, authentication, login, security
4 4 Requires at least: 3.0
5 -Tested up to: 4.6.1
6 -Stable tag: 1.3.1
5 +Tested up to: 4.4.2
6 +Stable tag: 1.0.1
7 7 License: GPLv3 or later
8 8 License URI: http://www.gnu.org/licenses/gpl.html
9 9
10 10 Loginizer is a WordPress plugin which helps you fight against bruteforce attack.
@@ -10,36 +10,12 @@
10 10 Loginizer is a WordPress plugin which helps you fight against bruteforce attack.
11 11
12 12 == Description ==
13 13
14 -Loginizer is a WordPress plugin which helps you fight against bruteforce attack by blocking login for the IP after it reaches maximum retries allowed. You can blacklist or whitelist IPs for login using Loginizer. You can use various other features like Two Factor Auth, reCAPTCHA, PasswordLess Login, etc. to improve security of your website.
14 +Loginizer is a WordPress plugin which helps you fight against bruteforce attack by blocking login for the IP after it reaches maximum retries allowed. You can blacklist or whitelist IPs for login using Loginizer.
15 15
16 -Loginizer is actively used by more than 300000+ WordPress websites.
16 +Features in Loginizer 1.0.1 include:
17 17
18 -You can find our official documentation at <a href="https://loginizer.com/docs">https://loginizer.com/docs</a> and our Frequently Asked Questions on our support portal at <a href="https://loginizer.com/members">https://loginizer.com/members</a>. We are also active in our community support forums on <a href="https://wordpress.org/support/plugin/loginizer">wordpress.org</a> if you are one of our free users. Our Premium Support Ticket System is at <a href="https://loginizer.com/members">https://loginizer.com/members</a>
19 -
20 -= Get Support and Pro Features =
21 -
22 -Get professional support from our experts and pro features to take your site's security to the next level with <a href="https://loginizer.com/pricing">Loginizer-Security</a>.
23 -
24 -Pro Features :
25 -
26 -* MD5 Checksum - of Core WordPress Files. The admin can check and ignore files as well.
27 -* PasswordLess Login - At the time of Login, the username / email address will be asked and an email will be sent to the email address of that account with a temporary link to login.
28 -* Two Factor Auth via Email - On login, an email will be sent to the email address of that account with a temporary 6 digit code to complete the login.
29 -* Two Factor Auth via App - The user can configure the account with a 2FA App like Google Authenticator, Authy, etc.
30 -* Login Challenge Question - The user can setup a <i>Challenge Question and Answer</i> as an additional security layer. After Login, the user will need to answer the question to complete the login.
31 -* reCAPTCHA - Google's reCAPTCHA can be configured for the Login screen, Comments Section, Registration Form, etc. to prevent automated brute force attacks. Supports WooCommerce as well.
32 -* Rename Login Page - The Admin can rename the login URL (slug) to something different from wp-login.php to prevent automated brute force attacks.
33 -* Rename Login with Secrecy - If set, then all Login URL's will still point to wp-login.php and users will have to access the New Login Slug by typing it in the browser.
34 -* Disable XML-RPC - An option to simply disable XML-RPC in WordPress. Most of the WordPress users don't need XML-RPC and can disable it to prevent automated brute force attacks.
35 -* Rename XML-RPC - The Admin can rename the XML-RPC to something different from xmlrpc.php to prevent automated brute force attacks.
36 -* Change the Admin Username - The Admin can rename the admin username to something more difficult.
37 -* Auto Blacklist IPs - IPs will be auto blacklisted, if certain usernames saved by the Admin are used to login by malicious bots / users.
38 -* Disable Pingbacks - Simple way to disable PingBacks.
39 -
40 -Features in Loginizer include:
41 -
42 18 * Blocks IP after maximum retries allowed
43 19 * Extended Lockout after maximum lockouts allowed
44 20 * Email notification to admin after max lockouts
45 21 * Blacklist IP/IP range
@@ -58,43 +34,11 @@
58 34
59 35 == Screenshots ==
60 36
61 37 1. Login Failed Error message
62 -2. Loginizer Dashboard page
63 -3. Loginizer Brute Force Settings page
38 +2. Loginizer Settings page
64 39
65 40 == Changelog ==
66 -
67 -= 1.3.1 =
68 -* [Feature] The Login attempt logs will now be shown as per the last attempt TIME and in Descending Order
69 -* [Feature] Added an option to Reset the Login attempts for all or specific IPs
70 -
71 -= 1.3.0 =
72 -* [Feature] Added pagination in the Brute Force Logs Wizard
73 -* [Bug Fix] Disabling and Re-Enabling Loginizer caused an SQL error
74 -
75 -= 1.2.0 =
76 -* [Task] The brute force logs will now be sorted as per the time of failed login attemps
77 -* [Bug Fix] Dashboard showed wrong permissions if wp-content path had been changed
78 -* [Bug Fix] Added Directory path to include files which caused issues with some plugins
79 -
80 -= 1.1.1 =
81 -* [Bug Fix] Added ABSPATH instead of get_home_path()
82 -
83 -= 1.1.0 =
84 -
85 -* [Feature] New Dashboard
86 -* [Feature] System Information added in the new Dashboard
87 -* [Feature] File Permissions added in the new Dashboard
88 -* [Feature] New UI
89 -* [Bug Fix] Fixed bug to add IP Range from 0.0.0.1 - 255.255.255.255
90 -* [Bug Fix] Removed /e from preg_replace causing warnings in PHP
91 -
92 -= 1.0.2 =
93 -
94 -* Fixed Extended Lockout bug
95 -* Fixed Lockout bug
96 -* Handle login attempts via XML-RPC
97 41
98 42 = 1.0.1 =
99 43
100 44 * Database structure changes to make the plugin work faster