Linus Rath 4bbcf9cdd7 fix: check telemetry targets at connect time and fail closed ...

The telemetry sender and the Stalwart version probe checked the target
with their own DNS lookup and then fetched with a plain `fetch`, which
resolved the name again: a rebinding answer between the two reached an
internal host, and a lookup that failed at check time passed the check
outright. Both now connect through `fetchPublicUrl`, which validates
the address inside the socket's own lookup and fails when the lookup
does. The `BULWARK_TELEMETRY_ALLOW_PRIVATE` dev bypass keeps the plain
fetch.

2026-09-26 15:15:23 +02:00

..

endpoint-guard.ts

fix: check telemetry targets at connect time and fail closed

2026-09-26 15:15:23 +02:00

index.ts

fix: block telemetry endpoint from pointing at internal hosts

2026-04-28 17:16:30 +02:00

login-tracker.ts

feat: track unique logins

2026-04-28 08:19:46 +02:00

payload.ts

fix: check telemetry targets at connect time and fail closed

2026-09-26 15:15:23 +02:00

sender.ts

fix: check telemetry targets at connect time and fail closed

2026-09-26 15:15:23 +02:00

state.ts

fix: make telemetry opt-in

2026-06-14 14:31:26 +02:00

types.ts

feat: add contacts feature gate and update telemetry payload

2026-04-28 17:54:11 +02:00