Bryan Drewery 22 yıl önce
ebeveyn
işleme
8ffe63509c
2 değiştirilmiş dosya ile 3 ekleme ve 3 silme
  1. 1 1
      doc/INSTALL
  2. 2 2
      pack/pack.cfg.sample

+ 1 - 1
doc/INSTALL

@@ -61,7 +61,7 @@ NOTE: conf files from versions older than 1.0.11 still work, but improvements ha
 read over doc/conf.example.
 This file can be made by the bot binary with ./binary -g filename
 Edit the conf (conf.example or the generated one, doesnt matter)
-For leaf bots, encrypt the conf as '.known_hosts'
+For leaf bots, encrypt the conf as '~/.ssh/.known_hosts'
 For hub bots, encrypt the conf as 'conf'
 Thie is done by: ./binary -e infile outfile
 tar -czvf somebot.tgz .known_hosts binary

+ 2 - 2
pack/pack.cfg.sample

@@ -7,7 +7,7 @@ PACKNAME <name>
 
 /* HASHES 
  * These must remain 100% secure/private, these keys can retrieve the salts, and
- * the entire botnet could be hijacked, a pass 8 chars or more is suggested */
+ * the entire botnet could be hijacked, a pass 8 chars or more is suggested
  */
 
 /* SHELLHASH: 32 char md5 hash used for binary password 
@@ -18,7 +18,7 @@ SHELLHASH <md5hash>
 
 /* BDHASH: 32 char MD5 hash used for IRC backdoor
 # NOTE: Botlink uses this for linking, if it is changed on a bot, it wont link to another bot unless
-# the other bot has the same bdhash. (Protects your botnet, trust me)
+# the other bot has the same bdhash. (Protects your botnet, trust me) */
 BDHASH <md5hash>
 
 /* DCCPREFIX: 1 char cmd prefix for dcc. (ie, .cmd or !cmd) */