JPKCom Enable Argon2

Plugin Name: JPKCom Enable Argon2
Plugin URI: https://github.com/JPKCom/jpkcom-argon2
Description: Enables ARGON2ID for password hashes.
Version: 2.0.8
Author: Jean Pierre Kolb jpk@jpkc.com
Author URI: https://www.jpkc.com
Contributors: JPKCom
Tags: Security, Encryption, Password, WordPress, Argon2
Requires at least: 6.9
Tested up to: 7.1
Requires PHP: 8.3
Network: true
Stable tag: 2.0.8
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Enables ARGON2ID for password hashes.

Description

Enables ARGON2ID for password hashes.

For more details visit: https://make.wordpress.org/core/2025/02/17/wordpress-6-8-will-use-bcrypt-for-password-hashing/

Documentation

API Documentation: Complete PHPDoc-generated API documentation is available at: https://jpkcom.github.io/jpkcom-argon2/docs/

Installation

1. In your admin panel, go to 'Plugins' > and click the 'Add New' button.
2. Click Upload Plugin and 'Choose File', then select the Plugin's .zip file. Click 'Install Now'.
3. Click 'Activate' to use the plugin right away.

Changelog

2.0.8

• Changed: the update manifest generator now defaults a missing Network: header to false instead of true, matching WordPress' own default. No change for this plugin, which declares Network: true explicitly
• CI: the lint and guard workflow now also runs on pushes to main. It only covered pull requests, so a direct push with bypass rights skipped every check
• Changed: comments, workflow step names and CI output across the repository are now English throughout, and the developer notes in CLAUDE.md were translated and trimmed. No effect on the shipped plugin

2.0.7

• Changed: Tested up to raised to WordPress 7.1
• Changed: the bundled updater's runtime floor now matches the plugin's own minimum. It bailed out below WordPress 6.8 while the plugin header has required 6.9 for several releases, so the check could never fire on a supported installation
• CI: the release manifest's fallback values for requires and tested now say 6.9 and 7.1. They only apply when the README metadata cannot be read, but a stale fallback would have published a minimum the plugin no longer supports

2.0.6

• Added: plugin banners (assets/banner-1544x500.avif, assets/banner-772x250.avif) — a plain #3c4955 surface with no lettering. The update manifest already advertised these two URLs, but nothing was published under them, so the plugin card in wp-admin had a broken banner

2.0.5

• CI: the release step no longer copies the staging directory into itself, so the ZIP has no empty jpkcom-argon2/jpkcom-argon2/ folder
• CI: bumped the pinned GitHub Actions (checkout v7.0.1, setup-python v7.0.0, action-gh-release v3.0.2, fetch-metadata v3.1.0), still pinned to full commit SHAs

2.0.4

• Security: update packages are now verified before installation — the verified file is handed to WordPress instead of being downloaded a second time, so the bytes that were checked are the bytes that get installed
• Security: a missing or unfetchable SHA-256 checksum now aborts the update instead of installing unverified code (previously it silently skipped verification)
• Security: pinned every GitHub Action to a full commit SHA and added Dependabot with a 7-day cooldown, so a moved tag can no longer change the release build
• Security: tightened which download the updater claims, so sibling plugins cannot match each other's package
• Fixed: sprintf() calls in the updater bound named arguments to a variadic parameter, which raises ArgumentCountError on PHP 8.3
• Fixed: the "View Details" modal could fail with a TypeError when the manifest omitted requires_plugins
• Performance: a failed manifest fetch is now cached for an hour instead of being retried on every admin request
• Added: CI workflow on every pull request (PHP lint, named-argument check, YAML validation, action-pinning guard)

2.0.3

• Docs: linked the published PHPDoc API documentation

2.0.2

• Added secure self-hosted plugin updates via GitHub with SHA256 checksum verification
• Added an automated release workflow (builds the ZIP, generates the manifest and deploys to gh-pages on tag push)
• Raised the minimum WordPress version to 6.9 and "Tested up to" to WordPress 7.0
• Switched license metadata to the SPDX identifier GPL-2.0-or-later with the HTTPS license URI
• Added PHPDoc-generated API documentation, built and deployed to gh-pages on release
• Hardening: enabled declare(strict_types=1)

2.0.1

• Fix Stable tag

2.0.0

• Added README.md
• Plugin meta data update

1.0.0

• Initial Release