Marc-André Bombeck afcb37e76c feat(config): let the operator turn off the breach and update checks ...

Two requests left the server without anything being connected: the
HaveIBeenPwned range query on every password set (registration, change,
admin reset) and the daily GitHub releases request behind the About page
and the admin version tile. Neither could be turned off, which made
"nothing leaves" untrue for an instance that wanted it to be.

PASSWORD_BREACH_CHECK_DISABLED and UPDATE_CHECK_DISABLED (1, true, yes or
on) stop each request. Both stay on by default. The breach check keeps
its fail-open contract: switched off, a password is simply not looked up.
The update route answers status "unknown" with reason "disabled" and
the admin tile says the check is off. The password routes reach the
check only through the switch, and a test holds that import line.

Both are on the compose whitelist, in the env manifest under a new
"Outbound requests" group with IP_GEO_LOOKUP_DISABLED, and documented in
both env examples and the getting-started guide.

2026-09-26 15:33:34 +02:00

..

__tests__

fix(admin): name the configured geo provider in the system snapshot

2026-06-30 18:08:57 +02:00

check-updates

feat(config): let the operator turn off the breach and update checks

2026-09-26 15:33:34 +02:00

route.ts

fix(admin): name the configured geo provider in the system snapshot

2026-06-30 18:08:57 +02:00