MxO Client - Time + Random Callings

[HD_Morpheus]

Hi all!

This is a listing of what functions are called and what do they do (if we know) in the client code/window.

At the moment, only till the first auth packet, which contains a timestamp.

Client Init

msvcr71.time
msvcr71.gmtime
advapi32.cryptGenRandom

msvcr71.time seed for next srand
msvcr71.srand

msvcr71.time seed for next srand
msvcr71.srand

Client Window. Show

msvcr71._time64
msvcr71._localtime64
msvcr71._gmtime64

msvcr71.strftime format the date into Client window showed date format
msvcr71._Strftime

Client Window. Show "Login:"

msvcr71.rand * number of key Pressed plays a random typing sound

Client Window. Show "Password:"

msvcr71.rand * number of key Pressed plays a random typing sound

msvcr71.time
msvcr71.time

Launchpad Socket is created

msvcr71.time seed for next srand
msvcr71.srand returns data used for the 4bytes, aka "connection ID" for launchpad 1st packet

msvcr71.rand * n
msvcr71.time "Autenticating..." appears

msvcr71.rand launchpad socket gets a port. maybe result from this rand

msvcr71.time/msvcr71.rand * n

Socket TCP created
Socket UDP created

Exception 406D1388 raised

msvcr71.time

msvcr71.time

Socket TCP points to Auth server on 11000
Socket UDP points to itself
Socket TCP sends 1st packet to Auth server
Socket UDP sends packet(s) to itself

[rajkosto]

cant be it, as i changed time and time64, and it could still do it properly.
ill redo them all i guess

EDIT: redid them all, and now in both msvcr71 and msvcrt... still can get the current time...

[rajkosto]

morpheus, can you make that function always return 04 or whatever, so client thinks pubkey is ALWAYS valid ?