-
Notifications
You must be signed in to change notification settings - Fork 7
Overview
zeroKilo edited this page Nov 9, 2019
·
9 revisions
- the game starts by processing the yeti.ini to extract the HTTP address and they key used for the checksums
- now it connects to the TCP/HTTP server and exchanges information about the authentication server via a webrequest
- it uses the result to establish a PRUDP connection
- over this it exchanges DATA payloads with encryption to get the address of the secure server
- it also request a keberos ticket for connecting to the secure server
- it now connects to the secure server with PRUDP again, this time the CONNECT QPacket has a payload and its the ticket
- todo
- Port 80 for HTTP
- Port 21030 for Authentication/Redirector Server
- Port 21031 for Secure Server