1
0

INSTALL 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. * The installation process has changed starting at version 1.0.11.
  2. * All commands and directories/ are assumed to be located/ran in the wraith root dir.
  3. 1. Pack settings
  4. 2. Compiling
  5. 3. Making bots
  6. Step 1: Pack settings
  7. The files listed here are all located in pack/, and will need to be saved for future compiles.
  8. If you have pack.cff place it in pack/
  9. pack.cfg(.sample):
  10. Simply edit it and change accordingly
  11. Rename to pack.cfg when completed and make sure it is in pack/
  12. Step 2: Compiling
  13. For leaf build: ./build leaf
  14. For hub build: ./build hub
  15. To build both: ./build all
  16. To compile a debug version of the pack, add -d in as a option before the type.
  17. ie, ./build -d leaf
  18. During the compile process many warnings may appear on screen, ignore them. Only report ERRORS please.
  19. After the compile process is finished, the binaries will be placed in wraith.OS.version.tgz.
  20. The OS and version are dynamic depending on the pack build, type 'ls' to find exact name.
  21. Step 3: Making bots
  22. NOTE: conf files from versions older than 1.0.11 still work, but improvements have been made.
  23. read over doc/conf.example.
  24. This file can be made by the bot binary with ./binary -g filename
  25. Edit the conf (conf.example or the generated one, doesnt matter)
  26. For leaf bots, encrypt the conf as '~/.ssh/.known_hosts'
  27. For hub bots, encrypt the conf as 'conf'
  28. Thie is done by: ./binary -e infile outfile
  29. tar -czvf somebot.tgz .known_hosts binary
  30. (or for hub): tar -czvf somehub.tgz conf binary
  31. then upload somebot.tgz to whatever shell..
  32. LEAF:
  33. untar, mkdir ~/.ssh;mv .known_hosts ~/.ssh/.known_hosts
  34. then just run the leaf binary, it will move itself to: ~/.sshrc
  35. HUB:
  36. untar, ./binary
  37. This is assuming the conf is already encrypted as 'conf', if not, move it to 'conf'.
  38. The binary can be named ANYTHING, just as long as the encrypted conf is known as 'conf' in the same dir