Named Pipes?

[xzidez]

hmm back after a break

Anyways. I was thinking of an idea to get rid of all those injections for LUA.. So Named Pipes?
good or bad?.. And should wow be my server or client?
Anyone who have tried this?

[amadmonk]

Don't remember the named pipes nomenclature, but WoW should definitely initiate the connection. That way you can and should use randomly named pipes to avoid the stupidly-easy way of detection.

Named pipes are fine; for message-oriented communication on-box, they're probably a little easier, and a little faster, than sockets.

If you have dynamic code, you can keep your number of hooks to a bare minimum (and, IMO, that's a good design, if you can get the "dynamic code" bit working properly; good luck with that).

[Nesox]

You should create the server in the bot atleast that's my opinion and that's what i did in my first attempts.
If ure using C# it's terribly easy to create a pipeserver just a couple of rows.

using System;
using System.IO;
using System.IO.Pipes;

class PipeServer
{
  static void Main()
  {
    NamedPipeServerStream pipeServer =
        new NamedPipeServerStream("testpipe", PipeDirection.Out))
    
      Console.WriteLine("NamedPipeServer created.");

      Console.Write("Waiting for client connection...");
      pipeServer.WaitForConnection();

      Console.WriteLine("Client connected.");
      pipeServer.WriteByte(0xFF);
  }
}

So that's the C# part now you just need to connect to it from C++ your dll or w/e language you are using.

Here's some code to chew make the best of it

   
  HANDLE hPipe;

   if( ! WaitNamedPipe("\\\\.\\pipe\\testpipe", 25000) ){
      //Error waiting for pipe
      return 1;
   }

   hPipe = CreateFile("\\\\.\\pipe\\testpipe",
                       GENERIC_READ | GENERIC_WRITE,
                       0, NULL, OPEN_EXISTING, 0, NULL);
   
    if( hPipe == INVALID_HANDLE_VALUE )
    {
      //"Error: cannot open named pipe\n";
      return;
    }

   char  buf[1024];
   DWORD bread;
   for(int i=0;i<15;i++)
   {
      if( ReadFile(npipe, (void*)buf, 1023, &bread, NULL) )
      {
         buf[bread] = 0;
         cout<<"Received: '"<<buf<<"'"<<endl;
      }

      Sleep(750);
   }

Hope this helps some here's some links too

A little example using pipes with .Net 3.5 - .NET 3.5 Adds Named Pipes Support | Switch on the Code

Some examples on how to do it with C++ - Advanced C++ Programming: Named pipes.

[amadmonk]

Hmm, just discovered that Unix supports named pipes too (in fact, it's even easier than in Windows). There goes my last justification for making my bot send data using sockets...