nezha_domains

0 Fork 0

mirror of https://github.com/Buriburizaem0n/nezha_domains.git synced 2026-11-04 00:40:20 +00:00

T

xvkong233 40240ed02b fix(nat): strip only dashboard-issued Authorization credentials at NAT ingress

Since 2640b86 (v2.2.11, 2026-07-20) the NAT ingress deleted the entire
Authorization header, breaking self-hosted apps behind the tunnel that
authenticate with their own Bearer tokens (e.g. the Qinglong panel login
loop).

Strip only credentials issued by this dashboard and forward foreign ones:

- controller.IsDashboardCredential classifies an Authorization value as
  dashboard-issued via a signature-only JWT parser derived from the auth
  middleware (same key, HS256 pinned, claims validation deliberately
  skipped so an expired panel token is still recognized and kept out of
  the tunnel) or an api_tokens lookup for PAT-shaped values. Unknown PATs,
  foreign signatures, other schemes and missing values pass through. When
  classification cannot complete (parser not ready, DB nil or error) the
  verdict fails closed (strip) and the log carries a fixed reason only,
  never credential content.
- Both NAT capability variants (default, and agent-compat legacy /
  invalid-capability / post-consume paths) replace the unconditional
  Del("Authorization") with stripDashboardCredential. The rpc package
  receives the classifier through SetNATDashboardCredentialGate, the same
  injection pattern as SetMCPKillSwitchObserver; an unwired gate keeps the
  historical strip-everything behavior.

Tests: controller classification semantics (panel JWT, expired panel JWT
and panel PAT stripped; foreign-signed JWT, unknown nzp_ token, random
strings, non-Bearer schemes and missing header pass through; parser
unavailable, DB nil and DB error fail closed with credential-free logs)
plus rpc unit and flow coverage for both variants (dashboard credentials
never reach the forwarded bytes; foreign and missing Authorization are
forwarded untouched).

Compatibility: no API, database or frontend changes; NAT backends that do
not use Authorization behave exactly as before.

2026-10-01 11:17:45 +00:00

.devcontainer

ci: use go1.24 (#1012 )

2025-02-28 22:19:57 +08:00

.github

ci: use latest compatible Go patch

2026-09-02 13:45:05 +00:00

cmd/dashboard

fix(nat): strip only dashboard-issued Authorization credentials at NAT ingress

2026-10-01 11:17:45 +00:00

integration/agentcompat

ci: use latest compatible Go patch

2026-09-02 13:45:05 +00:00

model

feat(auth): allow JWT IP changes by configuration (#1236 )

2026-09-12 22:59:17 +08:00

pkg

Update ddns_test.go

2026-09-14 11:06:44 +08:00

proto

feat: surface GPU memory in host state (#1235 )

2026-09-12 18:56:35 +08:00

script

feat: upgrade frontend

2025-03-22 22:44:25 +08:00

service

fix: harden dashboard security boundaries

2026-10-01 04:28:34 +00:00

.gitattributes

💄 UI: 前端优化调整

2021-01-30 11:22:59 +08:00

.gitignore

feat(auth): add PAT auth, scoped REST/MCP access, CSRF, and tenant isolation

2026-05-30 15:56:44 +00:00

.goreleaser.yml

feat(v2.0.0): tsdb (#1162 )

2026-02-15 13:13:33 +08:00

Dockerfile

fix: embed tzdata to correct container timezone (#1126 )

2025-10-03 09:33:12 +08:00

go.mod

chore(deps): update direct dependencies

2026-09-02 13:30:46 +00:00

go.sum

chore(deps): update direct dependencies

2026-09-02 13:30:46 +00:00

LICENSE

Create LICENSE

2021-03-22 17:41:38 +08:00

README.md

update contributors[no ci]

2026-09-14 11:23:19 +08:00

SECURITY.md

Update vulnerability reporting contact method

2026-05-22 22:58:18 +08:00

README.md

LOGO designed by 熊大 .

:trollface: Nezha Monitoring: Self-hostable, lightweight, servers and websites monitoring and O&M tool.

Supports monitoring system status, HTTP (SSL certificate change, upcoming expiration, expired), TCP, Ping and supports push alerts, run scheduled tasks and web terminal.

>> Telegram Channel: 哪吒监控（中文通知频道）
>> Telegram Group: Nezha Monitoring Global (English Only), 哪吒监控（中文群组）

>> Use Cases | 我们的用户 (Google)