Files
OpenFUT-Bridge/docs/setup-notes.md
T
funman300 a826e5f7d3 Initial commit: OpenFUT Bridge
FIFA 23 reverse-engineering proxy and integration scaffold.

- Catch-all HTTP proxy that captures all incoming FIFA 23 traffic
- Known-route mapper (speculative FUT paths → Core API calls)
- Placeholder JSON responses for unmapped endpoints
- Admin endpoints: GET /_bridge/captures, GET /_bridge/unknown
- Capture persistence to captures/*.json for RE analysis
- 4 unit tests passing

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-25 15:09:47 -07:00

2.3 KiB

Proxy Setup Notes

Research notes for routing FIFA 23 traffic through OpenFUT Bridge.


Goal

Intercept all FUT API calls from FIFA 23 so the Bridge can:

  1. Log every request for reverse engineering
  2. Route known endpoints to OpenFUT Core
  3. Return placeholder responses for the rest

PC (FIFA 23 via EA App / Steam)

Option A: Windows hosts file

Redirect utas.fut.ea.com and related domains to localhost.

# C:\Windows\System32\drivers\etc\hosts
127.0.0.1   utas.fut.ea.com
127.0.0.1   utas2.fut.ea.com
127.0.0.1   ea.com

The Bridge must listen on port 443 (HTTPS) or 80 (HTTP). FIFA 23 expects HTTPS — you'll need a self-signed cert and need to trust it.

Option B: mitmproxy

  1. Install mitmproxy
  2. Set Windows system proxy to 127.0.0.1:8080
  3. Configure mitmproxy to forward FUT traffic to Bridge
mitmproxy --mode transparent \
  --listen-host 127.0.0.1 \
  --listen-port 8080

⚠️ FIFA 23 may use certificate pinning — this is unconfirmed. If pinning is active, the hosts file approach or a traffic-level redirect may be needed instead.


RPCS3 (PS3 emulator)

RPCS3 has built-in network settings:

  1. Open RPCS3 → Configuration → Network
  2. Set DNS to point to your OpenFUT Bridge IP
  3. Configure PSN Status to RPCN or custom
  4. The Bridge intercepts DNS and HTTP/HTTPS traffic

Research needed: RPCS3 FIFA 23 title ID and specific network behavior.


Certificate Handling

EA's FUT API uses HTTPS. Options:

  1. Self-signed cert — generate with openssl and add to system trust store
  2. HTTP downgrade — if the client accepts HTTP (unlikely for production)
  3. Traffic-level redirect — use iptables/nftables to redirect port 443 traffic
  4. No cert — if FIFA 23 PC doesn't verify certs (to be tested)

Generating a self-signed cert

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes \
  -subj "/CN=utas.fut.ea.com"

Status

🔴 Not tested yet. All of the above is research / theoretical. The first step is to capture real FIFA 23 traffic with mitmproxy and document actual endpoints.


Next Steps

  1. Set up mitmproxy on a FIFA 23 PC
  2. Start FIFA 23 and navigate to FUT mode
  3. Export the mitmproxy capture
  4. Add real endpoints to docs/endpoint-map.md
  5. Add mappings to src/mapper.rs