alvego

Simple and easy WordPress plugin for protecting your login form.
Plugin implements setting the security key for the login form.
Thereby significantly reducing the likelihood of automatic brute force.
The security key is transmitted manually as GET parameter for login form.
For example: http://example.com/wp-login.php?sk=my_secure_key
Warning: Be careful if <code>sk</code> parameter is not specified, the login will not be possible, even if specifying the correct username and password.
<h3>Arbitrary section 1</h3>

Protected wp-login

This plugin protects your admin's login page (secure key in url).

Adam Franco

This plugin allows users to subscribe to feeds requiring authentication. When using <a href="https://wordpress.org/extend/plugins/more-privacy-options/" rel="ugc">More Privacy Options</a> in a multi-site installation RSS feeds for blogs marked as private require authentication. This plugin adds a user and site specific 40-character key on private blogs, creating a unique feed URL for each registered on user the blog. This allows feeds on private blogs to be subscribed to using feed readers that do not support authentication. As well, this allows subscription on sites where local HTTP authentication of feeds is not possible, such as those that use CAS or OpenId to authenticate users.
This plugin is similar in concept to the <a href="http://code.andrewhamilton.net/wordpress/plugins/feed-key/" rel="nofollow ugc">Feed Key</a> plugin, but designed from the ground up to operate in a multi-site context where access is controlled by the <a href="https://wordpress.org/extend/plugins/more-privacy-options/" rel="ugc">More Privacy Options</a> plugin.
Primary differences from Feed Key:
<ul>
<li>Only adds keys to the feed URLs on private sites, not all sites in the network.</li>
<li>Keys are per site and per user, preventing exposure of the key for a single site from giving access to other sites the user can see.</li>
<li>Presence of a feed key authenticates feed requests as the user that matches the key rather than blocking requests that don’t include a feed key.</li>
<li>If no key is present the RSS feed request continues without interference for handling by other authentication hooks.</li>
<li>Access control is still determined by other authentication plugins, ensuring that if a user is removed as a subscriber of a private blog, access to the feed will be denied.</li>
<li>Users can revoke their own keys on a per-blog basis.</li>
</ul>
Contributors and developers, please submit issues and pull-requests via <a href="https://github.com/adamfranco/private-feed-keys" rel="nofollow ugc">the Github repository</a>.
Licensed under the <a href="http://www.gnu.org/licenses/gpl.html" rel="nofollow ugc">GNU General Public License 2.0 (GPL)</a>

Private Feed Keys

Allows subscription to RSS feeds on private blogs that require authentication. Works with "More Privacy Options" on multi-site installs.

Protected wp-login vs Private Feed Keys