Skip to content

Releases

v1.0.3

Choose a tag to compare

@github-actions github-actions released this 18 Nov 13:52

Changed

  • Updated the startup constructor dependency used to register WAF, authentication,
    and compression plugins.

Fixed

  • Updated the SMTP email transport to fix upstream message handling, response
    parsing, and STARTTLS issues.

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Choose a tag to compare

@github-actions github-actions released this 17 Nov 16:58

Added

  • Synced selected fixes and features from the PingWAF source history through
    v0.32.31: path-scoped access rules, opt-in authenticated agent self-upgrade,
    agent peer-IP/version visibility, and upstream status / Server-Timing access
    log fields.
  • Hardened request inspection, passkey/MCP authorization, challenge clearance
    host binding, and dual-stack client-IP handling; details and source boundary
    are recorded in UPSTREAM.md.
  • Both shell installers accept a configurable HTTPS GitHub mirror in host-path
    or full-URL mode. The Compose installer also accepts a separate OCI image
    mirror and persists the chosen WAFred image path in .env for later pulls.
  • On Debian/Ubuntu, the Compose installer can install a missing Docker Engine
    and Compose v2 from the configured distribution package repository.

Fixed

  • Corrected the release installer to extract the WAFred-named archive root and
    fixed the release attestation paths to match the published assets.
  • The Compose installer now generates and preserves WAFRED_SECRET_KEY and
    passes it into the service, so stored notification, AI and backup credentials
    remain encrypted across reinstalls.
  • Host storage cleanup now protects WAFred's actual named volumes and keeps
    rollback images from ghcr.io/oyport/wafred.
  • Re-running the Compose installer preserves existing credentials and settings;
    choosing a new image mirror updates only WAFRED_IMAGE.
  • Compose startup failures now distinguish host-port conflicts from image pull
    errors in the troubleshooting message.

Full Changelog: v1.0.0...v1.0.2

v1.0.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 14:30

Fixed

  • Build x86-64 Linux binaries and Docker images for CPUs without AVX/AVX2.

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 17:42

The first independently maintained WAFred release. Functional changes from
the PingWAF source baseline are summarized below; inherited PingWAF history
remains in this file for attribution. See the 1.0.0 release guide
for setup and compatibility details.

Added

  • Per-site path restrictions with prefix, exact, wildcard and regex matching,
    optional WAF expressions, priority, time schedules and per-node request
    thresholds. Rules can block without adding an IP to the blacklist, require
    existing Basic credentials, or require OIDC sign-in for selected paths.
  • Rainbow DNS Manager (彩虹DNS) integration for ACME DNS-01 challenges, with
    automatic TXT record creation and cleanup.
  • Agent connection diagnostics for TLS/plaintext mismatches, untrusted CAs,
    certificate name mismatches and unreachable control planes.

Changed

  • WAFred is the product, executable, service, container and release archive
    identity. Its public repository is github.com/oyport/wafred and its domain
    is waf.red; the dashboard shows the PingWAF source attribution.
  • OIDC can protect only paths selected by path restriction rules. The installer
    now gives actionable TLS diagnostics for misconfigured remote agents.
  • The proxy foundation uses Pingora 0.9.1.

Fixed

  • Configured unmatched-host HTML error pages render their template values.
  • Console tables keep action buttons on one line and allow horizontal scrolling
    when their columns do not fit the viewport.

Compatibility

  • The pingwaf command, PINGWAF_* environment variables, service and data
    paths, database identifiers and PINGWAF-* managed rule IDs are no longer
    compatible. Existing installations require manual migration; no automatic
    conversion is provided. Original copyright and license notices remain in
    NOTICE.