Eric Mann

<p>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.</p>
<p>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.</p>
<p>New applications can be added whenever you want.  You can also change the names of applications, or revoke publishing permission by deleting them.</p>
<h3>Additional Information</h3>
<p>Lock graphic designed by Scott Lewis from the thenounproject.com</p>


Secure XML-RPC

More secure wrapper for the WordPress XML-RPC interface.

brainvireinfo

<p>You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.</p>
<h4>Features</h4>
<p>Block XML-RPC by following way.</p>
<ul>
<li>Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.</li>
<li>Disable/Block XML-RPC for all users.</li>
</ul>


Manage XML-RPC

Enable/Disable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.

Secure XML-RPC vs Manage XML-RPC