Hullo. I'm having a bit of trouble with this packet which is causing me no end of frustration. Here's the offending code (c++ with managed extensions)
[code]
    void KBin::Send0x51(Packet *s50)
   {
      // Read managed strings from buffer.
      String *msFilename = s50->sRead(20, Packet::UNTIL_NULL);
      String *msValueString = s50->sRead(msFilename->Length + 21, Packet::UNTIL_NULL);
      int iLenVS = msValueString->Length;
      int iLenFn = msFilename->Length;

      char *szFilename = new char[iLenFn + 1];
      char *szValueString = new char[iLenVS + 1];

      // managed string to zero terminated string
      KBinary::mstosz(msFilename, szFilename);
      KBinary::mstosz(msValueString, szValueString);



      // Read unmanaged values
      DWORD dwLogonType = s50->dRead(0);
      DWORD dwServerToken = s50->dRead(4);
      DWORD dwChecksum = 0;
      DWORD dwVersion = 0;
      DWORD dwClientToken = GetTickCount();
      DWORD dwProdId = 0, dwValue1 = 0, dwValue2 = 0;

      char *szExeInfo = new char[128];
      // compatability with unsigned char __gc[]
      unsigned char *bKeyHash = new unsigned char[20];


      if (dwLogonType != 0)
         throw new Exception("Unhandled Logon Version");
   
      if (!CheckRevision("C:\\downloads\\hash\\starcraft.exe",
                   "C:\\downloads\\hash\\storm.dll",
             "C:\\downloads\\hash\\battle.snp",
            szValueString, &dwVersion, &dwChecksum, szExeInfo, szFilename))
      {
            throw new Exception("CheckRevision Failed");
      }

      
      ///<fixme type = "hardcoding" id = "cdkey value"/>
      if (!DecodeCDKey("123456789ABCD", &dwProdId, &dwValue1, &dwValue2))
         throw new Exception("DecodeCDKey Failed");
      

      DWORD dwHashBuff[6];
      dwHashBuff[0] = dwClientToken;
      dwHashBuff[1] = dwServerToken;
      dwHashBuff[2] = dwProdId;
      dwHashBuff[3] = dwValue1;
      dwHashBuff[4] = 0;
      dwHashBuff[5] = dwValue2;

      calchashbuf((DWORD *)bKeyHash, dwHashBuff, 6 * 4);

      Packet *p = new Packet();
      p->Clear();
      p->Command = 0x51;
      p->dInsert(dwClientToken);
      p->dInsert(dwVersion);
      p->dInsert(dwChecksum);
      ///<fixme type = "hardcoding" id = "key amount"/>
      p->dInsert(0x01);
      ///<fixme type = "hardcoding" id = "spawn flag"/>
      p->dInsert(0x00);
      ///<fixme type = "hardcoding" id = "key length"/>
      p->dInsert(0x0D);
      p->dInsert(dwProdId);
      p->dInsert(dwValue1);
      p->dInsert(0x00);
      
      p->bInsert(bKeyHash, 0, 20);

      p->sInsert(szExeInfo, true);
      ///<fixme type = "hardcoding" id = "username"/>
      p->sInsert("Solumaeus",true);
      p->Send();

      delete [] bKeyHash;
      delete [] szValueString;
      delete [] szFilename;
   }
[/code]

Thanks in advance for any pointers. Critiques / Comments on style welcome as well.

Edit: looks like the forum mauled my hex dump. sorry.
Edit: hex dump removed. Moved to later post.

The sz prefix traditionally denotes a "string, zero terminated". If you must use Hungarian notation, it's best to not use inaccurate prefixes!

All of those byte-copy for loops look pretty slow - isn't there some sort of direct copy/assignment you could use instead?

Anyways, you didn't really specify what was going wrong. Maybe if you tell us that, we can be of more assistance.

[quote]
The sz prefix traditionally denotes a "string, zero terminated". If you must use Hungarian notation, it's best to not use inaccurate prefixes!
[/quote]
Thanks.

[quote]
All of those byte-copy for loops look pretty slow - isn't there some sort of direct copy/assignment you could use instead?
[/quote]
The managed string to char * routines I played with before seemed to be more expensive, but I went back and put them in anyway. I tried to weasel my way around converting an unsigned char array to an unsigned char __gc[] since my packetbuffer class is written in C#. Anyway, I just put an "unsafe" bInsert() function into my packetbuffer class that takes a byte* and a count, so that should deal with that.

[quote]
Anyways, you didn't really specify what was going wrong. Maybe if you tell us that, we can be of more assistance.
[/quote]

As far as I can tell nothing -- except I get an invalid version response at best and ip banned usually. I've compared packet logs of my client with that of the starcraft client and damned if I can find a difference. I am generating the same Checksum / Version information that starcraft does, and If I set my ClientToken to the one used by the client on any particular connection, I can generate the same hash. I'm looking for any reason why I would be IP banned.

Note: original code updated.

Looks like he set it up as a byte array of size 20, then inserted 20 elements. 5 * 4 is 20, is it not?

At any rate, I can't see anything that *looks* wrong...you're correctly calculating the packet size, right?

I think so; so far the only thing that I can think of is that I am having some sort of big endian / little endian problem in my packetbuffer class; since i'm using the System::BitConverter to convert other types to byte arrays, I'm having a hard time double checking.

[quote author=K link=board=17;threadid=1238;start=0#msg9248 date=1052229491]The only thing that I can think of is that I am having some sort of big endian / little endian problem in my packetbuffer class.[/quote]You usually don't need to do endian conversions; what's your target platform?

I realize that my platform and battle.Net are both little endian, but I'm unsure of whether or not the bitconverter is honoring this.

[quote author=K link=board=17;threadid=1238;start=0#msg9255 date=1052241834]
I realize that my platform and battle.Net are both little endian, but I'm unsure of whether or not the bitconverter is honoring this.
[/quote]If you're not sure about this, I'd recommend running something like 0x12345678 through the "bit converter" and checking the result with a byte hex dump...

I actually went back and rewrote my packetbuffer class in c++ without the use of the BitConverter just to make sure. Unfortunantly, I'm still getting IP banned.

I managed to log myself being IP banned as well as recieving an invald version response. Maybe someone will have a breakthrough with this. I've looked it over and I didnt see anything, but that doesn't mean someone else won't see something. (I modified my dumping function to not log high ascii value characters, so hopefully the forum wont choke)

[code]
Invalid Version Response
[KBin] Sent Packet: 0x50
FF 50 3A 00 00 00 00 00 36 38 58 49 52 41 54 53 ˙P:.....68XIRATS
C7 00 00 00 00 00 00 00 C0 A8 01 65 2C 01 00 00 ?.......A"?e,?..
09 04 00 00 09 04 00 00 55 53 41 00 55 6E 69 74 .?...?..USA.Unit
65 64 20 53 74 61 74 65 73 00 ed.States.

[KBin] Caught Packet: 0x25
FF 25 08 00 71 7E 22 A1 ˙.q~ˇ

[KBin] Sent Packet: 0x25
FF 25 08 00 71 7E 22 A1 ˙.q~ˇ


[KBin] Caught Packet: 0x50
FF 50 64 00 00 00 00 00 63 46 2E 66 44 CF 73 00 ˙Pd.....cF.fDIs.
00 3C 5B A5 63 E8 C0 01 49 58 38 36 76 65 72 31 .<[?c?A?IX86ver1
2E 6D 70 71 00 41 3D 31 30 34 38 36 38 31 39 36 .mpq.A=104868196
36 20 42 3D 34 35 35 35 36 30 30 38 31 20 43 3D 6.B=455560081.C=
38 33 35 33 32 37 35 39 34 20 34 20 41 3D 41 2B 835327594.4.A=A+
53 20 42 3D 42 5E 43 20 43 3D 43 2D 41 20 41 3D S.B=B^C.C=C-A.A=
41 2B 42 00 A+B.

[KBin] Sent Packet: 0x51
FF 51 6E 00 19 ED 26 01 01 00 01 01 87 A7 C8 6A ˙Qn.??&??.????Ej
01 00 00 00 00 00 00 00 0D 00 00 00 01 00 00 00 ?...........?...
7F F7 03 00 00 00 00 00 ???.....
73 74 61 72 star
63 72 61 66 74 2E 65 78 65 20 30 37 2F 32 37 2F craft.exe.07/27/
30 31 20 32 33 3A 34 37 3A 32 38 20 31 30 36 34 01.23:47:28.1064
39 36 30 00 53 6F 6C 75 6D 61 65 75 73 00 960.Solumaeus.

[KBin] Caught Packet: 0x51
FF 51 09 00 01 01 00 00 00 ˙Q..??...
[/code]

[code]
IP Banned
[KBin] Sent Packet: 0x50
FF 50 3A 00 00 00 00 00 36 38 58 49 52 41 54 53 ˙P:.....68XIRATS
C7 00 00 00 00 00 00 00 C0 A8 01 65 2C 01 00 00 ?.......A"?e,?..
09 04 00 00 09 04 00 00 55 53 41 00 55 6E 69 74 .?...?..USA.Unit
65 64 20 53 74 61 74 65 73 00 ed.States.

[KBin] Caught Packet: 0x25
FF 25 08 00 07 D7 03 6F ˙.x?o

[KBin] Sent Packet: 0x25
FF 25 08 00 07 D7 03 6F ˙.x?o

[KBin] Caught Packet: 0x50
FF 50 63 00 00 00 00 00 BE 0E 40 02 2B D0 73 00 ˙Pc.....????+Ds.
00 3C 5B A5 63 E8 C0 01 49 58 38 36 76 65 72 36 .<[?c?A?IX86ver6
2E 6D 70 71 00 41 3D 33 32 35 37 35 33 37 31 37 .mpq.A=325753717
20 42 3D 32 30 39 32 37 34 37 37 31 20 43 3D 32 .B=209274771.C=2
30 37 35 37 37 32 31 36 20 34 20 41 3D 41 5E 53 07577216.4.A=A^S
20 42 3D 42 2D 43 20 43 3D 43 5E 41 20 41 3D 41 .B=B-C.C=C^A.A=A
5E 42 00 ^B.

[KBin] Sent Packet: 0x51
FF 51 6E 00 FD 79 29 01 01 00 01 01 06 3B AB EB ˙Qn.yy???.???;??
01 00 00 00 00 00 00 00 0D 00 00 00 01 00 00 00 ?...........?...
7F F7 03 00 00 00 00 00 ???.....
73 74 61 72 star
63 72 61 66 74 2E 65 78 65 20 30 37 2F 32 37 2F craft.exe.07/27/
30 31 20 32 33 3A 34 37 3A 32 38 20 31 30 36 34 01.23:47:28.1064
39 36 30 00 53 6F 6C 75 6D 61 65 75 73 00 960.Solumaeus.

[KBin] Connection closed.
[/code]

[quote author=K link=board=17;threadid=1238;start=0#msg9259 date=1052249269][code][KBin] Caught Packet: 0x51
FF 51 09 00 01 01 00 00 00 ˙Q..??...
[/code][/quote]I beleive that result code is invalid version. Check to make sure that your hash files are correct.

Right; I plan to deal with that after I can connect without being IP banned 3/4 times. ;)

The data appears to be correct. Verify that your CD key data is correct.

If you have no means of doing this, BNLS can be used. You can compare what BNLS returns to you verses what your code returns. To see the correct CD key encryption for 0x51, use CDKEY_EX packets (you could use CDKEY packets, but those do not allow you to specify what the client key is). To see if your hashing algorithm is correct, use the HASHDATA packets. With common sense, you can use a combination of your own code and BNLS's packets to find your problem.

Does Battle.net IP ban for invalid key data? Wouldn't I just get an invalid cd key response?

[quote author=K link=board=17;threadid=1238;start=0#msg9274 date=1052262592]
Does Battle.net IP ban for invalid key data? Wouldn't I just get an invalid cd key response?
[/quote]The server will ban you for invalid cdkeys. Apparently the theory is that anyone with an invalid key is probably an illegal user anyway, so it is no loss to ban them.

I think it does ban for an invalid key, but I'm not sure. This makes sense when you consider that the games won't let you install without a valid key, therefore, no official client should ever supply an invalid one.

what about the muted keys whats the point of them bliz just mutes them but they still let them play games its gay the only thing mutes would be good for is like winbotting with and if they ban the keys they got lost numbers that are gonna be recycled sooner or later

[quote author=SubLiminaL_WolF link=board=17;threadid=1238;start=15#msg9367 date=1052367925]what about the muted keys whats the point of them[/quote]Mostly to prevent people from using them for spamming purposes.
[quote author=SubLiminaL_WolF link=board=17;threadid=1238;start=15#msg9367 date=1052367925]if they ban the keys they got lost numbers that are gonna be recycled sooner or later[/quote]Take a look at the StarCraft CD key decryption algorithm, and make a guess at how many possible valid codes there are.

[quote author=SubLiminaL_WolF link=board=17;threadid=1238;start=15#msg9380 date=1052385722]
there isnt that many bcuz within the cdkey there is a code that reches the limit of 5 numbers or letters the added crap is used for whole cdkey purposes (ex. *not a real key* 2517-55243-8495) within the cdkey is a 5 digit code that bnet reads for a check number the rest of the code is unknown to me right now so i call it crap and the 5 digit code is not the middle 5 digits its a mix like XX17XX2XX84XX might be the code they check ;)
but enough chat about keys this topic is about 0x51 or topic should be locked
[/quote]

You forgot to finish with, "and I base this on absolutely nothing." (South Park season 6 episode 8.)

Seriously, look at the CD-key decoding algorithms. They are practically public domain, and they are completely different from what you suggested.

[quote author=SubLiminaL_WolF link=board=17;threadid=1238;start=15#msg9405 date=1052412620]
thats the way they did it b4 around 1.0 - 1.4 im unsure of the version number, they might have changed it but the console has a huge list of cdkeys for every game client most likly each client has a different set numbers to confirm some make check all numbers and letters like war3 i know for a fact that they check every n's and l's in a cdkey for starcraft and di it was diff back then im just going by a previous code that was put upon me.
Yoni you should smack yourself in the face then smack your mom for teaching you!!
[/quote]
Here are some basic guidelines for engaging in intelligent, or at least coherent, conversation:
[list][*]Spelling.
[*]Grammar. (I am not trying to be Lindy here, and I don't mind a few spelling/grammar mistakes. As long as it's readable.)
[*]Punctuation.
[*]Punctuation. (I am usually able to read posts with bad spelling and grammar, but the total misuse/lack of punctuation in the above is almost too much.)
[*]Not insulting the person you're attempting to talk to - especially not before verifying the facts.[/list]
Now, to put that aside, and relate to the content of your post:

[quote]thats the way they did it b4 around 1.0 - 1.4 im unsure of the version number, they might have changed it[/quote]
AFAIK, CD-key encoding and decoding in Starcraft has always been done the same way. I'm not 100% sure about this, since I'm not familiar with the old versions. But it definitely never was as simple as you described.

[quote]the console has a huge list of cdkeys for every game client[/quote]
What is "the console"? Is it a web site? If so, the CD-keys are very likely stolen or invalid, or collected from other places on the web (which, recursively, are very likely stolen or invalid).
If not, might you want to tell us what that is?

[quote]most likly each client has a different set numbers to confirm[/quote]
That is quite obvious. Starcraft CD-keys don't work in Diablo 2. (They don't even fit.) Diablo 2 CD-keys don't work in Warcraft 2. (They do fit.)
That alone is enough to determine each client uses at least a slight variation of the CD-key verification algorithm.

[quote]some make check all numbers and letters like war3 i know for a fact that they check every n's and l's in a cdkey[/quote]
I didn't exactly understand what you mean, but I think you're saying every digit is allowed in CD-keys. This is false.

Months ago, when Skywing and I were working on the Warcraft 3 CD-key decoding algorithm for BNLS, I found out this interesting fact: Not all digits and letters are allowed in keys.
Here is the complete list that I wrote after a little research:

[list][*]Starcraft: All digits are allowed. No letters are allowed.
[*]Diablo 2, Lord of Destruction, Warcraft 2: The following digits and letters are not allowed: 0135 AILOQSUY
[*]Warcraft 3, (probably) Frozen Throne: The following digits and letters are not allowed: 0135 AILOQSU[/list]
I speculated that this was done to prevent users from not recognizing a certain digit (for example, 0 and O look very similar, and so do 5 and S).
Whatever the reason may be, that is the fact.

[quote]for starcraft and di it was diff back then im just going by a previous code that was put upon me.[/quote]
No comment and/or unable to parse input.

[quote]Yoni you should smack yourself in the face then smack your mom for teaching you!![/quote]
What are you, in 3rd grade? I'd come up with a brilliant reply if I weren't afraid that doing so would only make me dumber.

Now, some useful information about CD-keys:
The CD-key goes through a process called decoding.
This is done by taking the original CD-key (as it is printed on the label on the jewel case or DVD box), putting it through a mathematical algorithm, and producing three numbers.
These numbers are called the Type, the Serial, and the Secret.
The Type is simply an ID number that specifies the game that the CD-key belongs to.
That is the checking that the game installers perform - just if the ID matches the game.
The Serial and the Secret have some connection which only Blizzard knows the details of. Their server checks this, but the client (installer) doesn't - this is why it's so easy to generate a CD-key that works in the installer, but so hard to generate one that works on Battle.net. The algorithm is found only in the server, which makes it impossible to reverse-engineer it (nobody has the binaries of the servers except Blizzard).

Back to the original topic...
[quote author=Kp link=board=17;threadid=1238;start=0#msg9285 date=1052272251]
The server will ban you for invalid cdkeys. Apparently the theory is that anyone with an invalid key is probably an illegal user anyway, so it is no loss to ban them.
[/quote]

But in this case I would recieve a 0x200: Invalid CD key reponse first, as indicated by Arta's BnetDocs, correct? I'm recieving no SID_AUTH_CHECK response from the server, just an immediate disconnect and ip ban.

[quote author=K link=board=17;threadid=1238;start=15#msg9464 date=1052433813]
But in this case I would recieve a 0x200: Invalid CD key reponse first, as indicated by Arta's BnetDocs, correct? I'm recieving no SID_AUTH_CHECK response from the server, just an immediate disconnect and ip ban.
[/quote]
IIRC, that depends on how invalid the CD-key is.
If the key is just a little invalid, you'll get that. If it's very invalid, you'll get ipbanned.

But I could be wrong.

[quote]
IIRC, that depends on how invalid the CD-key is.
If the key is just a little invalid, you'll get that. If it's very invalid, you'll get ipbanned.
[/quote]

I was thinking that myself, if by "a little invalid" you mean it would theoretically install the product and is hashed correctly, and by "very invalid" you mean hashed incorrectly or completely wrong.

I doubt that the problem is with my hashing algorithm, since the hashes it generates are equivalent to those generated by the calchashbuf() and HashData() functions posted elsewhere on this board.

Thanks for the help.

[quote]
[quote author=Yoni link=board=17;threadid=1238;start=15#msg9456 date=1052432952]
Here are some basic guidelines for engaging in intelligent, or at least coherent, conversation:
[list][*]Spelling.
[*]Grammar. (I am not trying to be Lindy here, and I don't mind a few spelling/grammar mistakes. As long as it's readable.)
[*]Punctuation.
[*]Punctuation. (I am usually able to read posts with bad spelling and grammar, but the total misuse/lack of punctuation in the above is almost too much.)
[*]Not insulting the person you're attempting to talk to - especially not before verifying the facts.[/list]
[/quote]
ok that was dumb!! smite for that 1
[/quote]
I am glad to see that it seemed to work, at least partially. Your latest post in this thread has infinitely better spelling, grammar, and most importantly IMO, punctuation. Great! I'm happy for you. (Not sarcastic.)
The unnecessary insults still need work though. ;)

[quote]
[quote]
I'm not 100% sure about this, since I'm not familiar with the old versions.
[/quote]
if your not 100% sure then dont explain a reason to me!!
[/quote]
I was just offering my opinion. At least I said I'm not sure, rather than just saying a lot of nonsense and treating it as solid fact.

[quote]
[quote]
What is "the console"? Is it a web site? If so, the CD-keys are very likely stolen or invalid, or collected from other places on the web (which, recursively, are very likely stolen or invalid).
If not, might you want to tell us what that is?
[/quote]
The console is the building where all the computers are at with nerds behind them with there "hacks team", as kenny-z put it, and shit! if it was a website they would be the dumbest mother fuckers on the planet!!
[/quote]
I still don't understand what you were referring to. Maybe I'm just dumb?

[quote]
[quote]
[quote]some may check all numbers and letters like war3 i know for a fact that they check every number and letter in a cdkey[/quote]
I didn't exactly understand what you mean, but I think you're saying every digit is allowed in CD-keys. This is false.
[/quote]
no im saying war3 checks ever number and letter in the cdkey
[/quote]
Ah. That it does. So does every game Blizzard has released which requires a CD-key.

If there was a digit in the CD-key that wasn't checked by the game or server, every CD-key would be worth 10 valid CD-keys (assuming Starcraft-like key), just by changing that digit. Do you really think Blizzard would allow that?

A CD-key's primary function is to prevent piracy. If every CD-key was worth 10 CD-keys, that's like saying "Buy our game once and burn it to 9 of your friends", which is exactly what CD-keys try to prevent.

[quote]
[quote]
Months ago, when Skywing and I were working on the Warcraft 3 CD-key decoding algorithm for BNLS, I found out this interesting fact: Not all digits and letters are allowed in keys.
[/quote]
i knew this alrdy when i was into making a bnet cdkey generator. y dont you make a program, if you can, that decodes the cdkeys and find the product Id/serial number/code number, which bnet looks at the list and checks it
[/quote]
I'm not sure if you're aware of this, but I'm the co-author of BNLS. Wait, never mind, you win. That would be too difficult to make. :(

[quote]
[quote]
No comment and/or unable to parse input.
[/quote]
ok no, go dress up as a computer and act like it for halloween not here! this is a forum
[/quote]
What I meant was your message was too unreadable for me to understand. Maybe I'm just being dumb again? :(

[quote]we started messing around with it and ended up gettin ip banned everytime and warned by blizzard reps. ;D
[/quote]
You seem to be proud of this fact? Hmmk...

[quote author=Yoni link=board=17;threadid=1238;start=15#msg9456 date=1052432952]
[quote]thats the way they did it b4 around 1.0 - 1.4 im unsure of the version number, they might have changed it[/quote]
AFAIK, CD-key encoding and decoding in Starcraft has always been done the same way. I'm not 100% sure about this, since I'm not familiar with the old versions. But it definitely never was as simple as you described.[/quote]
actually, it was sent in clear text origionally. still is with jstr.

[quote author=Yoni link=board=17;threadid=1238;start=15#msg9456 date=1052432952]
[quote]most likly each client has a different set numbers to confirm[/quote]
That is quite obvious. Starcraft CD-keys don't work in Diablo 2. (They don't even fit.) Diablo 2 CD-keys don't work in Warcraft 2. (They do fit.)
That alone is enough to determine each client uses at least a slight variation of the CD-key verification algorithm.[/quote]
if you'll notice the 'product id' returned from cd key decoding: it is unique to each game type
(starcraft is 1, war2 is 4, d2 is 6, etc)

[quote]The CD-key goes through a process called decoding.
This is done by taking the original CD-key (as it is printed on the label on the jewel case or DVD box), putting it through a mathematical algorithm, and producing four numbers.
These numbers are called the Type, the Serial, and the Secret.[/quote]
that's three numbers :)

[quote]actually, it was sent in clear text origionally. still is with jstr.[/quote]
Ah, you're right, I forgot. Thanks :)
But the point is, it doesn't "skip" any digits like SubLiminaL_WolF suggested.

[quote]that's three numbers[/quote]
Yes, I was just impersonating Monty Python.
err, n/m. fixed :)

correction *in ever sayd anything about skipping digits* :P

[quote]there isnt that many bcuz within the cdkey there is a code that reches the limit of 5 numbers or letters the added crap is used for whole cdkey purposes (ex. *not a real key* 2517-55243-8495) within the cdkey is a 5 digit code that bnet reads for a check number the rest of the code is unknown to me right now so i call it crap and the 5 digit code is not the middle 5 digits its a mix like XX17XX2XX84XX might be the code they check[/quote]
What did you mean then? *confused*
It seems like you meant they "check" only some digits in the key, and skip the others.

[quote author=SubLiminaL_WolF link=board=17;threadid=1238;start=15#msg9503 date=1052444491]
YAY!!!
--*Applauds Camel*-- ;D ;D
atleast someone accually gets this and the secret number is a variation of 3 numbers cuz there is only 10 numbers in the numeral system thats including 0 and each number XXX is 0-9
[/quote]

"number" != 'digit'
(notice the variations on quotes, eh?)

stop thinking in base 10; it's bad for you

Disclaimer: this is a flame greater than most of my flames (which means its really bad), so don't read any further if you're offended by flames.

To start off, Wolf, do you read JeffK? In fact, ARE you JeffK? Cause you sound a lot like him, except he punctuates and you don't type as fast as him :P.

Second, posts with one big runon sentence piss me off. What's wrong with your period key?

Third, Yoni is smarter than most of the people on this forum AND he can ban you from this forum. Since that sounds a lot like a suckup, I'll compensate by saying hes a teenager and instead of going outside he's doing math problems ;)

Fourth, why would you send 0x50 between the SYN and SYN,ACK? It would obviously not happen, because of the seq. numbers in TCP packets. I'm sure you know this.

Fifth, where do you get your information from? I don't even know how the CD key algorithms work and I can still tell you're wrong.

Sixth, you are gay.

Seventh, you are going the way of ILurker, but faster. ILurker was a stupid, pissy newb who thought he was better than a few people. You are a stupid, pissy newb who thinks you are better than everyone else.

Eigth, I am smarter than you, I have a life, and I am straight. So don't even think of trying to come up with a good comeback since you'll get owned like all my former opponents. </joke>

Ninth, you really suck at dissing geeks. If you wanted to properly diss a bnetter, tell them to go play football.

Tenth, I couldn't come up with a tenth reason so I just wrote this instead.

So, taking it upon myself on behalf of my friends, foes, and peers on this forum, I think I can speak for all of us: LEAVE, WE DON'T WANT TO SEE YOU AND YOUR MIXED-CAPS USERNAME EVER AGAIN.

P.S. You've been added to my list. If you're wondering what the list is, just look at the replies to all of your future posts.

$t0rm:][) out.

And who's to say he doesnt ponder his algorithms and cogitate on his cosines under the shade of a lowly elm, surrounded by fern in a remote forest valley?

It's the only way to do it, in my view. :P

In case anyone was wondering what my original problem was, I figured it out, but only by completely rewriting my code in unmanaged c++. Apparently the managed socket was changing the unsigned I sent into signed chars, truncating values > 0x7F to 0x7F. See if I employ you again, managed c++! ha!