Follow me on twitter

Compiling

PackConfig

You should have generated a pack.cfg according to GettingStarted#PackConfig.

Proper build process

You only need to compile once per operating system for every release; you only need to compile *1* time for Linux and *1* time for FreeBSD. You copy these binaries to a webserver, or your own PC, and download/upload them to each server when you want to setup a new bot. Setting up bots in the binary remotely is not needed and can in fact be more confusing. You would only recompile when a new version comes out, or you want to change your hubs and update, or are patching the source and want to update. See also: Updating

One time per operating system and version

  1. Compile
  2. Initialize binary with your PackConfig file
    1. ./wraith -Q
      • Paste in pack config
  3. Copy binary to shells as needed and setup according to BotSetup

Compiling

Caveats

  • distcc/ccache are supported
  • Binary compatibility
    • Binaries compiled on FreeBSD 5/6/7/8 will NOT work on FreeBSD 4, skirting around this and compiling on FreeBSD 4 will render the update process useless and will result in a headache later.
    • Encourage your admins to upgrade instead, as it's likely if you are on a FreeBSD 4, 5, <6.4, < 7.1 server, it is vulnerable to exploitation.
  • Wraith has only been tested on Linux/FreeBSD/OpenBSD, any deviation from this is unsupported at this time.

Compiling

  1. Unpack the tarball.
  2. Create a pack.cfg file according to PackConfig
  3. ./configure
  4. make (gmake on BSD)
  5. ./wraith -Q
    • Paste in pack config
  6. Static binary 'wraith' is ready to distribute to shells of the same operating system.

Debug

  1. Unpack the tarball.
  2. Create a pack.cfg file according to PackConfig
  3. ./configure
  4. make debug (gmake on BSD)
  5. ./wraith -Q
    • Paste in pack config
  6. Dynamic binary 'wraith' is ready for debugging (DO NOT DISTRIBUTE OR LEAVE THIS BINARY SITTING AROUND ON PUBLIC SHELS. IT CAN BE USED TO EASILY HACK YOUR BOTNET.)