| 开发者 | ericmann |
|---|---|
| 更新时间 | 2017年12月30日 12:24 |
| 捐献地址: | 去捐款 |
| PHP版本: | 4.7.3 及以上 |
| WordPress版本: | 4.9.1 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
/secure-messaging directory to the /wp-content/plugins/ directory.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.
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.
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. Note: This plugin has been tested to work with both Liquid Web's managed WordPress hosting platform and the Dockerized WordPress system published by 10up.
SECUREMSG_KEYCHAIN_DIR constant for overriding where keys are stored