跳至主要內容
WordPress.org

Taiwan 正體中文

  • 佈景主題目錄
  • 外掛目錄
  • 最新消息
  • 技術支援
  • 關於我們
  • 團隊
  • 取得 WordPress
取得 WordPress
WordPress.org

Plugin Directory

Lock and Key

  • 提交外掛
  • 我的最愛
  • 登入
  • 提交外掛
  • 我的最愛
  • 登入

Lock and Key

由 shadowsplitter 開發
下載
  • 詳細資料
  • 使用者評論
  • 安裝方式
  • 開發資訊
技術支援

外掛說明

Lock and Key adds a Security Key button to your WordPress login page. Users register a hardware security key on their profile, then sign in by entering their username, clicking Security Key and confirming on the key. There’s no password to steal, and phishing sites can’t reuse the login.

Works with Ledger Nano S, S Plus, X and Stax (FIDO U2F / Security Key app), YubiKey, Google Titan, and any FIDO2/WebAuthn hardware key.

Features

  • Security Key login button on the WordPress login page
  • Choose which roles can use security keys: administrators, editors, authors, contributors, subscribers and custom roles
  • Security key only mode for each role: turns off password login for users who have registered a key
  • Clear “Use security key only for access” message when someone tries a password on a key-only account, whether the password was right or wrong
  • Users register and manage their own keys, including backup keys
  • Dashboard warning listing administrators who haven’t registered a key yet
  • Admins can remove a user’s lost key from their profile
  • Overview of who has registered keys and when they last used them
  • Full server-side verification of every login: signature (ES256 / RS256), origin, challenge and relying party
  • Cloned-key detection via the signature counter
  • Throttling of repeated failed key logins
  • Logins go through WordPress’s own login process, so other security plugins keep working
  • Works behind Cloudflare, load balancers and other proxies, with protection against faked addresses

Security key only mode

For roles set to Security key only, password login is refused on the login page and XML-RPC once the user has registered a key. Users who haven’t registered a key yet can still use their password, so nobody is locked out before setting one up.

If a user loses their key, an admin removes it from the user’s profile and their password works again. If you’re locked out, adding define( 'LOCKANDKEY_DISABLE_KEY_ONLY', true ); to wp-config.php allows passwords again.

Lock and Key Pro

Lock and Key Pro is a separate plugin that adds monitoring: a login activity log (logins, failed logins and security key changes, with IP address and browser), IP address blocking, XML-RPC attack blocking, manual and automatic IP blocking, 3-strike blocking for admin accounts, custom messages or pages for blocked visitors, email alerts for administrators and for each user about their own account, and WooCommerce support.

Privacy

Lock and Key doesn’t contact any external service. Registered keys (a public key, a key ID, the name the user gave it, and when it was created and last used) are stored in your own WordPress database.

螢幕擷圖

Choosing which roles can use security keys, and which use security keys only.
Choosing which roles can use security keys, and which use security keys only.

安裝方式

  1. Install the plugin from Plugins → Add New, or upload the ZIP under Plugins → Add New → Upload Plugin.
  2. Activate it.
  3. Go to Settings → Lock and Key and choose which roles can use security keys. Administrators are always enabled.
  4. Each user registers a key under Users → Profile → Security Keys.
  5. Optionally, tick Security key only for roles that should stop using passwords.

Your site must use HTTPS. Browsers only allow security keys on secure sites.

常見問題集

Which security keys work?

Any FIDO2 or U2F hardware key: Ledger (open the FIDO U2F / Security Key app), YubiKey, Google Titan, Feitian, SoloKeys and others.

Which users can use security keys?

Any role you enable on Settings → Lock and Key. Administrators are always enabled.

Can I stop users from logging in with a password?

Yes. On Settings → Lock and Key, tick Security key only for a role. Once a user in that role has registered a key, password attempts show “Use security key only for access” and are refused.

What if someone loses their key?

An admin opens the user’s profile and removes the lost key under Security Keys. If that was their last key, their password works again and they can register a new one. Encourage everyone to register a backup key.

I’m locked out. What now?

Add define( 'LOCKANDKEY_DISABLE_KEY_ONLY', true ); to wp-config.php. Passwords then work again. Remove the line once you’ve sorted out your keys.

What happens to the keys if I delete the plugin?

They’re kept, along with your settings, so nothing is lost when you reinstall. To remove everything when deleting the plugin, tick Delete all registered security keys and settings when the plugin is deleted in the plugin’s settings first.

My site is behind Cloudflare or another proxy. Does that matter?

Yes. Choose your proxy under Settings → Lock and Key → Visitor IP Addresses. Otherwise every visitor appears to come from the proxy’s address, so the failed-login limit would apply to everyone at once. The proxy’s header is only believed when the request really comes from the proxy (Cloudflare’s address ranges are built in), so visitors can’t fake their address.

Does it affect application passwords?

No. Application passwords (used by apps and the REST API) are managed separately under each user’s profile.

使用者評論

這個外掛目前沒有任何使用者評論。

參與者及開發者

以下人員參與了開源軟體〈Lock and Key〉的開發相關工作。

參與者
  • shadowsplitter

將〈Lock and Key〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄。

變更記錄

3.2.2

  • Security key login and registration now work with caching plugins such as W3 Total Cache, and with object caches (Redis, Memcached). The one-time code is signed and checked directly instead of being read back from the database.
  • Log in with your email address even when it contains “+”.

3.2.1

  • Security keys now work at both the www and non-www address of a site (for example example.com and www.example.com). Keys registered before this version keep working at the address they were registered on; register them again to use both.
  • One-time security key codes are stored in the database, so registration and login work on sites with an object cache (Redis, Memcached).

3.2.0

  • First release on WordPress.org.

中繼資料

  • 版本 3.2.2
  • 最後更新 3 週前
  • 啟用安裝數 少於 10 次
  • WordPress 版本需求 6.2 或更新版本
  • 已測試相容的 WordPress 版本 7.1.4
  • PHP 版本需求 7.4 或更新版本
  • 語言
    English (US)
  • 標籤:
    loginsecuritytwo factorwebauthn
  • 進階檢視

評分

這個項目尚無任何評論記錄。

撰寫評分

查看全部使用者評論

參與者

  • shadowsplitter

技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

檢視技術支援論壇

  • 關於我們
  • 最新消息
  • 主機代管
  • 隱私權
  • 展示網站
  • 佈景主題目錄
  • 外掛目錄
  • 區塊版面配置目錄
  • Learn
  • 技術支援
  • 開發者資源
  • WordPress.tv ↗
  • 共同參與
  • 活動
  • 贊助基金會 ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org

Taiwan 正體中文

The WordPress® trademark is the intellectual property of the WordPress Foundation.

  • 查看我們的 X (之前的 Twitter) 帳號
  • 造訪我們的 Bluesky 帳號
  • 造訪我們的 Mastodon 帳號
  • 造訪我們的 Threads 帳號
  • 造訪我們的 Facebook 粉絲專頁
  • Visit our Instagram account
  • Visit our LinkedIn account
  • 造訪我們的 TikTok 帳號
  • Visit our YouTube channel
  • 造訪我們的 Tumblr 帳號
程式碼,如詩