Skip to content

SecurityKit 0.1.2

Latest
Latest

Choose a tag to compare

View all tags
@RbnCore RbnCore released this 31 Oct 14:50
0.1.2
73cf38f

SecurityKit hardens the parts of a WordPress site that are open to the public, one
switch at a time, and tells you what it changed. It is not a firewall and not a malware
scanner. Nothing is on after installation: a fresh install changes nothing until you
switch a module on.

What is new in 0.1.2:

  • The security score card and the overview counters refresh live. When you switch a
    module on the Security screen, the score ring and the counters in the overview update
    by themselves — no page reload, and no trip to another tab to see the new number.
    This works when AdminKit 0.1.3 or newer is active; on an older AdminKit the screen
    simply behaves as before (nothing breaks, the numbers still update on the next page
    load).

Everything from 0.1.1 is included: the ten modules (security headers, XML-RPC, user
enumeration, version details, the file editor, login attempts, wp-config.php advice,
the activity log, e-mail alerts and the security score), all off by default.

Recovery

If you lock yourself out (for example with the login limit), add
define( 'SECURITYKIT_DISABLE', true ); to wp-config.php: no module starts while
this constant is set.

Requirements and behaviour

  • The AdminKit plugin is required (Requires Plugins: adminkit); install and
    activate AdminKit first. SecurityKit adds no hook without it.
  • WordPress 6.5+ and PHP 8.1+.
  • Updates are signed (Ed25519 + SHA-256) and follow the central AdminKit network
    setting.
  • A module that is off adds no hook and does not load its code.

SHA-256: e64470b39144b2d93a7e4786f6b1e63104a12fa88c0be6d05aa37675a78b44fa

Assets 5
Loading