Why every Ironhelm update is signed
How Ironhelm verifies every release with an Ed25519 signature before WordPress installs it, and why that matters even if our server were compromised.
When WordPress updates a plugin, it downloads a ZIP from the vendor's server and runs the code inside it with full access to your site, your database and your visitors. You are trusting that the file you receive is exactly the file the developer released.
Most of the time that trust is fine. The times it is not are the ones that make the news: an update server breached, a developer account taken over, a release replaced on the way. In each case, every site that updates installs the attacker's code.
How Ironhelm checks an update
Every Ironhelm Suite release is signed on an offline machine with an Ed25519 private key that never touches our servers. The signature covers four things together: a fixed label, the plugin's name, the version number and the SHA-256 hash of the exact ZIP file.
When WordPress is about to install an update of Ironhelm, the plugin steps in first. It downloads the file itself, computes its hash and checks the signature against the public key built into the version you already run. Then:
- If the signature is valid for that version and that file, WordPress continues as normal.
- If anything does not match, the file is deleted, the update stops with a plain explanation, and the refusal is written to the activity log.
What this protects you from
A compromised update server. Even if someone took over the server that offers updates, they could not produce a valid signature for altered code, because the signing key is not there. The worst they could do is withhold updates.
Tampering on the way. A file changed between our server and yours no longer matches its signature.
Old releases passed off as new. The version number is part of what is signed, so an older release with a known weakness cannot be relabelled as a new version and pushed to you.
What it does not do
Signing proves a file came from us unchanged. It does not prove the code is free of bugs; that is what our testing and changelog are for. And if you install a ZIP by hand through Plugins, Add New, WordPress does not ask Ironhelm first, so download releases only from your Ironhelm account.
Keeping the key safe
The private key lives offline, backed up in two places, and never enters a server, a repository or a release. If it ever had to change, the next release would add the new public key alongside the old one, signed with the old key, so sites move over safely through a normal update.
Security plugins ask you to trust them with a lot. Signed updates are one way we try to deserve it. More in Security and trust.
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.