Title: Secure XML-RPC Author: Eric Mann Published: 1 Ocak 2014 Last modified: 30 Ağustos 2014 --- Eklentilerde ara ![](https://ps.w.org/secure-xml-rpc/assets/banner-772x250.png?rev=975920) Bu eklenti, **WordPress’in son 3 ana dağıtımı ile test edilmemiş**. Artık bakımı yapılmıyor veya desteklenmiyor olabilir ve WordPress’in daha güncel sürümleriyle birlikte kullanıldığında uyumluluk sorunları olabilir. ![](https://ps.w.org/secure-xml-rpc/assets/icon-256x256.png?rev=975920) # Secure XML-RPC [Eric Mann](https://profiles.wordpress.org/ericmann/) tarafından [İndir](https://downloads.wordpress.org/plugin/secure-xml-rpc.1.0.0.zip) * [Detaylar](https://tr.wordpress.org/plugins/secure-xml-rpc/#description) * [İncelemeler](https://tr.wordpress.org/plugins/secure-xml-rpc/#reviews) * [Kurulum](https://tr.wordpress.org/plugins/secure-xml-rpc/#installation) * [Geliştirme](https://tr.wordpress.org/plugins/secure-xml-rpc/#developers) [Destek](https://wordpress.org/support/plugin/secure-xml-rpc/) ## Açıklama 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 ## Ekran Görüntüleri [⌊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. ## Yükleme #### 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. ## SSS 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. ## İncelemeler ![](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/) 3 Eylül 2016 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/) 7 Şubat 2017 [ 3 incelemeyi oku ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/) ## Katkıda Bulunanlar ve Geliştiriciler “Secure XML-RPC” açık kaynaklı yazılımdır. Aşağıdaki kişiler bu eklentiye katkıda bulunmuşlardır. Katkıda bulunanlar * [ Eric Mann ](https://profiles.wordpress.org/ericmann/) [“Secure XML-RPC” eklentisini dilinize çevirin.](https://translate.wordpress.org/projects/wp-plugins/secure-xml-rpc) ### Geliştirmeyle ilgilenir misiniz? [Kodu görüntüleyin](https://plugins.trac.wordpress.org/browser/secure-xml-rpc/), [SVN deposuna](https://plugins.svn.wordpress.org/secure-xml-rpc/) göz atın ya da [RSS](https://plugins.trac.wordpress.org/log/secure-xml-rpc/?limit=100&mode=stop_on_copy&format=rss) ile [geliştirme günlüğüne](https://plugins.trac.wordpress.org/log/secure-xml-rpc/) abone olun. ## Değişiklik Kaydı #### 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 ## Meta * Sürüm **1.0.0** * Son güncelleme **12 yıl önce** * Etkin kurulumlar **50+** * WordPress sürümü ** 3.8 veya üstü ** * Test edilen sürüm **4.0.38** * Dil * [English (US)](https://wordpress.org/plugins/secure-xml-rpc/) * Etiketler * [authentication](https://tr.wordpress.org/plugins/tags/authentication/)[oauth](https://tr.wordpress.org/plugins/tags/oauth/) [security](https://tr.wordpress.org/plugins/tags/security/)[xmlrpc](https://tr.wordpress.org/plugins/tags/xmlrpc/) * [Gelişmiş görünüm](https://tr.wordpress.org/plugins/secure-xml-rpc/advanced/) ## Puanlar 5 üzerinden 3.7 yıldız. * [ 2 5 yıldızlı inceleme ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=5) * [ 0 4 yıldızlı inceleme ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=4) * [ 0 3 yıldızlı inceleme ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=3) * [ 0 2 yıldızlı inceleme ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=2) * [ 1 1 yıldızlı inceleme ](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/#new-post) [Tüm değerlendirmeleri görün](https://wordpress.org/support/plugin/secure-xml-rpc/reviews/) ## Katkıda bulunanlar * [ Eric Mann ](https://profiles.wordpress.org/ericmann/) ## Destek Söyleyeceğiniz bir şey mi var? Yardım mı lazım? [Destek forumunu görüntüle](https://wordpress.org/support/plugin/secure-xml-rpc/) ## Bağış yap Bu eklentinin geliştirilmesini desteklemek ister misiniz? [ Bu eklentiye bağış yap ](http://wordpress.org/plugins/secure-xmlrpc)