tesla-roadtrip

Files

T

tony f793b526aa fix(security): owner auth gate, OAuth state cookie binding, 0600 token perms

- Add OWNER_SECRET-based session: signed HMAC cookie, /api/auth/owner login,
  requireOwner middleware. All Tesla routes refuse 401 without it.
- Bind OAuth state to a SameSite=Lax httpOnly cookie at /start, validate
  match in /callback with constant-time compare. Refuses unmatched callbacks.
- Token store now mkdir 0700, writeFile + rename atomic, mode 0600 with
  defensive chmod. Owner-only on disk.
- VIN masked to last 4 in responses; partner-register no longer echoes raw
  Tesla body to clients; coord bounds checked on send-to-nav.
- Client: useTesla also tracks owner status; Connect Tesla button opens an
  OwnerLoginModal when not authenticated, then continues to Tesla OAuth.

Conscious deferrals:
- Explicit CSRF tokens on POST routes: mitigated by SameSite=Lax cookies
  + same-origin CORS. Will revisit if cross-origin clients land.
- At-rest token encryption: deferred for single-user app; tokens are on a
  0700 Dokku volume readable only by the app uid. Will add AES-GCM if we
  multi-tenant.

2026-05-31 22:32:22 +01:00

auth.ts

feat: wire build/test infra, trips API, and enriched journey stops

2026-05-19 10:32:53 +01:00

logger.ts

chore: initial checkpoint - Tesla Roadtrip planner

2026-05-15 19:24:35 +01:00

ownerAuth.ts

fix(security): owner auth gate, OAuth state cookie binding, 0600 token perms

2026-05-31 22:32:22 +01:00

teslaClient.ts

feat(tesla): real Fleet API integration — OAuth, vehicle state, send-to-nav