Skip to content

chore: update module github.com/greenpau/caddy-security to v1.7.0 - autoclosed - #1999

Closed
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/toolchain
Closed

renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/toolchain

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/greenpau/caddy-security 1.6.2 → 1.7.0 age confidence

Release Notes

greenpau/caddy-security (github.com/greenpau/caddy-security)

v1.7.0

Compare Source

Caddy Security v1.7.0 upgrades go-authcrunch from v1.5.0 to v1.6.0 and brings identity-bound profile, password-management, and encrypted Documents workflows to the optional SQLite identity backend.

  • SQLite profile and password support. SQLite users can read profile information, diagnostics, and supported dashboard data, and change their passwords. Operations validate the current immutable account identity; stale login evidence is rejected after credential or account changes. The backend remains sqlite, regardless of its realm name. AuthCrunch implementation, Caddy integration.
  • Encrypted Documents for SQLite accounts. All sixteen Documents operations are available with the required configuration. Caddy E2E coverage exercises upload/download, sharing and revocation, administrator isolation, account deletion/recreation, restart ownership, and browser Web Crypto. Smoke tests also cover the shipped Profile information, Security Manager account details, and File Vault pages. Caddy qualification.
  • Authenticated capability discovery. GET <portal-mount>/api/capabilities reports backend identity, supported operations, configuration state, permissions, and signing-key availability. Clients can distinguish unavailable features from disabled or forbidden ones. Discovery does not replace each API's authorization checks. Upstream change.
  • Safer administration and storage failures. SQLite administration returns structured public identity fields, capability metadata, and supported credential counts without exposing credential collections. Role additions are atomic and idempotent. Identity locks remain held until callbacks finish, and queued operations cannot enter a quarantined database. Storage errors distinguish storage_unavailable from commit_uncertain. Upstream implementation.
  • Inherited portal hardening. AuthCrunch rejects ambiguous decoded portal paths beginning with // or /\, escapes inferred mount segments once, and scopes legacy signing-failure diagnostics to the individual event. Runtime change, route-contract regressions.
  • Security dependency updates. Upgrade crewjam/saml to v0.6.3 and golang.org/x/net to v0.62.0 through AuthCrunch v1.6.0, including signed-response regression coverage for SAML subject namespaces. Upgrade klauspost/compress to v1.20.2 for GO-2026-6865. CI and release builds use Go 1.26.11. AuthCrunch dependency fixes, Caddy dependency updates.
  • Build and test reliability. Prefer installed Python 3.14 while honoring explicit interpreter overrides, preserve that interpreter through nested commands, normalize Go execution timestamps, and provide browser prerequisites for SQLite Documents CI shards. Improve TLS failure diagnostics, avoid stale connections after reload, bound live browser contexts, and align oversized public-key upload tests with HTTP 413. Caddy changes.

For upgrades, SQLite companions remain opt-in build modules; the standard Caddy release binary does not automatically include them. Existing Profile, Admin, and Documents configuration controls apply, with no new Caddyfile switch for this integration. The existing SQLite account schema, account UUIDs, enrollment tombstones, and encrypted document format are preserved. Stop/start preserves accounts and vault ownership but requires fresh login evidence; already issued stateless access tokens retain their bounded lifetime.

API clients should handle structured SQLite administration fields and treat missing credential counts as unsupported rather than zero. Administrative mutations retain their HTTP-200 failure envelopes, so inspect the response body. Account and Documents writes are separate transactions: reconcile a commit_uncertain result before retrying a mutation. Within this SQLite identity store, API keys, public-key collections, MFA, stored login rules, connected accounts, and downstream OIDC provider realms remain unsupported. Full capability-aware UI integration remains separate work.

The verified SAML namespace correction does not remove the unbounded affected-version range in GO-2026-6909; scanners may still report that advisory. Legacy OpenPGP findings match the module, but the affected deprecated packages are absent from the qualified production binaries. Residual SAML and historical Caddy advisory assessments are retained rather than suppressed. This release does not claim that every scanner finding is resolved.

Release validation and publication passed for the exact v1.7.0 tag, and the CodeQL workflow completed successfully. Pre-release qualification included race-enabled Go unit/E2E tests with Chrome and Consul, SQLite handoff and Documents journeys, all twelve cross-built command targets, and 36 packaged configuration checks. Official OIDC conformance was not part of this qualification. Release workflow, CodeQL workflow.

Release assets include Caddy and caddy-authenticator archives for Linux, macOS, and Windows on amd64 and arm64, plus authcrunch_1.7.0_SHA256SUMS.

The upstream range also adds web-app and React authentication guidance and a Documents test-driver-only CodeQL exception. These are contributor tooling changes, not additional runtime capabilities or a Caddy-wide scanner exception.

Full comparisons: Caddy Security v1.6.2 → v1.7.0, go-authcrunch v1.5.0 → v1.6.0.


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title chore: update module github.com/greenpau/caddy-security to v1.7.0 chore: update module github.com/greenpau/caddy-security to v1.7.0 - autoclosed Nov 17, 2026
@renovate renovate Bot closed this Nov 17, 2026
@renovate
renovate Bot deleted the renovate/toolchain branch November 17, 2026 02:09
@github-advanced-security

Copy link
Copy Markdown
Contributor

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions

Copy link
Copy Markdown
Contributor

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

  • Components: 1873

🔍 Vulnerability Scan

Severity Count
🔴 Critical 0
🟠 High 0
🟡 Medium 13
🟢 Low 2
Total 16

📎 Artifacts

  • SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

Generated by Supply Chain Verification workflow • View Details

@codecov

codecov Bot commented Nov 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant