| Author | Message | Time |
|---|---|---|
| UserLoser | How does BNLS hash the data for packets 53/54 or does anybody else know how to do it without BNLS? | January 15, 2003, 4:23 PM |
| Spht | I am not familiar with packets 0x35 and 0x36. | January 15, 2003, 4:32 PM |
| UserLoser | [quote]I am not familiar with packets 0x35 and 0x36.[/quote] ..........? | January 15, 2003, 4:40 PM |
| Noodlez | haha, you got owned. | January 15, 2003, 5:34 PM |
| tA-Kane | I've never seen 0x35 (perhaps you could show me a packetlog?), but 0x36 is... DWORD - CDKeyStringLength DWORD - ProductID (Not STAR/SEXP/W2BN/etc) DWORD - CDKeyValue1 DWORD - ServerKey DWORD - ClientKey 5 DWORDS - KeyHash The KeyHash is generated by doing HashData of... DWORD - ServerKey DWORD - ClientKey DWORD - ProductID DWORD - CDKeyValue1 DWORD - CDKeyValue2 The server provides the Server key in one of the first packets (too lazy to look it up atm), the client key can be anything (most people do GetTickCount()). Refer to the BNLS's GetVersionByte sequence to get the ProductID; it uses the same IDs. You get the two CDKeyValues from decrypting the CD Key. | January 15, 2003, 5:53 PM |
| zorm | you guys are so mean! :-/ | January 15, 2003, 9:25 PM |
| UserLoser | I've never heard/seen packet 35 either. I do believe i said 54/53, unless they are the same which i dont think they are... [QUOTE]haha, you got owned. [/QUOTE] Wtf is this supposed to mean? | January 15, 2003, 9:35 PM |
| Zakath | Hehe...good one Spht. Because some of my friends are stumped as well, I'll spill the beans. Convert '53' into hex. It becomes 0x35. | January 15, 2003, 11:29 PM |
| MesiaH | Zakath, you are a fucking genious! | January 15, 2003, 11:32 PM |
| Yoni | [code]#define SID_AUTH_ACCOUNTLOGON (0x53) #define SID_AUTH_ACCOUNTLOGONPROOF (0x54)[/code] [quote]How[/quote] Automagically. | January 16, 2003, 10:08 AM |
| tA-Kane | Way to ruin the fun, Zakath ::) UserLoser, you should *always* be sure the people you're asking help from know what you're referencing to, such as decimal vs hex. | January 16, 2003, 12:26 PM |
| UserLoser | I didnt even think of that | January 16, 2003, 1:30 PM |
| tA-Kane | that's intelligent... ::) *refrains from a nasty flame* | January 16, 2003, 2:29 PM |
| UserLoser | :-* <--thinks skywing should share how to hash it :o | January 16, 2003, 6:50 PM |
| Noodlez | /me thinks you dont deserve the hash if you couldnt catch on to what spht said | January 16, 2003, 8:36 PM |
| UserLoser | [quote]/me thinks you dont deserve the hash if you couldnt catch on to what spht said[/quote] [BLUE]So everytime i see numbers, im supposed to get what it means in hex?[/BLUE] --- :D | January 16, 2003, 8:44 PM |
| Yoni | [quote] [BLUE]So everytime i see numbers, im supposed to get what it means in hex?[/BLUE] --- :D[/quote] Of course... Have you ever seen The Matrix? | January 18, 2003, 8:48 AM |
| UserLoser | Yeah, but don't forget im not the only one who didnt think that at first, tA-Kane actually posted code for 0x36 8) | January 18, 2003, 3:53 PM |
| tA-Kane | Guess what 54 in decimal is in hex? | January 18, 2003, 4:16 PM |
| Arta | I just deleted a few posts from the end of this thread. Please stay on topic. | January 19, 2003, 12:23 PM |