Skip to content

Releases

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 10 Nov 21:39
  • Change: the settings screen is split into four tabs: Hardening, Headers
    (the standard headers and HSTS), Content-Security-Policy (the policy and
    report-only, side by side) and Check (what the site sends now, and exactly
    what this plugin sends). Save still saves every tab at once, and says so.
    After saving, checking or clearing reports, the screen comes back to the
    tab you were on. Without JavaScript the tabs work as ordinary links.
  • Change: the header check no longer lists X-XSS-Protection or Expect-CT.
    Browsers ignore both, so the two rows only ever read "not sent".
  • Change: the two status pills at the top of the screen sit together on the
    right.
  • Nothing this plugin sends has changed.

Tested up to: 7.1

Upgrade notice: Headers: unchanged. Splits Settings > Biscuit Security into four tabs: Hardening, Headers, Content-Security-Policy and Check. Save still saves every tab. The header check drops two retired headers. No setting changes.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 15:47
  • New: the collected CSP reports are listed on the settings screen: one row
    per directive and blocked source, with how many reports, when it was first
    and last seen, and a sample page. Most reported first. A source reported
    only once is greyed, because anyone can send a report. The list stays
    after collection is switched off or ends.
  • New: "Send a test report". Sends one report the way a visitor's browser
    does, with no login, and says whether it got through and was stored, or
    what stopped it: collection off, a REST API lockdown, or a firewall.
  • New: "Clear reports" deletes every collected report and restarts the
    refused counts.
  • New: a warning if the daily clean-up of old reports stops running.
  • Change: update offers now carry "Tested up to" and a one-line upgrade
    notice that says whether the release changes the headers this plugin
    sends. Both were empty before, so an update report could see that the
    version changed but not what changed. Starts with this release.
  • Change: the Settings menu entry and the screen's heading are now
    "Biscuit Security", not "Security", so they cannot be mistaken for another
    plugin's.
  • Fix: update-check failures are logged as [BSSEC], this plugin's tag. They
    were logged as [BSM], so searching a PHP log for [BSSEC] missed them.

Tested up to: 7.1

Upgrade notice: Headers: unchanged. Adds a list of collected CSP reports, a test report button and Clear reports to Settings > Biscuit Security. Nothing changes on a site that has never switched CSP report-only on.

Full Changelog: v0.3.2...v0.4.0

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 10 Nov 14:48
  • Fix: CSP reports from Safari were all refused as unreadable. Safari sends
    each report on its own, labeled as the older report format but written in
    the newer one. Reports are now read by their shape rather than their label,
    so the older format, a newer-format list (Chrome) and a single newer-format
    report (Safari) are all accepted.
  • Fix: Safari writes the default port into addresses (https://example.com:443)
    where Chrome does not. Default ports are now dropped, so one site is one
    source whichever browser reported it.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 23:02
  • Fix: CSP reports from Chrome were mostly refused. Chrome bundles every
    report from about the last minute into one request, and 0.3.0 kept only the
    first ten reports of a request and refused the rest. Repeats are now folded
    together first, so forty reports of the same blocked image are one row with
    a count of forty, and the limit applies to ten different sources per
    request rather than ten reports.
  • Fix: a request can now be up to 256 KB, up from 16 KB. Every report repeats
    the whole policy, so with a real policy 16 KB held only about a dozen
    reports and a bigger bundle was refused whole. At most 200 reports are read
    from one request; any beyond that are refused and counted.
  • Change: the status line now says why reports were refused, largest count
    first, for example "8 refused: 6 over the per-request limits, 1 from
    another site, 1 too large". Refusals counted by 0.3.0 show their reasons
    too.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 22:47
  • New: CSP report-only. A second policy, separate from the enforced one, that
    blocks nothing. Each visitor's browser checks pages against it and reports
    what it would have blocked, so a real policy can be written from what a site
    actually loads before anything is enforced. Off by default. Under
    Settings > Security, "CSP report-only".
  • New: reports are folded into one row per directive and blocked site, with a
    count and the time of the last report. Only the blocked site's address and
    the page's path are kept. Query strings and fragments are never stored, and
    order numbers in WooCommerce paths are replaced with {n}.
  • New: collection ends on its own, 30 days after it is switched on unless a
    later date is set. After that the header stops and the report address
    closes.
  • Note: while report-only is switched on, the plugin has its first database
    table (wp_bssec_csp_reports, capped at 500 rows, with rows not reported for
    30 days removed daily), its first scheduled task (that daily clean-up, on
    WP-Cron), and a public address browsers send reports to,
    /wp-json/bssec/v1/csp-report, with limits on size, batch and new rows per
    hour. None of the three exists on a site that never switches it on.
    Deleting the plugin removes all three.
  • Note: this policy also reaches the WooCommerce Checkout and My Account
    pages, where WooCommerce replaces the enforced Content-Security-Policy with
    its own one-line policy.
  • Note: if Perfmatters' "Disable REST API" setting is on, the report address
    is added to its exceptions while collection runs, or every report would be
    refused.
  • Note: on Kinsta, purge the site cache after changing these settings. Cached
    pages keep the headers they were stored with.

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 17:07
  • Change: this is Biscuit Security Headers under a new name, folder and
    repository: Biscuit Security, bs-security. It now covers site hardening as
    well as headers, so the old name no longer described it. WordPress sees it
    as a different plugin, so it does not update in place. Activate this one
    first, which copies the old plugin's header settings across, then deactivate
    and delete Biscuit Security Headers.
  • New: hide usernames from logged-out visitors. Closes the REST API users
    routes, the ?author=1 lookup, the users list in WordPress's own sitemap, and
    the author name in oEmbed data. The rest of the REST API keeps working. On by
    default.
  • New: one login error for every mistake, and the lost-password form shows the
    same "check your email" screen whether the account exists or not. Error codes
    are kept, so lockout and logging plugins still see what happened. On by
    default.
  • New: switch off the theme and plugin file editor, the same three capabilities
    DISALLOW_FILE_EDIT removes, without editing wp-config.php. Plugin updates are
    not affected. On by default.
  • New: optional redirect of author pages to the home page for logged-out
    visitors. Off by default, because some sites use author pages on purpose.
  • Change: the settings screen moves to Settings > Security.

Full Changelog: https://github.com/biscuitstudios/bs-security/commits/v0.2.0