quote:
2) to hope that MS didn't put in date & time fields like most handshake protocols do.
unquote:
Why should this be a problem?
We only have to get some Liveusers to log in.
use etherreal to snif all packets send to and back from MS.
get those data and check them about differences into each packet; just to know the 'important' packets and second; what the important differences are.
If i'm right informed; If you select Xboxlive;
1) then first checking of dashversion is done; if to old; download of new dash is performed... >>> Checked and confirmed by perdorsPad and others. (Thanks you MS!)
2) Otherwise; Live-signin is started with an encrypted modes. The sessionkey is transmitted to the xbox and the xbox encrypts/decrypts all datapackets with those sessionkey. >> thios key should be into the first packets we retrieve from MS. If we can locate it into the right packetnr. (the procedure is always exact the same!)
then we have the second step; encrypt the data inside the packets.
3) If we can manage to encrypt data into the packets; we know also what info MS get's, want's and send back to you. >> to analyse the data we learn 'the system'.
4) patch xboxonline so that it refers to a other Ip adres (those are fixed).
If we know the system, we can emulate the xboxlive server and get xlink kind of system running. >> The ultimate mod.
5) to be helpfull; into the latest MS Xbox SDK there seams to be lot's of info of xboxLive procedures, call's etc. and also there seams to be a xboxlive service EMULATE program for use on PC! Just for testing purposes.
>> Hopefully I can get acces to those XDK; to find more info regarding live.
(MS is not helping me i think with it. But if they can; i like to get a complete developer package from them for free...

)