gfxgfx
 
Please login or register.

Login with username, password and session length
 
gfx gfx
gfx
75717 Posts in 13285 Topics by 2660 Members - Latest Member: badsanta308 November 18, 2018, 09:46:52 pm
*
gfx*gfx
gfx
WinMX World :: Forum  |  Technical  |  Protocol Discussion  |  WinMX Server Response?
gfx
gfxgfx
 

Author Topic: WinMX Server Response?  (Read 1434 times)

0 Members and 1 Guest are viewing this topic.

Offline Josh

  • Forum Member
  • Thinking about tomorrow...
    • http://www.winmxunlimited.net
WinMX Server Response?
« on: March 27, 2006, 12:50:47 am »
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?
- Josh

KM

  • Guest
Re: WinMX Server Response?
« Reply #1 on: March 27, 2006, 03:24:35 am »
the encryption key, look at some of the open source applications... :-P

Offline Josh

  • Forum Member
  • Thinking about tomorrow...
    • http://www.winmxunlimited.net
Re: WinMX Server Response?
« Reply #2 on: March 28, 2006, 04:31:35 am »
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.
- Josh

Offline GhostShip

  • Ret. WinMX Special Forces
  • WMW Team
  • *****
Re: WinMX Server Response?
« Reply #3 on: March 28, 2006, 07:15:38 am »
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

  • Guest
Re: WinMX Server Response?
« Reply #4 on: March 28, 2006, 08:28:43 pm »
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)

WinMX World :: Forum  |  Technical  |  Protocol Discussion  |  WinMX Server Response?
 

gfxgfx
gfx
©2005-2018 WinMXWorld.com. All rights reserved.
SMF 2.0.15 | SMF © 2017, Simple Machines
Page created in 0.044 seconds with 20 queries.
Helios Multi © Bloc
gfx
Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS!