When you have a connection established to a remote host, there is a stream of data which you can send information to them, and likewise receive from them, on.

You only have to accept the TcpClient once, after that, you're free to send to and receive from it as you please. In most server apps that I've created, I keep a collection of all of the TcpClients, and add them to it as they come. (when you accept) Then, I usually assign a thread to each of them to listen for the actual data coming from them, receive it, and finally handle it.

To show the similarities between server and client, when the client does Connect(), the server's Pending() changes to true, and the server can then accept the connection in the form on a TcpClient or Socket. After that, any data sent from that client to the server will end up at it's network stream, and can be accessed from client.GetStream().Read().

Also, I rarely use timers in .Net. Threads ftw.

A packet buffer is basically a byte array with special functions making it easier to insert different types of data (strings, integers, etc) into it.

For example, the way you would put a string into a byte array would be:
byte[] buffer;
string a = "some string";
int t = buffer.Length;
Array.Resize(buffer, t + a.Length + 1);
Encoding.ASCII.GetBytes(a + "\n").CopyTo(buffer, t);But with a packet buffer:
PacketBuf pak = new PacketBuf();
pak.InsertString("some string");

It's incredibly simple.

byte[] data = Encoding.ASCII.GetBytes("ohai");
client.GetStream().Write(data, 0, data.Length);NetworkStream ns = client.GetStream();
byte[] data = new byte[ns.Length];
ns.Read(data, 0, data.Length);

Wow Fail Bot gets around it? Thats awsome.

I have not implemented ANY Warden support AT ALL, but thats just cool.  I'll test this out later, when i get time.

If you haven't implemented any Warden support at all, then it definitely doesn't get past it, and considering that nobody has figured out what the new packet even wants yet, let alone how to get it, I doubt that it would get past it even if you did have support in it.

Test for 0x5E in a bot, and see if warden still gets send using that packet ID.

It will. The only thing that changed was the addition of a new request. It still uses the same packet id and format, just with different values.

I think the only laptops you can find for under $350 are EeePC's. These things are tiny. I could probably fit it in my pocket. They usually have very small hard drives (mine's 2 gigs) and run Linux. (Although you can upgrade to Windows XP if your HD is big enough.)

Hmm sounds like fun! Now if only Stealthbot thought of that!

I'm sure they have, just never had the time to implement such a system. It can be done with scripting, anyways.

You're probably going to find out that it's much easier and less time consuming to just go ahead and re-install them on the other computer. You can directly copy over simple programs, but most games and 'larger' applications require certain files placed in alternate locations, such as the System32 folder, and going around and downloading all of these files individualy would be a very long and tedious process.