The game uses HTTP-like protocol, called STS on port 6112.
First couple messages are sent as cleartext:
P /Sts/Connect STS/1.0
l:254
<Connect>
<ConnType>400</ConnType>
<Address>192.168.1.69</Address>
<ProductType>0</ProductType>
<ProductName>Gw2</ProductName>
<AppIndex>1</AppIndex>
<Epoch>479124536</Epoch>
<Program>101</Program>
<Build>1004</Build>
<Process>23128</Process>
</Connect>
Then it starts login process on TLS channel. When using saved account credentials game sends srp2 token to the server. I guess it's because password is saved as srp2 token. In the following message i inputted credentials myself, so password is sent as base64 encoded.
P /Auth/StartTls
s:1;timeout=29989
</Request>
P /Auth/StartSsoLogin STS/1.0
l:193
s:2;timeout=29990
<Request>
<Provider>Portal</Provider>
<LoginName>censored</LoginName>
<Scopes>_self full_economy</Scopes>
<Language>en</Language>
<Password>Base64Encoded</Password>
<SavePassword/>
</Request>
So my program succeeds in creating TLS connection, but I get
StsGate: permission denied 'Auth/StartSssoLogin', {not logged in}
as reply when i sent StartSsoLogin message. My guess is that there's some kind of secondary authentication process going on in TLS's encrypted handshake message.
And does it use padding as my program's encrypted handshake message is equal in size to the one that the game sends.
