Updating
Updating is very simple and straight forward.
You should always have a backup client opped in all of your channels just in case the upgrade goes bad.
Binary preparations
- See also GettingStarted#MakingBinaries
- Download the latest source code and Compile or simply download pre-compiled binaries for each operating system you plan to use. (Linux/FreeBSD)
- Initialize the new binary with your PackConfig using the same salts as you originally did.
Updating
- If updating from a version before 1.2.16: Kill off and remove crontab of all althubs. After all leaf bots are updated, you can start the althubs back up and let them update as well.
- Pick a hub that should distribute the binaries to the botnet. (high bandwidth allowed)
Shell operations for hub
- Eg. If you keep your hub in ~username/hub/
- Change to your ~username/hub/ directory before you do any of the following.
- Do not skip any of these steps; skipping steps leads to confusion later.
- Login to the shell for the hub and change into the hub's directory.
- mkdir bins/ (only needed if not already there)
- cd bins/
- wget all of your tar.gz packages that you created above.
- Untar the packages. (tar -zxf package.tar.gz)
- rm -f *.tar.gz
- Copy the unzipped binary to ../newhub cp wraith.Linux-1.2.10 ../newhub
- Nothing else should be done. Do not rename your hub or recreate it. Stop here and move on to the next section.
Example directory structure
Your hub directory should look like this:
$ ls -al total 1384 drwx------ 5 bryan bryan 512 May 22 23:37 ./ drwx-----x 17 bryan bryan 1024 May 19 03:52 ../ drwx------ 2 bryan bryan 512 May 22 00:00 .../ -rwx------ 1 bryan bryan 193504 May 22 23:21 .u* drwxr-xr-x 2 bryan bryan 512 May 19 03:51 bins/ -rwx------ 1 bryan bryan 1187724 May 19 03:51 hub* -rwx------ 1 bryan bryan 1187724 May 19 03:51 newhub* drwx------ 2 bryan bryan 512 May 22 23:37 tmp/ $ ls -al bins/ total 2628 drwxr-xr-x 2 bryan bryan 512 May 19 03:51 ./ drwx------ 5 bryan bryan 512 May 22 23:37 ../ -rwx------ 1 bryan bryan 1187724 May 19 03:48 wraith.FreeBSD-1.2.10-rc1* -rwx------ 1 bryan bryan 1447696 May 19 03:49 wraith.Linux-1.2.10-rc1*If it doesn't look like this, start over again. Extra .tar.gz files or old binaries can be ignored, but are not necessary. Just don't touch the current hub binary.
Botnet operations on hub
- Enable cleartext linking in case the encryption algorithm has changed.
.set link_cleartext 1
- Disable cookies for all channels.
.chanset * +fastop
- Tell the main hub to start sharing out the new binaries
.chattr THEHUB +u
- Update the hub itself with the name of the NEW-BINARY you created above.
.update NEW-BINARY
- The hub will now restart; Telnet back in.
- Grab a beer, some guacamole and chips.
- Check status of update with .netver
- Once the entire update is done be sure to disable the cleartext botlink
.set link_cleartext 0
- Re-enable cookies for selected channels.
.chanset * -fastop
Notes on updating
- One bot is sent the binary at a time.
- The first bot listed in each binary will download the new binary, and then will restart its child bots.
- After a few minutes, that bot will restart itself.
- Bots will cycle channels as they restart. This cycling will be eliminated in 1.3 most likely.
