| 开发者 | etbsjp |
|---|---|
| 更新时间 | 2026年11月8日 16:16 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.3 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
?author= redirect and the messages of the login screen. Once a login name is known, only the password is left to guess.
ETBS Account Guard closes these places. Each one can be turned on or off from Settings > ETBS Account Guard.
What it covers
/wp/v2/users and everything below it) are removed for visitors who are not logged in, including the author data embedded with _embed. An existing user ID and a missing one give the same response. Logged-in users, including the block editor, are not affected.wp-sitemap-users-1.xml) is removed.comment-author-{name} on comments by registered users and author-{name} on author pages are removed. Class names that contain the user ID are kept./?author=1 goes to the home page instead of the author page. The admin screens are not affected./author/{name}/) return 404 for visitors who are not logged in. Before turning this on, open a post on your site and click the author name. If a page whose address contains /author/ opens, your theme links to author pages, and those links will lead to "Page not found". Logged-in users still see author pages, so check the result in a private window of your browser.# is a note. Only the address the server itself sees for the connection (REMOTE_ADDR) is used; headers such as X-Forwarded-For are never read, since a visitor can set those themselves..htaccess snippet is shown for servers that need it, for you to review and add yourself — this plugin never edits .htaccess automatically.wp_signon(), including WooCommerce My Account. No login cookie is issued before the code. Sign-ins that cannot show the code screen (XML-RPC with the ordinary password, AJAX sign-ins and similar; except from a trusted device, never for XML-RPC) get the same message as a wrong password, and the user is emailed (not for XML-RPC).define( 'ACGD_DISABLE_RESTRICTION', true ); to wp-config.php. This stops Access Restriction only; Login Name Protection keeps working.
If nobody can sign in because verification codes do not arrive, add define( 'ACGD_DISABLE_TWO_STEP', true ); to wp-config.php. This stops Two-Step Verification only; Access Restriction and Login Name Protection keep working. Define it also on a copy of your site whose email sending is turned off. When the switch is taken off again, users who need a code and signed in while it was on are signed out once on their next request. The two switches are independent. While a switch is on, a warning is shown on the admin screens.
What it does not do
Authenticator apps (TOTP), login attempt limits, CAPTCHA and firewalls are not included. Two-Step Verification is limited to a code sent by email. Use a dedicated security plugin for the others. The ?author= redirect and the login messages overlap with some of those plugins; having both does no harm.
Known limitations
etbs-account-guard folder to the /wp-content/plugins/ directory.No. The REST API user endpoints stay available to logged-in users, which is what the author panel of the block editor uses.
No. Each item returns to the behavior of WordPress itself when it is turned off.
Deleting the plugin removes the denial log of Access Restriction, the saved result of the BASIC authentication receive diagnosis (rebuilt the next time it is run), the sign-in attempts, send records, confirmations and trusted devices of Two-Step Verification, a few internal records and cached counts, and, if present, the update check data left behind by an earlier version distributed outside WordPress.org. All settings, including the per-role and per-user Access Restriction modes, IP lists, BASIC authentication IDs and password hashes, and the per-role and per-user Two-Step Verification settings (including the number of days a device is trusted), are kept so that they come back if you install the plugin again.
No. It is off for every role and user until you turn it on. Existing settings are not changed.
Wait a few minutes, check the spam folder, and send a new code from the code screen. If codes never arrive, check the email sending of your site. As a last resort, add define( 'ACGD_DISABLE_TWO_STEP', true ); to wp-config.php to stop Two-Step Verification until the problem is fixed.
No. Only users who can manage options can change it, on the settings tab or on the user edit screen.
On the code screen, a user can check "Skip the verification code on this device for 30 days" (unchecked by default; do not check it on a shared computer). The number of days is set on the tab: 7, 30 (the default) or off. Only the code is skipped: the password is needed every time, and IP restriction and BASIC authentication still apply. The browser keeps a random value in an HttpOnly cookie, and the site stores only its hash (up to 20 devices per user; the oldest go first). A change of the number of days applies at once to devices already trusted, and saving "Do not trust devices" revokes every trusted device of every user. Changing the password (by a reset, on the profile screen or by any other means) revokes every trusted device of that user, and so does the "Revoke all trusted devices on save" checkbox on the user edit screen — use either if a device is lost. When another user trusts the same browser, the earlier user needs a code again there. Trusted devices do not apply to XML-RPC.
First click "Send a confirmation code" at the top of the tab (or in the Two-Step Verification section of your own Profile screen) and enter the code you receive. A save that would turn two-step verification on for your own account is refused until you have done this within the last 10 minutes, so you cannot lock yourself out with an address that does not receive email. Turning it on for someone else requires that their account has a valid email address.
A session of a user who needs a code is kept only if it went through the code (or was created inside such a session). Sessions from before the feature was turned on, and sessions created by other plugins' sign-in methods, are signed out on their next request. The acgd_two_step_session_exempt filter can keep them.
Two-Step Verification is not available on multisite: the login cookie can be shared across the network, so a site without it would let people in. The other features work as before.
When the server (or another plugin) asks for its own BASIC sign-in on the same address, only one username and password can be sent with each request, so the two cannot be used together. Where the server tells WordPress that its own sign-in was passed (Apache with PHP-FPM and LiteSpeed did in our tests; mod_php was not tested), the confirmation screen shows an explanation instead of asking again. Where it does not (nginx in its default setup, or a sign-in at a CDN or proxy), the prompt keeps coming back, and the page shown after cancelling it says that the two may be overlapping. Either way, remove that sign-in or narrow it so that it does not cover the login and admin screens, then run the receive diagnosis again, or use IP restriction instead.