mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-18 16:12:11 +00:00
Write restored PHI 0o600 and let TRUST_PROXY_HOPS reach the container
Two findings from the docs truth audit, both operator-facing. scripts/restore-backup.ts wrote the decrypted backup, which is health data in plaintext, with the process default file mode, leaving it world-readable on the operator's disk while it sat there. It is now written 0o600. TRUST_PROXY_HOPS is read from the environment to size the trusted X-Forwarded-For chain, but it was absent from the compose environment whitelist, so an operator value in .env never reached the container and was silently ignored. It now rides all four surfaces: the compose whitelist, both env examples, and the manifest that pnpm check-env reads.
This commit is contained in:
1 parent
7f407797f4
commit
0037cc1bcd
5 files changed
+35
-9
No files matched your search
@@ -75,6 +75,13 @@ x-healthlog-env: &healthlog_env
|
||||
# free ip-api.com endpoint) — off by default, an explicit operator choice.
|
||||
# Listed here so operator values in .env reach the container (the
|
||||
# `environment:` block is a whitelist — vars not listed never propagate).
|
||||
# TRUST_PROXY_HOPS is the number of trusted reverse-proxy hops in front of
|
||||
# the app: the client IP is read that many entries from the right of the
|
||||
# X-Forwarded-For chain. Wrong value and the app refuses to read XFF and
|
||||
# collapses every anonymous caller into one rate-limit bucket. Listed here
|
||||
# so an operator value in .env reaches the container (the `environment:`
|
||||
# block is a whitelist).
|
||||
TRUST_PROXY_HOPS: "${TRUST_PROXY_HOPS:-}"
|
||||
TRUST_CF_CONNECTING_IP: "${TRUST_CF_CONNECTING_IP:-}"
|
||||
IP_GEO_LOOKUP_URL: "${IP_GEO_LOOKUP_URL:-}"
|
||||
IP_GEO_LOOKUP_DISABLED: "${IP_GEO_LOOKUP_DISABLED:-}"
|
||||
|
||||
Reference in new issue
Block a user