You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm trying to analyze how FIFA enforces the single-session lockout feature, where logging in on console prevents additional sessions from being created on other devices or vice versa. Specifically, I'd like to see if there's a way to capture or replicate the network requests that trigger this lockout.
However, in my testing, all console traffic appears to be encrypted (likely HTTPS/TLS with possible certificate pinning). Common approaches—like Wireshark or local proxy tools (e.g., Charles, mitmproxy)—haven’t worked because I can’t install or trust a custom CA on the console. Thus, I'm stuck at capturing gibberish or seeing failed handshakes.
What I’ve tried
Setting my console’s network DNS and gateway to my PC’s proxy.
Using Wireshark on the local network to see packets (encrypted).
Searching forums, but mostly finding info on intercepting the PC or Web/mobile companion app traffic.
Why I think this repo might help
I see this project references reverse engineering or analyzing traffic for EA or console titles. I’m hoping there's a known workaround or partial solution for capturing these console requests.
Questions
Is there any known method to intercept or decrypt console traffic?
Does console traffic remain locked behind certificate pinning or system-level encryption that’s effectively unbreakable without deeper console hacking?
If you’ve successfully analyzed the console’s single-session enforcement logic, can you share any guidance or references?
Thanks.
The text was updated successfully, but these errors were encountered:
Hello! I'm trying to analyze how FIFA enforces the single-session lockout feature, where logging in on console prevents additional sessions from being created on other devices or vice versa. Specifically, I'd like to see if there's a way to capture or replicate the network requests that trigger this lockout.
However, in my testing, all console traffic appears to be encrypted (likely HTTPS/TLS with possible certificate pinning). Common approaches—like Wireshark or local proxy tools (e.g., Charles, mitmproxy)—haven’t worked because I can’t install or trust a custom CA on the console. Thus, I'm stuck at capturing gibberish or seeing failed handshakes.
What I’ve tried
Why I think this repo might help
I see this project references reverse engineering or analyzing traffic for EA or console titles. I’m hoping there's a known workaround or partial solution for capturing these console requests.
Questions
Thanks.
The text was updated successfully, but these errors were encountered: