Title: Secure XML-RPC Author: Eric Mann Published: 2014年1月1日 Last modified: 2014年8月30日 --- プラグインを検索 ![](https://ps.w.org/secure-xml-rpc/assets/banner-772x250.png?rev=975920) このプラグインは **WordPress の最新3回のメジャーリリースに対してテストされていま せん**。もうメンテナンスやサポートがされていないかもしれず、最新バージョンの WordPress で使用した場合は互換性の問題が発生する可能性があります。 ![](https://ps.w.org/secure-xml-rpc/assets/icon-256x256.png?rev=975920) # Secure XML-RPC 作者: [Eric Mann](https://profiles.wordpress.org/ericmann/) [ダウンロード](https://downloads.wordpress.org/plugin/secure-xml-rpc.1.0.0.zip) * [詳細](https://ja.wordpress.org/plugins/secure-xml-rpc/#description) * [レビュー](https://ja.wordpress.org/plugins/secure-xml-rpc/#reviews) * [インストール](https://ja.wordpress.org/plugins/secure-xml-rpc/#installation) * [開発](https://ja.wordpress.org/plugins/secure-xml-rpc/#developers) [サポート](https://wordpress.org/support/plugin/secure-xml-rpc/) ## 説明 Rather than sending usernames and passwords in plain text with every request, we’re going to use a set of public/secret keys to hash data and authenticate instead. On your WordPress profile, you will see a new “Remote Publishing Permissions” section listing out the applications that have permission to publish, along with their public and secret keys. New applications can be added whenever you want. You can also change the names of applications, or revoke publishing permission by deleting them. ### Additional Information Lock graphic designed by Scott Lewis from the thenounproject.com ## スクリーンショット [⌊The new Remote Publishing Permissions area of the user profile.⌉⌊The new Remote Publishing Permissions area of the user profile.⌉[ The new Remote Publishing Permissions area of the user profile. ## インストール #### Manual Installation 1. Upload the entire `/secure-xml-rpc` directory to the `/wp-content/plugins/` directory. 2. Activate Secure XML-RPC through the ‘Plugins’ menu in WordPress. ## FAQ How do I use the new authorization? The old username/password paradigm can still be used, but will result in a `X-Deprecated` header being returned by the server. From now on, you will send an `Authorization` header. This header will be the publishing application’s public key, two pipe (`|`) characters, and a hash of the application’s secret key concatenated with the body of the request. How do I generate the message hash? Say your application has the following information: * Public Key: b730db0864b0d4453ba6a26ad6613cd4* Secret Key: 7647a19f5bf3e9fd001419900ad48a54 And you want to make the following request (whitespace/indentation added for readability, but is removed when calculating hashes): ``` wp.getPosts 1 ``` Note that the second and third parameters (traditionally `username` and `password`) are empty. Usernames and passwords can still be specified, but will result in the server returning an `X-Deprecated` header. Your Authorization header would thus become: ``` b730db0864b0d4453ba6a26ad6613cd4||3fac15f99f7a178f922bcc4942e62dc9001b2a45118fc3a6f3aebd77d25f4d58 ``` The second part of the header is generated in PHP by calculating: ``` hash( 'sha256', '7647a19f5bf3e9fd001419900ad48a54' . hash( 'sha256', '7647a19f5bf3e9fd001419900ad48a54' . {request_body} ) ) ``` WordPress will read the header and log you in as usual, but you never need to send your password across the wire. In this paradigm, application secret keys should _also_ be treated as passwords – they are sensitive information! Why are we using the secret key twice? Some developers raised concerns about [length extension attacks](https://blog.whitehatsec.com/hash-length-extension-attacks/) in previous editions of the plugin. While length extension isn’t strictly necessary when dealing with XML-based messaging, a double hash helps end the discussion around potentially-related vulnerabilities. The double-hash is similar to but simpler than HMAC and is fairly easy to implement in any programming language. Just note, PHP’s `hash()` function returns a base64- encoded string, not a raw hash of the data passed in. Do I have to copy/paste my application keys into remote systems? Not necessarily. The latest version of the plugin adds a new XML-RPC method to the system that allows for the generation of user-specific application keys remotely. _Please only ever call this method over a secure/trusted network connection_ when setting up an application for the first time. ## 評価 ![](https://secure.gravatar.com/avatar/06288c97f5f235cc2685c817994161456093c02621eaa5ce0856b8ee3fab3299? s=60&d=retro&r=g) ### 󠀁[Secure fail ?](https://wordpress.org/support/topic/secure-fail/)󠁿 [Anonymous User 13245058](https://profiles.wordpress.org/anonymized-13245058/) 2016年9月3日 This plugin has been hacked on a client website… ![](https://secure.gravatar.com/avatar/c0c5b4ff7ab8a4de9e2651d48d0fd7d2ebd77c5ba1bc9bf67f58b2d9ea0c2341? s=60&d=retro&r=g) ### 󠀁[Very useful plugin](https://wordpress.org/support/topic/very-useful-plugin-440/)󠁿 [benjib0t](https://profiles.wordpress.org/benjib0t/) 2017年2月7日 [ 3件のレビューをすべて表示 ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/) ## 貢献者と開発者 Secure XML-RPC はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献 しています。 貢献者 * [ Eric Mann ](https://profiles.wordpress.org/ericmann/) [“Secure XML-RPC” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/secure-xml-rpc) ### 開発に興味がありますか ? [コードを閲覧](https://plugins.trac.wordpress.org/browser/secure-xml-rpc/)するか、 [SVN リポジトリ](https://plugins.svn.wordpress.org/secure-xml-rpc/)をチェックする か、[開発ログ](https://plugins.trac.wordpress.org/log/secure-xml-rpc/)を [RSS](https://plugins.trac.wordpress.org/log/secure-xml-rpc/?limit=100&mode=stop_on_copy&format=rss) で購読してみてください。 ## 変更履歴 #### 1.0.0 * New: Add a custom RPC method for generating application keys remotely. * Dev change: Move all functional implementations inside our pseudo-namespace. * Dev change: Use a constant-time string comparison method for better security and less data leakage during authentication. * Dev change: Use a double-hash to prevent any potential length-extension attacks. #### 0.1.0 * First release ## メタ * バージョン **1.0.0** * 最終更新日 **12年前** * 有効インストール数 **50+** * WordPress バージョン ** 3.8またはそれ以降 ** * 検証済み最新バージョン: **4.0.38** * 言語 * [English (US)](https://wordpress.org/plugins/secure-xml-rpc/) * タグ * [authentication](https://ja.wordpress.org/plugins/tags/authentication/)[oauth](https://ja.wordpress.org/plugins/tags/oauth/) [security](https://ja.wordpress.org/plugins/tags/security/)[xmlrpc](https://ja.wordpress.org/plugins/tags/xmlrpc/) * [詳細を表示](https://ja.wordpress.org/plugins/secure-xml-rpc/advanced/) ## 評価 5つ星中3.7つ星 * [ 2 5-星レビュー ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=5) * [ 0 4-星レビュー ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=4) * [ 0 3-星レビュー ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=3) * [ 0 2-星レビュー ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=2) * [ 1 1-星レビュー ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/#new-post) [すべてのレビューを見る](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/) ## 貢献者 * [ Eric Mann ](https://profiles.wordpress.org/ericmann/) ## サポート 意見や質問がありますか ? [サポートフォーラムを表示](https://wordpress.org/support/plugin/secure-xml-rpc/) ## 寄付 このプラグインが今後も改善できるよう応援しませんか ? [ このプラグインに寄付 ](http://wordpress.org/plugins/secure-xmlrpc)