Friend System Progress about fortnite-client HOT 8 CLOSED

I am currently on holidays. Before I went on holidays I looked into a way to bypass the ssl pinning. Luckily epic games doesn't use ssl pinning for the launcher yet, hence it should be easy to figure out the endpoints.

I'll be back in the mid of June and I will work on these endpoints then.

from fortnite-client.

Looking forward to that! Great repo.

from fortnite-client.

@lukechatton I added the launcher client, however I noticed there is no websocket or long polling HTTPS communication for incoming friend requests. It seems the launcher is using some custom TCP protocol additionally, to get these real time events. I expected them to use Websockets.

I am not sure if I can figure that out, but I'll try to.

from fortnite-client.

They communicate via Port 5222 using the jabber client (XMPP protocol). Communication is TLS encrypted

from fortnite-client.

Did you find anything ? Or do you have any idea on how to bypass/decrypt this TLS encryption please ?

from fortnite-client.

@leomelki Yes, I figured something out, but currently I don't have time to further investigate. I hope to have something ready to release within the next 2 month.

from fortnite-client.

Can you please tell me what you found (code if possible), I can reverse the protocol. I'm just having troubles with authentification and I don't see how to mitm the TLS encrypted connection.
Thank you

from fortnite-client.

@leomelki Currently I don't want to share how you can bypass the SSL pinning, so that you can inject your own certificates and decrypt the traffic as Epic seems to watch some Github repositories. Multiple workarounds have already been patched by Epic.

from fortnite-client.