INSTALL 2.8 KB

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