mtnviewpro

ArchivioID is an add-on plugin for ArchivioMD that adds a full cryptographic identity and signature layer to your WordPress site. It manages GPG public keys, verifies detached OpenPGP signatures on posts, supports multi-signer workflows with configurable thresholds, and exposes public proof pages so anyone can verify authenticity without logging in.
<h4>Key Features</h4>
<ul>
<li>Public Key Management: Store, manage, and rotate GPG public keys with expiry tracking and administrator alerts</li>
<li>Post Signature Verification: Upload detached .asc signature files for posts — verified automatically using phpseclib v3</li>
<li>Browser-Based Signing: Sign posts directly in the WordPress admin using a browser-held key — no server-side key material required</li>
<li>Multi-Signature Workflows: Collect signatures from multiple key holders on a single post; each signer identified by key fingerprint and timestamp</li>
<li>Configurable Signature Threshold: Require a minimum number of verified signatures before a post displays the verified badge — configurable globally or per post type</li>
<li>Algorithm Enforcement Floor: Block weak signature algorithms (MD5, SHA-1) and enforce minimum RSA/DSA key sizes at upload, REST submission, and re-verification time</li>
<li>Automated Re-Verification: Daily WP-Cron job re-verifies all signed posts and flags content that has changed since signing</li>
<li>Key Expiry Notifications: Email alerts at 30, 14, and 3 days before a key expires, sent to the key owner or site admin</li>
<li>Key Rotation Workflow: Admin UI for generating replacement keys, migrating existing signatures, and retiring old keys</li>
<li>Bulk Verification: Verify all signed posts in a single admin action with per-post status reporting</li>
<li>REST API: Full REST endpoint for programmatic signature submission, key retrieval, and verification status</li>
<li>Key Server: Publishes active public keys at a stable well-known endpoint for external verifiers</li>
<li>Bundle Download: Downloadable evidence package (hash, signatures, key fingerprints, timestamps) for any post</li>
<li>Public Proof Pages: Stable public permalink at <code>/archivio-id/verify/{post_id}</code> — renders full chain of custody without requiring admin access</li>
<li>Audit Logging: Immutable log of all verification attempts, key changes, and rotation events</li>
<li>WP-CLI Support: Full CLI interface for batch operations and automated pipelines</li>
<li>Visual Status Badges: Front-end badge showing verified / unverified / threshold-unmet status on every post</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 7.4 or higher (tested up to PHP 8.5)</li>
<li>ArchivioMD plugin version 1.5.0 or higher (required parent plugin)</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Upload your GPG public key via the ArchivioID → Key Management admin page</li>
<li>Create or edit a post in WordPress</li>
<li>Upload a detached .asc signature file for the post, or sign directly in the browser</li>
<li>ArchivioID verifies the signature immediately and on every subsequent automated re-verify run</li>
<li>A verification badge appears on the front end; a public proof page is available at a stable permalink</li>
</ol>
<h4>Technical Details</h4>
<ul>
<li>Uses phpseclib v3 for all cryptographic operations — no system GPG installation required</li>
<li>Uses OpenPGP-PHP for packet parsing and key handling</li>
<li>All key material and signatures stored in dedicated WordPress database tables</li>
<li>Algorithm enforcement floor consulted at upload, REST submission, and re-verification time</li>
<li>Multi-signature threshold evaluated before displaying the verified badge</li>
<li>Public proof pages require no admin login — safe to share externally</li>
<li>Fully WordPress coding standards compliant</li>
</ul>
<h4>External Services</h4>
This plugin can make outbound HTTP requests to the following third-party services. All external lookups are opt-in and can be disabled under ArchivioID → Settings → Key Server Lookup.
keys.openpgp.org (VKS API) 
When an administrator uses the Key Management page to look up a GPG public key by fingerprint or email address, the plugin sends a GET request to <code>https://keys.openpgp.org/vks/v1/</code>. No personal data beyond the fingerprint or email address entered by the administrator is transmitted. This request is made only on explicit administrator action and only when the “Allow key server lookup” setting is enabled. 
* Service: https://keys.openpgp.org 
* Privacy policy: https://keys.openpgp.org/about/privacy
WKD — Web Key Directory (user’s email domain) 
When an administrator looks up a key by email address, the plugin may also query the Web Key Directory endpoint on the domain portion of that email address (e.g. <code>https://example.com/.well-known/openpgpkey/</code>). This follows the OpenPGP Web Key Directory specification (draft-koch-openpgp-webkey-service). The request is made only on explicit administrator action and only when key server lookup is enabled. 
* Specification: https://datatracker.ietf.org/doc/draft-koch-openpgp-webkey-service/ 
* The domain contacted is determined entirely by the email address the administrator enters; it is not a fixed third-party service.
Identity Proof URLs (user-supplied) 
Administrators may optionally store a public identity proof URL alongside each key (for example, a Keyoxide or Keybase profile page). These URLs are stored in the WordPress database and displayed as links in the frontend badge tooltip. The plugin itself makes no outbound request to these URLs; they are rendered as standard hyperlinks for visitors to follow voluntarily. 
* Keyoxide: https://keyoxide.org 
* Keybase: https://keybase.io 
* Any HTTPS URL may be entered; the plugin validates only that the value is a well-formed HTTPS URL.
<h3>Source Code for Bundled Minified JavaScript</h3>
This plugin includes <code>assets/js/openpgp.min.js</code>, the minified build of OpenPGP.js.
<ul>
<li>Project home: https://openpgpjs.org</li>
<li>Source code: https://github.com/openpgpjs/openpgpjs</li>
<li>License: LGPL-3.0-or-later</li>
<li>Version used: 5.x (see <code>assets/js/openpgp.min.js</code> file header for exact version)</li>
</ul>
To reproduce the minified file from source:
<pre><code>`
</code></pre>
git clone https://github.com/openpgpjs/openpgpjs.git 
cd openpgpjs 
npm install 
npm run build # produces dist/openpgp.min.js 
 `
Copy <code>dist/openpgp.min.js</code> to <code>assets/js/openpgp.min.js</code> in this plugin.
<h3>Security</h3>
<ul>
<li>All inputs sanitized and validated; all outputs escaped</li>
<li>Nonce verification on all forms and AJAX handlers</li>
<li>Capability checks (<code>manage_options</code>) on all admin actions</li>
<li>REST API write endpoints require authentication</li>
<li>SQL prepared statements throughout; no raw query interpolation</li>
<li>Algorithm enforcement floor blocks known-weak cryptographic primitives</li>
</ul>
<h3>Support</h3>
For support, please visit: https://mountainviewprovisions.com/archivio-id
<h3>License</h3>
This plugin is licensed under GPLv2 or later.

ArchivioID

OpenPGP signature verification, multi-signer workflows, key lifecycle management, and public proof pages for ArchivioMD.

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.

ArchivioID vs OpenPGP Form Encryption for WordPress