WinMX Server Response?

[Josh]

Ive been reading about how when you connect to a WinMX server you receive a "1".  How come it sends 16 bytes including the 1?

[KM]

the encryption key, look at some of the open source applications...

[Josh]

Well in most of them they just look for the 1st byte and ignore the rest.


Taken From Nushi's Dos Chat

   if(Sock.Recv(Buff, 1, 5) != 1){         // Recv Timeout
      puts("Negotiation Failed !");
      return 0;
      }
   if(Buff[0] != 0x31){               // Recv Except 0x31
      puts("Negotiation Failed !");
      return 0;
      }

   // Make Key Block
   CreateCryptKeyID(0x0057, (BYTE *)Buff);   // Chat Client Key ID is 0x0057

/End Take

See it only looks for the 1. I dont get why the server sends those.

[GhostShip]

Josh KM has already told you what they are and what they are for.
 You are receiving a key that you will use to speak to other winmx nodes, without the key your traffic will be unreadable to other winmx users.
the 31 send is merely to let you know that the cache is ready to send a key and for you to issue issue your own, as before this the cache is not able to confirm you are a winmx client.

Try watching the udp sniffer a few times to see it all operating, I feel sure you are confusing yourself over what is one of the simpler parts of how it all works.

[KM]

if you looked at more than a couple of lines of it you'd see that it receives a lot of data, not just a single byte then closes

in fact you'll see it receives 1 byte, then receives 16 bytes = 17 bytes
an identification byte (1 byte) + a crypt key (16 bytes) = 17 bytes

and it's 17 bytes including the initial identification byte (which is a '1' for winmx clients, or an '8' for the peer cache)