GPG security for WordPress messaging.
|Author:||Eric Mann (profile at wordpress.org)|
|WordPress version required:||4.7.3|
|WordPress version tested:||4.9.1|
|Added to WordPress repository:||30-07-2017|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Click to start download
This plugin requires PHP 7 or greater to operate. It does not check for PHP compatibility directly and will not work if installed on an older server.
The GPG functionality requires GPG to be installed and available to WordPress. The plugin will try to test for this functionality upon activation, but will not work if GPG is unavailable.
- Upload the entire
/secure-messagingdirectory to the
- Activate Secure Messaging through the ‘Plugins’ menu in WordPress.
Does the server sign messages as well?
Not by default. On many installations, the GPG keychain folder needs to live in the
/wp-content directory and might be readable by third parties. To avoid leaking GPG secret keys, none are ever added by the system in the first place. This means the server can’t sign messages before they’re sent.
Is there a limit to the size of the GPG key I can use?
Not to my knowledge. We’re using Pear’s Crypt_GPG module, which defer’s to the server’s GPG module directly. So long as GPG itself supports a key, this plugin will as well.
What if my host doesn’t support GPG?
Not every host does. Most self-hosting platforms will have GPG support by default, but some (like WP Engine) do not support the GPG subsystem and will not allow you to proactively encrypt messages.
I highly suggest you look into a managed host like Liquid Web, who does support GPG, for your hosting needs.
- Fix: Explicitly add Eric Mann’s public key for the GPG subsystem test
- Update: Store the public key fingerprint instead of the entire key for better references later
- Update: Introduce the
SECUREMSG_KEYCHAIN_DIRconstant for overriding where keys are stored
- Fix: Test for the presence of the GPG subsystem upon activation to prevent downstream errors
- Update: Switch to the Pear GPG library for better RSA compatibility
- Update: Use a new GPG library for better PHP compatibility
- Update: Add nonce checks on the profile page
- Update: Add Romanian translations
- First release