Enrico Rossomando

Whenever you try to login into your website, you can use this plugin to trasmit your password encrypted. The encryption process is done by the Chap protocol; this is particularly useful when you can’t use ssl or other kinds of secure protocols. By activating the ChapSecureLogin plugin, the only information transmitted unencrypted is the username; password is hided with a random number (nonce) generated by the session – and opportunely transformed by the SHA-256 algorithm. 
In the first login there will be an error, but don’t worry is only a tecnical error. Indeed in the next login’s operation, if the values are correct, there will not be errors, but you give mind because the password will sended in unencrypted way. 
If you want more details about this algorithm, check <a href="http://www.devarticles.com/c/a/JavaScript/Building-a-CHAP-Login-System-An-ObjectOriented-Approach/" rel="nofollow ugc">“Building a CHAP Login System”</a>. 
This is a zero-configuration plugin.
Enrico Rossomando (redsend) this is my blog about programming, gaming and startup > <a href="https://www.mrred.it/" title="Blog about programming, gaming and startup" rel="nofollow ugc">https://www.mrred.it</a>

Chap Secure Password Login

Do not show password, during login, on an insecure channel (without SSL). Use a SHA-256 hash algorithm.

Scott Reilly

This plugin allows you to restrict the usernames that new users may use when registering for your site.
If open registration is enabled for your site (via Settings -> General -> Membership (“Anyone can register”)), WordPress allows visitors to register for an account on your blog. By default, any username they choose is allowed so long as it isn’t an already existing account and it doesn’t include invalid (i.e. non-alphanumeric) characters.
Possible reasons for wanting to restrict certain usernames:
<ul>
<li>Prevent usernames that contain foul, offensive, or otherwise undesired words</li>
<li>Prevent squatting on usernames that you may want to use in the future (but don’t want to actually create the account for just yet) (essentially placing a hold on the username)</li>
<li>Prevent official-sounding usernames from being used (i.e. help, support, pr, info, sales)</li>
<li>Prevent official username syntax from being used (i.e. if all of your administrators use a prefix to identify themselves, you don’t want a visitor to use that prefix)</li>
<li>Prevent spaces from being used in a username (which WordPress allows by default)</li>
<li>Require that a username starts with, ends with, or contain one of a set of substrings (i.e. “support_”, “admin_”)</li>
<li>Require a minimum number of characters for usernames</li>
<li>Limit usernames to a maximum number of characters</li>
</ul>
When attempting to register with a restricted username, the visitor will be given an error notice that says: 
ERROR: This username is invalid. Please enter a valid username.
NOTE: This plugin does not put any restrictions on usernames that the admin chooses for users when creating user accounts from within the WordPress admin. This only restricts the names that users choose themselves when registering for your site.
SPECIAL NOTE: Many membership plugins implement their own user registration handling that often bypasses checks (and hooks) performed by WordPress. As such, it is unlikely that the plugin is compatible with them without special plugin-specific amendments.
Compatible with Multisite and BuddyPress as well.
Links: <a href="http://coffee2code.com/wp-plugins/restrict-usernames/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/restrict-usernames/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/restrict-usernames/" rel="nofollow ugc">GitHub</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin exposes one filter for hooking. Typically, customizations utilizing this hook would be put into your active theme’s functions.php file, or used by another plugin.
c2c_restrict_usernames-validate (filter)
The ‘c2c_restrict_usernames-validate’ hook allows you to add your own customized checks for the username being registered. You can add additional restrictions or override the assessment performed by the plugin.
Arguments:
<ul>
<li>$valid (boolean): The assessment by the plugin about the validity of the username based on settings. True means username can be used.</li>
<li>$username (string): The username being registered.</li>
<li>$settings (array): The plugin’s settings.</li>
</ul>
Example:
<pre><code>/**
 * Add custom checks on usernames.
 *
 * Specifically, prevent use of usernames ending in numbers.
 *
 * @param bool $valid True if the username is valid, false if not.
 * @param string $username The username.
 * @param array $options Plugin options.
 */
function my_restrict_usernames_check( $valid, $username, $options ) {
 // Only do additional checking if the plugin has already performed its
 // checks and deemed the username valid.
 if ( $valid ) {
 // Don't allow usernames to end in numbers.
 if ( preg_match( '/[0-9]+$/', $username ) ) {
 $valid = false;
 }
 }
 return $valid;
}
add_filter( 'c2c_restrict_usernames-validate', 'my_restrict_usernames_check', 10, 3 );
</code></pre>

Restrict Usernames

Restrict the usernames that new users may use when registering for your site.

Chap Secure Password Login vs Restrict Usernames