Both PHP 7 and a server-installed GPG environment are required for proper operation!<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":"1705367","resolution":"256x256","location":"assets"}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.3.0","0.4.0","0.4.1"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[15413,15414,600],"plugin_category":[],"plugin_contributors":[79892],"plugin_business_model":[],"class_list":["post-65868","plugin","type-plugin","status-publish","hentry","plugin_tags-gpg","plugin_tags-pgp","plugin_tags-security","plugin_contributors-ericmann","plugin_committers-ericmann"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/secure-messaging\/assets\/icon-256x256.png?rev=1705367","icon_2x":"https:\/\/ps.w.org\/secure-messaging\/assets\/icon-256x256.png?rev=1705367","generated":false},"screenshots":[],"raw_content":"\n
Automatically encrypt certain WordPress messages using your GPG public key to ensure no one but you can ever read the message.<\/p>\n\n
This is primarily used to secure password reset emails so, even if an attacker were to gain access to your email account, they couldn't change your WordPress password.<\/p>\n\n\n
This plugin requires PHP 7 or greater to operate. It does not<\/em> check for PHP compatibility directly and will not work<\/em> if installed on an older server.<\/p>\n\n 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<\/em> if GPG is unavailable.<\/p>\n\n This plugin requires PHP 7 or greater to operate. It does not<\/em> check for PHP compatibility directly and will not work<\/em> if installed on an older server.<\/p>\n\n 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<\/em> if GPG is unavailable.<\/p>\n\n Not by default. On many installations, the GPG keychain folder needs to live in the Not to my knowledge. We're using Pear's Crypt_GPG<\/a> module, which defer's to the server's GPG module directly. So long as GPG itself supports a key, this plugin will as well.<\/p><\/dd>\n Not every host does. Most self-hosting platforms will have GPG support by default, but some (like WP Engine<\/em>) do not support the GPG subsystem and will not allow you to proactively encrypt messages.<\/p>\n\n I highly suggest you look into a managed host like Liquid Web<\/a>, who does<\/em> support GPG, for your hosting needs.<\/p>\n\n Note:<\/em> This plugin has been tested to work with both Liquid Web's managed WordPress hosting platform and the Dockerized WordPress<\/a> system published by 10up<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\nManual Installation<\/h4>\n\n
\n
\/secure-messaging<\/code> directory to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
Requirements<\/h4>\n\n
Manual Installation<\/h4>\n\n
\n
\/secure-messaging<\/code> directory to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\/wp-content<\/code> 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.<\/p><\/dd>\n0.4.1<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
SECUREMSG_KEYCHAIN_DIR<\/code> constant for overriding where keys are stored<\/li>\n0.3.0<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n