v1.3.3

CVE-2020-7720 vuln with update of node-forge from 0.9.1 -> 0.10.0

v1.3.2

Important security update: Bump node-fetch from 2.6.0 to 2.6.1

v1.3.1

Upgrading

To upgrade to v1.3.0, do the following:

1. Enter the root account: sudo su
2. Copy, paste, and execute the following code in your terminal:

systemctl stop bulletbot.service; cd /home/bulletbot; mkdir temp/; mv out/bot-config.json temp; rm -rf LICENSE  README.md  crashProof.time  installers  linux-master-installer.sh  node_modules  out  package-lock.json  package.json  tsconfig.json; wget https://raw.githubusercontent.com/CodeBullet-Community/BulletBot/release/linux-master-installer.sh; bash linux-master-installer.sh; mv temp/bot-config.json src; rm -rf temp

3. When prompted by a menu telling you to install prerequisites for BulletBot, choose option 3 then press enter
4. Wait for Node.js 14.x to finish installing
5. Exit the script using option 7
6. Execute the master installer once more: bash /home/bulletbot/linux-master-installer.sh
7. Choose option 6 to compile the code
8. Wait for the code to compile
9. Resolve any problems that may be displayed during the compilation time
10. Start BulletBot in any mode you'd like
11. Make sure that BulletBot successfully starts up

Changes:

• BulletBot now uses node.js 14 instead of 13
• Installers download and manage BulletBot's code much more cleanly
• Installers will now download the newest BulletBot Updates from the release branch, instead of downloading zip files in the release
• Installer doesn't provide the option to create
• Bump bl from 2.2.0 to 2.2.1
• Update BullteBot Documentation

Fixes:

• Several installer bug fixes

Other:

• ETC.

Patch v1.2.18

Fixes

• Fixed constant error throwing when saving to the crashProof file

Release v1.2.17

Additions

• Mute persistence was added

Changes

• Capitalized all command descriptions

Fixes

• Fixed wrong usage of Let's

IMPORTANT

Some of the syntax used in this version requires the use of Node.js 14. You will need to install nodejs 14 for BulletBot to work.

Release v1.2.15

Summary

• In DMs, only bot masters now have the bot master rank (#111)
• Help command and help embed now work correctly in DMs
• Warn without reason will reply with the appropriate error message (#112)
• The confirmation reply on mod commands when the reason has formatting in it will no longer be incorrectly formatted (#108)
• Megalog now correctly says category instead of channel for category channels (#109)
• Fixed typos

Release v1.2.14 - Hot fix

Summary

This is a hotfix to resolve a problem with the installers where if bullet-mongo-start.local exists and BulletBot was updated, the file would not be moved before the current code in /home/bulletbot was archived. This means that after BulletBot was updated/downloaded, bullet-mongo-start.local would not be placed back to where it belonged.

Release v1.2.13

Summary

This update comes only with changes to the installers. In this update, we have created and now require users to follow a bash script coding style. On top of this, the installers now handle the downloading and updating of BulletBot much more efficiently.

Updating to v1.2.13

For this update, and hopefully, for the last time, you will need to place the code below into a file called pre-update.sh and executing it via sudo bash pre-update.sh.

#!/bin/bash

me=$(basename "$0")

cd "$(dirname "$0")"
echo "Removing sub-master installers..."
rm installers/Debian-Ubuntu/debian-ubuntu-installer.sh
rm installers/CentOS-RHEL/centos-rhel-installer.sh
rm "$me" # This automatically deletes the script, that way you don't forget to do it yourself
echo "Done..."

After executing the pre-update.sh (which will delete itself after doing what it needs to do), execute the master installer, and use option one to update/download the newest release.

Changes

• The installers now follow the new bash script style guide described in CONTRIBUTING.md.
• When downloading/updating BulletBot, instead of completely overwriting the files already in /home/bulletbot, the installers will archive/move all of them to a directory inside Old_BulletBot, then download the newest release.

BulletBot v1.2.13-beta Pre-release

Installer changes only

BulletBot v1.2.11 (Re-release #2)

Summary

This update comes with several bug fixes as well as a massive addition and some changes to the installers.

Updating to v1.2.11

In this update, there are a few files that can be removed, due to them being renamed and such. To make the process easy for you, I've written the code below to take care of that. Before updating to the new release, place the code below into a file named pre-update.sh and then execute that script with sudo privilege. You can do this after already updating to the new release, but it is recommended to do it before, just to reduce the possibility of running into errors.

#!/bin/bash

me=$(basename "$0")

cd "$(dirname "$0")"
echo "Stopping services bulletbot.service and bullet-mongo-start.service..."
systemctl stop bulletbot
systemctl stop bullet-monogo-start
echo "Removing directory 'autorestart'..."
rm -r /home/bulletbot/installers/Linux_Universal/autorestart
echo "Removing file 'run-in-background-autorestart.sh'..."
rm /home/bulletbot/installers/Linux_Universal/bb-start-modes/run-in-background-autorestart.sh
echo "Removing 'bullet-mongo-start.sh'..."
rm /home/bulletbot/bullet-mongo-start.sh
echo "Removing services bulletbot.service and bullet-mongo-start.service..."
rm /lib/systemd/system/bulletbot.service
rm /lib/systemd/system/bullet-mongo-start.service
echo "Reloading systemd daemons..."
systemctl daemon-reload
echo "Removing 'casedelete.js'..."
rm /home/bulletbot/out/commands/Moderation/casedelete.js
rm "$me" # This automatically deletes the script, that way you don't forget to do it yourself
echo "Done"

After running the code above, you can use the master installer to download the new version of BulletBot. Though due to an annoying update foresight, after running the update option once, you will have to exit then re-execute the master installer. The foresight prevents any changes to the master installer from being loaded into memory along with the rest of the installers, right after updating/downloading the newest release. This has been fixed in the new version.

Bug Fixes

BulletBot Bug Fixes:

• An issue preventing the ability to ban users who have already left the server has been fixed. (#75)
• Having BulletBot message itself (such as when you ?!warn the bot) would cause an error. (#59)
• Fixed the bug making it impossible to use case list with a userID. (#59)

Installer Bug Fixes:

• Small bug fixes, but nothing too major

Changes

BulletBot Changes:

• casedelete has been merged with case, which means that cases can now be deleted using ?!case delete [case #]. (#59)

Installer Changes:

• The installers now provide the option to stop BulletBot. (#34)
• When setting up BulletBot's config file, the callback.URL inside of bot-config.json, automatically gets filled in with the system's IP Address. (#53)
• BulletBot's auto-restart run mode now has the ability to send a status report on BulletBot's startup, via postfix. (#35)

All of the installer changes listed below are from (#62)

• All the services used by/for BulletBot now log events to /var/log/syslog and have syslog identifies:
• Syslog Identifiers:
  • bullet-mongo-start.service: bullet-mongo-start
  • bulletbot.service: bulletbot
• bulletbot.service is created after the master installer is executed, instead of waiting until a run mode is chosen.
• bullet-mongo-start.service is created when BulletBot is downloaded to your system or when the run mode that requires it is run.
• When switching from one run mode to another, the service and bash files (bullet-mongo-start.servce and bullet-mongo-start.sh) are not removed. Instead, bullet-mongo-start.sh stays in its original location (/home/bulletbot/installers/Linux_Universal/auto-restart/bullet-mongo-start.sh) and bullet-mongo-start.service is either enabled or disabled.
• When the installers display bulletbot.service's startup logs, instead of only displaying the last 40-60 lines of logged events, all events for that specific startup period are displayed.
• bullet-mongo-start.sh no longer attempts to start mongod.service or bulletbot.service more than once
• Renamed a few files and directories.
• Completely revamped the coding/commenting style.