diff --git a/README.html b/README.html index 4d7dfc4..6736995 100644 --- a/README.html +++ b/README.html @@ -18,7 +18,7 @@
Contributions by JuanPotato, BigNerd95, TiagoDanin, and iicc1.
Released to the public domain wherever applicable. Elsewhere, consider it released under the WTFPLv2.
Depends on tmux. Uses JSON.sh.
+Uses JSON.sh, but no more TMUX.
Even bashbot is written in bash, it depends on commands typically availible in a Unix/Linux Environment. More concret on the common commands provided by coreutils, busybox or toybox, see Developer Notes
Bashbot Documentation and Downloads are availible on www.github.com
At the beginning bashbot was simply the file bashbot.sh
I can copy everywhere and run the bot. Now we have ‘commands.sh’, ‘mycommands.sh’, ’modules/*.sh’ and much more.
Hey no Problem, if you are finished with your cool bot simply run dev/make-standalone.sh
to create a stripped down Version containing only ‘bashbot.sh’ and ‘commands.sh’! For more information see Create a stripped down Version of your Bot
Running a Telegram Bot means it is connected to the public and you never know whats send to your Bot.
Bash scripts in general are not designed to be bullet proof, so consider this Bot as a proof of concept. Bash programmers often struggle with ‘quoting hell’ and globbing, see Implications of wrong quoting
@@ -94,6 +91,7 @@Your Bot configuration must no be readable from other users. Everyone who can read your Bots token can act as your Bot and has access to all chats your Bot is in!
Everyone with read access to your Bot files can extract your Bots data. Especially your Bot Token in token
must be protected against other users. No one exept you must have write access to the Bot files. The Bot must be restricted to have write access to count
and tmp-bot-bash
only, all other files must be write protected.
To set access rights for your bashbot installation to a reasonable default run sudo ./bashbot.sh init
after every update or change to your installation directory.
Bashbot is not more (in)secure as any other Bot written in any other language, we have done our best to make it as secure as possible. But YOU are responsible for the bot commands you wrote and you should know about the risks …
At the beginning bashbot was simply the file bashbot.sh
you can copy everywhere and run the bot. Now we have ‘commands.sh’, ‘mycommands.sh’, ’modules/*.sh’ and much more.
Hey no Problem, if you are finished with your cool bot run dev/make-standalone.sh
to create a stripped down Version of your bot containing only ‘bashbot.sh’ and ‘commands.sh’! For more information see Create a stripped down Version of your Bot
@Gnadelwartz
If you feel that there’s something missing or if you found a bug, feel free to submit a pull request!
-