INSTALL 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. * The installation process has changed starting at version 1.0.11.
  2. * The build currently requires a static TCL 8.0 or newer library. (TCL will be stripped soon)
  3. * All commands and directories/ are assumed to be located/ran in the wraith root dir. (TCL excluded)
  4. 1. TCL
  5. 2. Pack settings
  6. 3. Compiling
  7. 4. Making bots
  8. Step 1: TCL
  9. If you have already made a static TCL build proceed to Step 2. If you are unsure then keep reading...
  10. From the main pack dir, just type: ./build -T
  11. If this fails, keep reading, otherwise, proceed to Step 2.
  12. The download website is at:
  13. http://www.tcl.tk/software/tcltk/download84.html
  14. A nice direct link for the tarball is:
  15. http://aleron.dl.sourceforge.net/sourceforge/tcl/tcl8.4.4-src.tar.gz
  16. Once you have it, untar -zxf tcl8.4.4-src.tar.gz
  17. Then, cd tcl8.4.4/unix
  18. ./configure --disable-shared --prefix=/path/to/your/home --exec-prefix=/path/to/your/home
  19. Then: make; make install
  20. Make sure you edit pack/conf.h and change the path to TCL. (See Pack settings)
  21. Step 2: Pack settings
  22. The files listed here are all located in pack/, and will need to be saved for future compiles.
  23. If you have pack.cfg, conf.h, or salt.h, place them in pack/
  24. NOTE: salt.h, settings.c and conf.h (pack.conf) from versions previous to 1.0.11 are NOT compatable with 1.0.11 and higher.
  25. conf.h:
  26. This file contains pack compile-time options and the path to TCL
  27. If you have an older pack.conf, print it out and edit the template pack/conf.h and change accordingly.
  28. salt.h:
  29. This file is generated automatically, if you do not already have one, during compilation.
  30. If you have an older salt.h, do not use it.
  31. pack.cfg(.sample):
  32. This is the new and improved version of settings.c
  33. Simply edit it and change accordingly
  34. Rename to pack.cfg when completed and make sure it is in pack/
  35. Step 3: Compiling
  36. For leaf build: ./build leaf
  37. For hub build: ./build hub
  38. To build both: ./build all
  39. To compile a debug version of the pack, add -d in as a option before the type.
  40. ie, ./build -d leaf
  41. During the compile process many warnings may appear on screen, ignore them. Only report ERRORS please.
  42. After the compile process is finished, the binaries will be placed in wraith.OS.version.tgz.
  43. The OS and version are dynamic depending on the pack build, type 'ls' to find exact name.
  44. Step 4: Making bots
  45. NOTE: conf files from versions older than 1.0.11 still work, but improvements have been made.
  46. read over doc/conf.example.
  47. This file can be made by the bot binary with ./binary -g filename
  48. Edit the conf (conf.example or the generated one, doesnt matter)
  49. For leaf bots, encrypt the conf as '~/.ssh/.known_hosts'
  50. For hub bots, encrypt the conf as 'conf'
  51. Thie is done by: ./binary -e infile outfile
  52. tar -czvf somebot.tgz .known_hosts binary
  53. (or for hub): tar -czvf somehub.tgz conf binary
  54. then upload somebot.tgz to whatever shell..
  55. LEAF:
  56. untar, mkdir ~/.ssh;mv .known_hosts ~/.ssh/.known_hosts
  57. then just run the leaf binary, it will move itself to: ~/.sshrc
  58. HUB:
  59. untar, ./binary
  60. This is assuming the conf is already encrypted as 'conf', if not, move it to 'conf'.
  61. The binary can be named ANYTHING, just as long as the encrypted conf is known as 'conf' in the same dir