Marc Armengou

Signed Posts allows authors to sign posts, assuring content integrity. Signature verification proves post-signing alteration hasn’t occurred.
Features:
<ul>
<li>In-browser verification: The signature verification is done on the client side (in the visitor’s browser).</li>
<li>Methods: OpenPGP (ASCII-armored detached signature) and DID (did:key, did:web) using Ed25519 detached JWS (b64=false).</li>
<li>Source of trust: For OpenPGP, the author specifies the URL of their public key in their profile. For DID, the author sets their DID (did:key or did:web). For did:web, the plugin fetches <code>https://<host>/.well-known/did.json</code>.</li>
<li>Status block: An informative block is automatically added to the end of each signed article, showing the verification status (valid, invalid, or error).</li>
<li>Author badge: The author name in posts is enhanced with an icon and KeyID/fingerprint text.</li>
</ul>
<h3>Source Code and Libraries</h3>
OpenPGP.js 
* Version: 6.2.2 
* License: LGPL-3.0-or-later 
* Public Source Code: https://github.com/openpgpjs/openpgpjs
Web Crypto API 
* Used to verify Ed25519 signatures for DID.

Signed Posts

Signed Posts allows authors to sign posts, assuring content integrity. Signature verification proves post-signing alteration hasn't occurred.

arnesonium

This plugin uses <a href="http://openpgpjs.org/" rel="nofollow ugc">OpenPGP.js</a> to provide public key encryption for a 
textarea. It is most useful for any kind of text area that will be 
submitted via email or over an unsecured network connection.
The GitHub repository for this plugin is located at https://github.com/pymander/wordpress-openpgp
<h4>Usage</h4>
This plugin provides a simple shortcode which you can add to your 
forms. To use the shortcode, you must first upload your ASCII-armored 
public key to your blog’s media section. Note that the public key must 
reside on the same server as your blog.
The <code>cryptbutton</code> shortcode takes the following arguments.
keyid 
The media ID of your ASCII-armored public key. Either this or <code>keyurl</code> 
are required.
keyurl 
The URL for your ASCII-armored public key. Either this argument or 
 keyid are required.
textarea 
Optional. The HTML ID for the textarea element to be encrypted. When 
this is omitted, the plugin will try to find the correct textarea 
automatically.
class 
Optional. Specify additional CSS classes for the button element.
text 
Optional. Specify the button text. This defaults to “Encrypt”. You can 
also use the shortcode as an open/close tag, and the contents will be 
used as the button text.
<h4>Example</h4>
This example uses the <a href="http://jetpack.me/" rel="nofollow ugc">Jetpack for WordPress</a> contact form. You can 
see an example of the output on my <a href="http://arnesonium.com/contact/" rel="nofollow ugc">Contact page</a>. The WordPress code 
looks something like this:
<pre><code>[contact-form subject='ARNESONIUM CONTACT']
[contact-field label='Name' type='name' required='1'/]
[contact-field label='Email' type='email' required='1'/]
[contact-field label='Phone' type='text'/]
[contact-field label='Comment' type='textarea' required='1'/]
[cryptbutton keyid=42]Encrypt[/cryptbutton]
[/contact-form]
</code></pre>
Line 6 displays the cryptbutton usage. Note that I changed some 
elements of this example to make things clearer. You will need to play 
with layout and CSS to get things looking nice.
<h4>Contact Form 7</h4>
This plugin also adds a <code>cryptbutton</code> shortcode to 
<a href="http://contactform7.com/" rel="nofollow ugc">Contact Form 7</a>. Shortcodes use a slightly 
different syntax with CF7. All of the options are still available, but 
the example above would be used in a form like this:
<pre><code>
[cryptbutton keyid:42 "Encrypt"]
[submit "Send"]

</code></pre>

OpenPGP Form Encryption for WordPress

OpenPGP public key encryption for any textarea with a shortcode button.

Signed Posts vs OpenPGP Form Encryption for WordPress