Skip to content

Releases

Palisade v3.4.3

Choose a tag to compare

@github-actions github-actions released this 21 Nov 10:17
  • (#345) Mobile background tabs get stuck on the bot challenge and autobanned

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.4.3 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.4.3

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Kubernetes (Helm)

helm install waf oci://ghcr.io/sinhaparth5/charts/palisade --version 3.4.3 -n palisade --create-namespace

Or helm repo add palisade https://sinhaparth5.github.io/palisade-waf. Chart docs: deploy/helm/palisade.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.4.3" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.4.2

Choose a tag to compare

@github-actions github-actions released this 20 Nov 20:35
  • (#344) Let Google's own fetchers skip the bot challenge

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.4.2 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.4.2

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Kubernetes (Helm)

helm install waf oci://ghcr.io/sinhaparth5/charts/palisade --version 3.4.2 -n palisade --create-namespace

Or helm repo add palisade https://sinhaparth5.github.io/palisade-waf. Chart docs: deploy/helm/palisade.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.4.2" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.4.1

Choose a tag to compare

@github-actions github-actions released this 19 Nov 14:38
  • (#341) Create services from Docker container labels
  • (#340) Scan file uploads for malware with ClamAV
  • (#342) Push autobans to CrowdSec as alerts
  • (#343) Extension hook for dialing backends

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.4.1 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.4.1

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Kubernetes (Helm)

helm install waf oci://ghcr.io/sinhaparth5/charts/palisade --version 3.4.1 -n palisade --create-namespace

Or helm repo add palisade https://sinhaparth5.github.io/palisade-waf. Chart docs: deploy/helm/palisade.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.4.1" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.4.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 17:30
  • (#328) Helm chart: single-replica deployment with a persistent /data volume
  • (#329) Keep the database across Kubernetes upgrades, rollbacks and uninstalls
  • (#330) Load the DB key, first admin and TLS files from Kubernetes Secrets
  • (#331) Resolve the real client IP behind Kubernetes Ingress and cloud load balancers
  • (#332) TLS options on Kubernetes: Ingress termination, built-in ACME, cert-manager
  • (#333) Separate admin Service and NetworkPolicy in the Helm chart
  • (#334) Optional Varnish sidecar in the Helm chart
  • (#335) Prometheus ServiceMonitor and Grafana dashboard
  • (#336) Write the access log to stdout for kubectl logs and log shippers
  • (#337) Declarative config for GitOps: import a config file on install
  • (#338) Publish the Helm chart with each release and test it in CI
  • (#339) Kubernetes and Helm documentation

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.4.0 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.4.0

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Kubernetes (Helm)

helm install waf oci://ghcr.io/sinhaparth5/charts/palisade --version 3.4.0 -n palisade --create-namespace

Or helm repo add palisade https://sinhaparth5.github.io/palisade-waf. Chart docs: deploy/helm/palisade.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.4.0" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.3.4

Choose a tag to compare

@github-actions github-actions released this 14 Nov 21:54
  • Add --demo mode and a self-resetting public demo stack served over HTTPS with Caddy
  • Move embedded UI assets into an importable static package
  • Add internal/ext hooks for add-on routes, settings cards and config reload

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.4 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.4

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.4" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.3.3

Choose a tag to compare

@github-actions github-actions released this 13 Nov 14:45
  • (#320) Improve Services
  • (#319) Make the multipart request body limit configurable

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.3 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.3

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.3" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.3.2

Choose a tag to compare

@github-actions github-actions released this 13 Nov 09:41
  • (#318) Read the admin audit log from the shell (setup --audit)
  • (#317) Reset an admin's 2FA from the shell (setup --reset-2fa)
  • (#316) List admin users from the shell (setup --list-users)

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.2 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.2

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.2" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.3.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 17:30
  • (#315) Admin setup accepts a non-email login, says it configured an account it skipped, and has no password reset

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.1 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.1

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.1" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.3.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 16:54
  • (#314) Return a JSON challenge_required to API calls instead of redirecting them to the challenge page

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.3.0 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.3.0

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.3.0" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).

Palisade v3.2.9

Choose a tag to compare

@github-actions github-actions released this 12 Nov 16:47
  • (#304) Fuzz client IP resolution
  • (#305) Fuzz edge JWT verification
  • (#306) Fuzz signed cookie parsing for challenge, waiting room and SSO
  • (#307) Fuzz request body and header extractors
  • (#308) Fuzz admin rule parsers and config import
  • (#309) Read-only MCP server for AI assistants
  • (#310) Path-based checks can be bypassed with non-canonical paths
  • (#311) CSP inventory can be filled with fake reports to silence new-script alerts
  • (#312) Bot challenge pass cookie is not bound to the client
  • (#313) Allow service that uses self signed certificate

Install (Linux)

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo bash

Pin to this exact version:

curl -fsSL https://waf-install.astrareconslabs.com/palisade-waf/install.sh | sudo PALISADE_VERSION=v3.2.9 bash

Re-running the installer is safe. It upgrades the binary and restarts the service without touching your existing config or database.

Docker

docker run -d --name palisade -p 8080:8080 -v coraza-waf-data:/data ghcr.io/sinhaparth5/palisade-waf:3.2.9

Multi-arch (linux/amd64, linux/arm64). Persistent state (waf.db, certs/) lives under /data — mount a volume there. Also published to Docker Hub.

Verify checksums

sha256sum --check checksums.txt

checksums.txt and the SBOM are signed with cosign (keyless, GitHub OIDC). The installer checks the signature when cosign is installed, or check it yourself:

cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity "https://github.com/sinhaparth5/palisade-waf/.github/workflows/ci.yml@refs/tags/v3.2.9" \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

What's inside the binary

Everything is embedded, so no external files are needed at runtime:

  • Admin UI (HTMX + Tailwind templates + minified JS)
  • Bundled GeoLite2 Country database (geo blocking)
  • Bundled DB-IP ASN Lite database (ISP/org lookup)
  • OWASP Core Rule Set (WAF rules)

The only files created on disk at runtime are waf.db (SQLite) and certs/ (TLS, if enabled).