Lynbro Login Guard Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Three things guard a WordPress sign-in page, and this plugin does all three on
your own server: it moves the page to an address of your choosing, it makes
failed sign-ins cost time, and it can ask for a code from an authenticator app
after the password.
There is no account to create, no API key to paste, nothing to pay for and
nothing sent anywhere. Every automatic decision is written down in plain
language, and every one of them can be undone in a click.
Source code and issue tracker on GitHub:
https://github.com/andrey-tut/lynbro-login-guard
You cannot lock yourself out
This is the part that usually goes wrong, so it is the part built first. Plugins
that move the sign-in page are famous for one support thread: “I changed the
address and now I cannot get in.” There are three ways back here, and the
plugin tells you about them before you need them.
- The address is shown, in full, on the plugin’s own screen — and e-mailed to
your site’s administration address, from your own site, whenever it changes. - WP-CLI:
wp lynbro-login-guard urlprints it,wp lynbro-login-guard off
puts the page back where WordPress had it. - One line in
wp-config.phpswitches every guard in the plugin off without
deleting a single setting:
define( ‘LYNBRO_LOGIN_GUARD_DISABLE’, true );
Deactivating the plugin has the same effect. Nothing here can leave you outside
your own site.
Moving the sign-in page
Pick an address and wp-login.php stops showing the form. Visitors who ask for
the old one get your theme’s own 404 page, or the front page, or an address you
choose.
Before the address is saved it is checked against your site: a page, post,
category or tag already living there would swallow the sign-in page and leave
you with a 404, which is exactly what people complain about with other plugins.
If the address will not work, the plugin says why and keeps the one that was
working.
Things that must keep working, keep working: unlocking a password-protected
post, WordPress recovery mode after a fatal error, admin-ajax, admin-post, cron,
WP-CLI and the REST API are all left alone. So is the sign-in page itself for
anybody who is already signed in — locking somebody out of their own log-out
button helps nobody.
Be clear-eyed about what this buys you: a moved address stops the automated
traffic that only ever knocks on wp-login.php. It is one layer, not a lock.
The limit below is what actually stops somebody guessing passwords.
Limiting failed sign-ins
Two counters run side by side, because they answer different questions. One is
keyed on the address and notices a single machine working through passwords.
The other is keyed on the username and notices one account being tried from a
hundred addresses at once — which the first cannot see at all.
Past the limit, that address or that username waits. A repeat offender waits
longer each time, up to a ceiling you set. Every lockout ends by itself: there
is no permanent ban here and there is not going to be one.
Getting the password right clears the counter, so somebody who mistyped twice
and then got in is not one slip away from a lockout tomorrow. Addresses you
list are never limited at all — put your office in there.
Two-factor sign-in
Any authenticator app. The password is checked by WordPress exactly as before;
only then does a second screen ask for six digits. Ten single-use recovery codes
are made when you switch it on, and an administrator can switch two-factor off
for somebody who has lost both their phone and their codes.
The QR code is drawn by this plugin, on your server, and put straight into the
page. Most plugins hand your shared secret to an outside chart service to get a
picture back. That secret is the one value that must never leave your site.
The smaller things that stop a sign-in page answering questions
- Say the same thing whether the username or the password was wrong, so the form
cannot be used to find out which accounts exist. The lost-password form stops
confirming addresses too. - Ignore
/?author=1, which otherwise hands over a username. - Optionally keep the REST API from listing users to strangers, and optionally
switch XML-RPC off. Both are off by default, because both break real sites
when switched on without thinking. - Optionally refuse a list of usernames outright — and if one of them turns out
to belong to a real administrator, it is let through anyway, because that is
almost certainly you.
The journal
Every refusal, lockout and rejected code is recorded with the reason in a
sentence: not “blocked”, but “8 failed sign-ins from this address in 15
minutes, so it is held out for 20 minutes”. One click lets that address back in
and forgets the failures that caused it. Another adds it to the list that is
never limited. The whole journal exports to CSV, and it is deleted after however
many days you choose.
No limits
No caps, no quotas, no counting, nothing switched off after a number. Every
feature here runs on your server and costs us nothing, so it is free, for every
site, for as long as you have the plugin.
External Services
This plugin’s own features do not connect to any external service. Nothing is sent anywhere,
and no code, font, script or image is loaded from another server.
Two things are worth naming because they look like exceptions and are not:
- The QR code for setting up two-factor sign-in is generated by this plugin
in PHP and written into the page as SVG. It is not fetched from a chart
service, so the shared secret never leaves your site. - The e-mail telling you that the sign-in address has changed is sent by your
own WordPress installation, through whatever mail setup your site already
uses, to the administration address in Settings General. It goes nowhere
else, and it can be switched off.
WordPress.org plugin directory (the shared Lynbro “Our plugins” screen).
Apart from the above, one request goes to WordPress.org, from every Lynbro plugin
alike: when an administrator who may install plugins opens Lynbro Our plugins,
the screen asks the WordPress.org Plugin Directory API
(https://api.wordpress.org/plugins/info/1.2/) which Lynbro plugins are listed,
through WordPress core’s own plugins_api() — the same call the Plugins Add New
screen makes.
- What is sent: the query (plugins by the author “lynbro”), plus what WordPress
core adds to every request to WordPress.org: your WordPress version, the admin
language and, in the User-Agent, your site address. Nothing about your visitors,
users or content. - When: only on that screen, at most once a day (the answer is cached for a day;
after a failed request, an hour). No other screen and no visitor request triggers it. - Installing a suggested plugin uses WordPress core’s own installer, which downloads
the plugin from downloads.wordpress.org — only when you click “Install now”. - WordPress.org Terms of Service ·
Privacy Policy
Privacy
Everything the plugin records is stored in two tables in your own database and
never leaves your site.
The journal holds, for each event: the time, what happened, the username that
was tried, the visitor’s IP address, the browser identification string, and the
reason in plain language. Storing the IP address can be switched off, at the
cost of no longer being able to see where attempts came from. Entries are
deleted automatically after the number of days you set — 30 by default — and you
can empty the journal yourself at any time.
For accounts using two-factor sign-in, the plugin stores the shared secret and
the hashes of the unused recovery codes against that account. The recovery codes
themselves are shown once and never stored, so nobody can read them back.
Deleting the plugin removes both tables, every setting, and all two-factor data
from every account.
Screenshots
The overview: your sign-in address, the way back in, and what has been stopped.
The journal: every refusal with the reason, and a button to undo it.
Settings: where the sign-in page lives, and what the old address gives back.
Setting up two-factor sign-in, with the QR code drawn on your own server.
