Jakub Klapka

This plugin adds new status for posts (or pages/custom post types) called “Secured with link”. If you select this status, that specific post wouldn’t be accessible on its standard URL anymore, but you have to access it on URL with random token in it. This URL is displayed on post edit screen in administration.
<h4>Configuration</h4>
For now, there is no administration screen yet. To configure plugin, you can inject your changes to plugin configuration array from your theme or plugin. Just put this code into functions.php file in your theme:
<pre><code>add_filter( 'lumi.secure_post_with_link.config', function( $config ){
 $config[ 'allowed_post_types' ] = [ 'post', 'page' ];
 $config[ 'url_identifier' ] = 'sec';
 // ... Other $config variables
 return $config;
} );
</code></pre>
Preferably, don’t include lines with attributes, which you don’t want to change.
These are attributes (with defaults), which you can change this way:
<ul>
<li>
allowed_post_types ([ ‘post’ ]) List of post types, which should be affected by this plugin. Use array notation like: <code>[ 'post', 'page', 'custom_type' ]</code>.
</li>
<li>
secured_meta_name (‘_secured_with_link_token’) Name of meta, which stores post token. You can change that in case of conflicts with themes or other plugins.
</li>
<li>
url_identifier (‘s’) Part of URL before token, which identifies secured posts.
</li>
<li>
token_length (4) Length of random token. With default generator, length is in bytes!
</li>
<li>
use_openssl (true) If plugin should use cryptographically secure random generator, or less-secure PHP functions. (See below)
</li>
<li>
assets_url (Defaults to [plugin URL]/assets) URL for static assets (like Javascripts), in case, you want to use your assets for some reason.
</li>
<li>
translations_dir (Defaults to [Plugin path]/lang) You can change path, where plugin looks for translation files. If you want to translate plugin, you should not use this setting, but create standard translation in wp-content/languages folder.
</li>
</ul>
In case, you have changed any settings after plugin installation, deactivate and reactivate plugin, so all changes are correctly applied.
<h4>Compatibility</h4>
<ul>
<li>For now, you need to use WP URL Rewriting for plugin to work correctly</li>
<li>Plugin should work with PHP 5.4, but at least PHP 5.6 is highly recommended. I’m sorry, but I won’t support older, insecure and slow versions of PHP.</li>
<li>By default, plugin uses OpenSSL library to generate cryptographically secure random tokens. If your hosting provider don’t have OpenSSL set up, you can use configuration variable: <code>$config[ 'use_openssl' ] = false</code> to use less-secure method of token generating. This should still be secure enough for most use cases.</li>
</ul>
<h4>Planned features</h4>
<ul>
<li>Administration page</li>
<li>Regenerate token</li>
<li>Role management – users with privileges should be able to access post without token</li>
</ul>
<h4>Developers</h4>
Plugin is also hosted on <a href="https://github.com/jakub-klapka/wp-secure-post-with-link" rel="nofollow ugc">Github</a>.

Secure post with link

Adds new post status "Secured with Link". Posts with this status will be accessible only with randomly generated token in URL.

Julio Potier

SeoMix

SecuPress

Daniel Roch

WordPress show your WordPress login and ID in several places. It’s time to fix this !
<ul>
<li>WordPress automaticaly uses “User login” to fill in the “User Display Name”.</li>
<li>WordPress also allows everyone to use the same value for Nickname, Display Name and Login.</li>
<li>The body_class function also shows to everyone your User ID and Login on author pages.</li>
</ul>
A hacker can easily see then use your “NickName” or “Display Name” to find your real login. Once activated, SX User Name Security will prevent WordPress from showing those informations, and will warn you if you need to fix old users.
Features
Body_class function:
<ul>
<li>Removes User ID from body_class function (front-end users pages)</li>
<li>Removes User Nicename from body_class function (front-end users pages)</li>
</ul>
Current User informations:
<ul>
<li>The plugin changes “Display Name” and “Nickname” to a random value (like ‘Ticibe T. Aduvoguripe’, ‘Lagubo N. Agigerovibe’ or ‘Datela N. Orejadavino’) if they are identiqual to user login</li>
<li>If not, it changes “Display Name” to “Nickname” or “Nickname” to “Display Name” if one of them is identiqual to user login</li>
</ul>
New Registration:
<ul>
<li>Display Name and Nickname are changed to random value during user registration.</li>
<li>Nicename is also changed (it’s used to generate the user permalink on the front-end). For previous user, a notice has been added to use another plugin to safely change old nicenames.</li>
</ul>
Other information:
All functions are translated into french and english.
You can find me here on <a href="https://www.seomix.fr" rel="nofollow ugc">SeoMix</a>, and here is the official french post about this plugin <a href="https://www.seomix.fr/user-name-security/" rel="nofollow ugc">https://www.seomix.fr/user-name-security/</a>
Find here our other plugins:
<ul>
<li><a href="https://fr.wordpress.org/plugins/seo-key/" rel="nofollow ugc">SEOKEY WordPress SEO plugin</a></li>
<li><a href="https://fr.wordpress.org/plugins/secupress/" rel="nofollow ugc">SecuPress Security plugin</a></li>
</ul>

SX User Name Security

SX User Name Security prevents WordPress from showing your real Login everywhere. It ovverides the body_class function, User Nicename, Nickname and Di …

Secure post with link vs SX User Name Security