| 1 |
�� n � � � P Q Q ) � |
| 2 |
� |
| 3 |
" � |
| 4 |
� |
| 5 |
I |
| 6 |
|
| 7 |
U |
| 8 |
> e |
| 9 |
F � |
| 10 |
" � |
| 11 |
|
| 12 |
|
| 13 |
/ |
| 14 |
= |
| 15 |
W |
| 16 |
? q |
| 17 |
� |
| 18 |
� |
| 19 |
! � |
| 20 |
� |
| 21 |
h � |
| 22 |
O _ |
| 23 |
� |
| 24 |
� |
| 25 |
� |
| 26 |
) � |
| 27 |
� � � � � � z � # � � ) � 5 G \ l � � | � � } < � � � M % W } _ � � � ? l N |
| 28 |
� � � d � S e |
| 29 |
o } d � � � G |
| 30 |
_ U i � � ; � } |
| 31 |
! � |
| 32 |
� � � � 8 � , " ( O � x 9 C |
| 33 |
Y |
| 34 |
e |
| 35 |
p ~ n � � � � � # � { 2 i � * > C |
| 36 |
� 2 � � � N � k *! �! D �! M �! . H" V w# 7 �$ % % |
| 37 |
%% 9 2% l% 9 �% K �% % & ! .& P& $ c& �& L �& �& �& ' ' � "' � �' H( R( h( ' o( �( � �( <) P) � j) � * l �* " &+ I+ e+ �+ �+ �+ �+ �+ � �+ � �, | ^- $ �- L . M. ' ]. 0 |
| 38 |
. $ �. �. o �. |
| 39 |
a/ n/ F x/ � �/ |
| 40 |
I0 % W0 }0 N �0 �0 �0 |
| 41 |
�0 |
| 42 |
�0 ( 1 12 82 |
| 43 |
K2 [ X2 Q �2 T 3 x [3 < �3 � 4 �4 �4 �4 �4 �4 2 �4 '5 - F5 � t5 3 �5 J 26 |
| 44 |
}7 �7 �7 �7 � �7 =8 N8 |
| 45 |
_9 � m9 : ! : 9: � O: o |
| 46 |
; ! z; 6 �; �; < �; < *< N :< E �< �< D �< o 3= |
| 47 |
- k l c L ^ Y S M m 4 3 X a g H |
| 48 |
R 7 j U 6 ( C P \ |
| 49 |
! ) 1 F |
| 50 |
, ; > f ' * I [ ? A ` 2 8 B e " Q W i 5 O ] D : $ V h J Z N E + @ T % 0 G = . & 9 b d K # < n / _ i.e. XMLRPC requests coming in to WordPress (whether from a legitimate app, or from an attacker) can only be verified using the password - not with a two-factor code. As a result, there not be an ideal option to pick below. You may have to choose between the convenience of using your apps, or the security of two factor authentication. (check your OTP app to get this password) (update) Activate two factor authentication Advanced settings Another way to do that is by using a user-switching plugin like this one. Change to email Choose which algorithm for One Time Passwords you want to use. Choose which user roles will have two factor authentication available. Click here and re-scan the QR-Code Click to enter One Time Password Current codes Current codes (login: %s) Current one-time password David Nutbourne + David Anderson, original plugin by Oskar Hane Default Default algorithm Disable two-factor authentication Disabled Do not require 2FA over XMLRPC (best option if you must use XMLRPC and your client does not support 2FA) Do require 2FA over XMLRPC (best option if you do not use XMLRPC or are unsure) Emergency codes Enable two-factor authentication Enabled Enter One Time Password (if you have one) Error: For OTP apps that support scanning, scanning this code is the quickest way to set the app up (e.g. with Duo Mobile, Google Authenticator) HOTP (event based) Higher PHP version required If you activate two-factor authentication, then verify that your two-factor application is showing the same One Time Password as shown on this page before you log out. If you translate this plugin, please send the translations .po-file to us so we can include it in future releases - paste a link in the plugin's support forum. If you want to say 'thank you' or help this plugin's development, or get extra features, then please take a look at the premium version of this plugin. It comes with these extra features: Lead developer's homepage Make two factor authentication compulsory Manage all users centrally More free plugins More premium plugins More shortcodes Multisite Super Admin N.B. Generating two-factor codes depends upon your web-server and your TFA app/device agreeing upon the time. The current UTC time according to the server when this page loaded: %s, and in the time-zone you have configured in your WordPress settings: %s N.B. These two-factor settings apply to your entire WordPress network. (i.e. They are not localised to one particular site). N.B. This site is configured to forbid you to log in if you disable two-factor authentication after your account is %d days old No emergency codes left. Sorry. Nothing you change here will have any effect on other users. One Time Password One Time Password (i.e. 2FA) One-time emergency codes are a feature of the Premium version of this plugin. PHP OpenSSL or mcrypt module required Personal support Please re-sync or you might not be able to log in if you generate more OTPs without logging in. Plugin settings Premium version Private key (base 32 - used by Google Authenticator and Authy): Private key - always to be kept secret - type this into your app to set it up (instead of scanning the code) Private key: Private key: %s (base 32: %s) QR code Requiring users to use two-factor authentication is a feature of the Premium version of this plugin. Reset private key Response: Save Settings Saving... Secure your WordPress login forms with two factor authentication - including WooCommerce login forms Settings Settings saved. Support TOTP (time based - most common algorithm; used by Google Authenticator) The Premium version of this plugin allows you to see and reset the TFA settings of other users. The Two Factor Authentication plugin requires PHP version %s or higher - your current version is only %s. The Two Factor Authentication plugin requires either the PHP openssl (preferred) or mcrypt module to be installed. Please ask your web hosting company to install one of them. The one-time password (TFA code) you entered was incorrect. The site owner has forbidden you to login without two-factor authentication. Please contact the site owner to re-gain access. These are your personal settings. Translations Twitter Two Factor Auth Two Factor Authentication Two Factor Authentication (Version: %s) - Admin Settings Two Factor Authentication currently disabled Two Factor Authentication re-sync needed Two factor authentication is currently disabled via the TWO_FACTOR_DISABLE constant (which is mostly likely to be defined in your wp-config.php) Two factor authentication is not available for your user. Unfortunately, XMLRPC also provides a way for attackers to perform actions on your WordPress site, using only a password (i.e. without a two-factor password). More unfortunately, authors of legitimate programmes using XMLRPC have not yet added two-factor support to their code. Updating... User roles User settings Users' settings Warning: if you reset this key you will have to update your apps with the new one. Are you sure you want this? WordPress backups XMLRPC is a feature within WordPress allowing other computers to talk to your WordPress install. For example, it could be used by an app on your tablet that allows you to blog directly from the app (instead of needing the WordPress dashboard). XMLRPC requests You are attempting to log in to an account that has two-factor authentication enabled; this requires you to also have two-factor authentication enabled on the account whose credentials you are using. You are currently using You have to enter a username first. You have unsaved settings. You need to resync your device for Two Factor Authentication since the OTP you last used is many steps ahead of the server. You should also bookmark the FAQs, which explain how to de-activate the plugin even if you cannot log in. Your counter on the server is currently on Your users can change this in their own settings if they want. a time based access to our personal support desk for 12 months. algorithm an event based enable, disable or see TFA codes for all your users from one central location. flexible shortcodes allowing you to design your front-end settings page for your users exactly as you wish. https://www.simbahosting.co.uk https://www.simbahosting.co.uk/s3/product/two-factor-authentication/ provide your users with one-time codes to use in case they lose their device. PO-Revision-Date: 2017-10-11 16:50:47+0000 |
| 51 |
MIME-Version: 1.0 |
| 52 |
Content-Type: text/plain; charset=UTF-8 |
| 53 |
Content-Transfer-Encoding: 8bit |
| 54 |
Plural-Forms: nplurals=1; plural=0; |
| 55 |
X-Generator: GlotPress/2.4.0-alpha |
| 56 |
Language: zh_TW |
| 57 |
Project-Id-Version: Plugins - Two Factor Authentication - Stable (latest release) |
| 58 |
舉例來說，無論是合法程式或是攻擊� |
| 59 |
，只要他們透過 XMLRPC 請求進� |
| 60 |
� WordPress 網站，� |
| 61 |
需正確的密碼即可通行，無須使用第二步驟驗證碼。正因為如此，下面沒有既便利又安� |
| 62 |
�的選� |
| 63 |
，你� |
| 64 |
須從使用 App 的便利性以及使用� |
| 65 |
�步驟驗證的安� |
| 66 |
�性� |
| 67 |
�� |
| 68 |
間擇一選用。 (開啟你的驗證碼產生器 App 以取得驗證碼) (更新) 啟用� |
| 69 |
�步驟驗證 進階設定 另一個方式是透過這個切換使用� |
| 70 |
的外掛。 變更至電子郵件 選擇你想使用的演算法以產生一次性密碼。 以下使用� |
| 71 |
角色，核取後即� |
| 72 |
�備啟用� |
| 73 |
�步驟驗證的資格。 按一下這裡並重新掃描 QR 碼 按一下以輸� |
| 74 |
�一次性密碼 目前的驗證碼 目前的驗證碼 (使用� |
| 75 |
為 %s) 目前的一次性密碼 原開發� |
| 76 |
為 Oskar Hane，目前為 David Nutbourne 以及 David Anderson 預設 預設演算法 停用� |
| 77 |
�步驟驗證 停用 透過 XMLRPC 連線時無須進行� |
| 78 |
�步驟驗證 (如果你的用戶端應用程式不支援� |
| 79 |
�步驟驗證時，此為最佳設定) 透過 XMLRPC 連線時強制使用� |
| 80 |
�步驟驗證 (當你未使用 XMLRPC 相關用戶端程式或不確定自己有沒有使用 XMLRPC，此為最佳設定) 復原碼 啟用� |
| 81 |
�步驟驗證 啟用 輸� |
| 82 |
�一次性密碼 (如果有的話) 錯誤: 使用支援 OTP 協定並� |
| 83 |
�備掃描條碼功能 App 去掃描下方的條碼，是設定 App 最快的方式 (例如 Duo Mobile 或 Google Authenticator) HOTP (根據事件) 需要更新版本的 PHP 啟用� |
| 84 |
�步驟驗證後，請在登出前確認你的� |
| 85 |
�步驟驗證碼產生器 App 產生的驗證碼，是否與本頁面顯示的一次性密碼相符。 如果你為此外掛進行本地化，請將完成本地化的 PO 檔寄給我們，我們便能在將來釋出該語言的新版本，並將連結放在外掛支援論壇。 如果你想致謝、協助外掛的開發，或是想要更多的功能，請考� |
| 86 |
�使用付費版外掛。 以下是付費版的進階功能: 首席程式設計師網站 強制啟用� |
| 87 |
�步驟驗證 集中管理所有使用� |
| 88 |
更多� |
| 89 |
�費外掛 更多付費外掛 更多短代碼 多站點� |
| 90 |
級管理員 請注意，產生第二步驟驗證碼取決於網站伺服器與你的� |
| 91 |
�步驟驗證 App/裝置的約定時間。這個頁面載� |
| 92 |
�時，伺服器目前的 UTC 時間為 %s，而你為 WordPress 網站所設定的時區時間為 %s。 請注意，此處的� |
| 93 |
�步驟驗證設定會套用至整個 WordPress 網路，即使他們並未集中至同一個特定網站。 請注意，這個網站設定為符合「帳號已啟用 %d 天、卻停用� |
| 94 |
�步驟驗證」這個條件就禁止登� |
| 95 |
�。 抱歉！已無可用的復原碼。 你在此處進行的設定變更，並<b>不會影響� |
| 96 |
�他使用� |
| 97 |
</b>。 一次性密碼 一次性密碼 (意即� |
| 98 |
�步驟驗證) 一次性復原碼為付費版外掛的功能。 需要 PHP OpenSSL 或 mcrypt 模組 個人化技術支援 如果未進行登� |
| 99 |
�卻不斷生成一次性密碼，請馬上進行重新同步，否則將會無法登� |
| 100 |
�。 外掛設定 付費版 私密金鑰 (Base 32 格式 - 用於 Google Authenticator 及 Authy): 請不要洩漏下方的私密金鑰。在你的 App 中輸� |
| 101 |
�下方的私密金鑰，是取代掃描上方條碼的另一種設定方式 私密金鑰: 私密金鑰: %s (Base 32 格式: %s) QR 碼 「強制要求使用� |
| 102 |
啟用� |
| 103 |
�步驟驗證」是付費版外掛的功能。 重設私密金鑰 回應: 儲存設定 儲存中... 使用� |
| 104 |
�步驟驗證保護你的 WordPress 登� |
| 105 |
�表單 - � |
| 106 |
含 WooCommerce 登� |
| 107 |
�表單。繁體中文本地化由「<a href="https://www.alexclassroom.com" target="_blank">阿力� |
| 108 |
的教室</a>」站長<a href="https://www.facebook.com/captain.alexlion" target="blank">阿力� |
| 109 |
</a>提供。 設定 設定已儲存。 技術支援 TOTP (根據時間 - 最通用的演算法，Google Authenticator 也採用這個演算法) 付費版外掛� |
| 110 |
�許你檢視及重設� |
| 111 |
�他使用� |
| 112 |
的� |
| 113 |
�步驟驗證設定。 � |
| 114 |
�步驟驗證外掛需要 %s 版 PHP 或更新版本 - 你目前的版本為 %s。 � |
| 115 |
�步驟驗證外掛需要 PHP OpenSSL (首選) 或 mcrypt 模組，請要求你的主機託管服務商擇一安裝。 你輸� |
| 116 |
�了錯誤的一次性密碼 (� |
| 117 |
�步驟驗證碼)。 由於你未使用� |
| 118 |
�步驟驗證，所以網站管理員已禁止你的登� |
| 119 |
�，請聯絡網站管理員以重新取得登� |
| 120 |
�權限。 以下是你的個人設定。 本地化 Twitter � |
| 121 |
�步驟驗證 Two Factor Authentication Two Factor Authentication %s 版 - 管理員設定 目前已停用� |
| 122 |
�步驟驗證 � |
| 123 |
�步驟驗證碼產生器� |
| 124 |
須重新同步 目前因設定了常數 TWO_FACTOR_DISABLE 導致� |
| 125 |
�步驟驗證停用，這� |
| 126 |
設定通常會定義在你的 wp-config.php 檔案中。 你的使用� |
| 127 |
帳號無法使用� |
| 128 |
�步驟驗證。 糟糕的是，XMLRPC 也提供了攻擊� |
| 129 |
在你的 WordPress 網站上執行變更操作的能力，在<b>未啟用� |
| 130 |
�步驟驗證</b>的狀況下，� |
| 131 |
需知道密碼即可實作此類攻擊。更糟糕的是，開發� |
| 132 |
�建 XMLRPC 功能的合法程式的開發� |
| 133 |
們，並未對在他們的程式加� |
| 134 |
�� |
| 135 |
�步驟驗證支援。 更新中... 使用� |
| 136 |
角色 使用� |
| 137 |
設定 使用� |
| 138 |
設定 提示: 如果重新設定設金鑰，就� |
| 139 |
須在你的驗證碼產生器 App 中輸� |
| 140 |
�新的金鑰。你確定要這麼做嗎？ WordPress 備份 XMLRPC 為 WordPress 的� |
| 141 |
�建功能，該功能� |
| 142 |
�許� |
| 143 |
�他裝置與你的 WordPress 進行互動。舉例來說，如果你的平板上有個� |
| 144 |
�備 XMLRPC 功能的 App，你可以透過該 App 直接在你的 WordPress 上發文，而無須進� |
| 145 |
� WordPress 控制台。 XMLRPC 請求 目前你要進行登� |
| 146 |
�的帳號已啟用� |
| 147 |
�步驟驗證，這表示你� |
| 148 |
須為這個已啟用� |
| 149 |
�步驟驗證帳號輸� |
| 150 |
�驗證碼才能登� |
| 151 |
�。 你目前使用的是 你� |
| 152 |
須� |
| 153 |
�輸� |
| 154 |
�使用� |
| 155 |
名稱 你已回復設定。 自你最後一次使用一次性密碼後，你裝置上的計數器已經落後伺服器許多；為了取得正確的� |
| 156 |
�步驟驗證碼，你� |
| 157 |
須為你的裝置進行重新同步。 也請將「常見問題集」儲存在書籤裡，當中會解釋如何在無法登� |
| 158 |
�時停用這個外掛。 目前伺服器上的計數器為 使用� |
| 159 |
可根據他們的需求變更此� |
| 160 |
設定。 基於時間的 12 個月� |
| 161 |
�隨時存取我們的個人化技術支援平台 演算法 基於事件的 提供集中啟用、停用以及檢視所有使用� |
| 162 |
� |
| 163 |
�步驟驗證的功能 靈活的短代碼讓你設計出更符合所需的前端設定頁面 https://www.simbahosting.co.uk https://www.simbahosting.co.uk/s3/product/two-factor-authentication/ 當使用� |
| 164 |
遺失產生驗證碼的裝置時，提供給他這種一次性密碼進行登� |
| 165 |
�並變更設定。 |
