From d25f6fcbe8e291dd858bf734fa85cde176dc8415 Mon Sep 17 00:00:00 2001 From: Wilmer van der Gaast Date: Mon, 26 Dec 2005 15:02:47 +0100 Subject: Added OperPassword and RunMode = ForkDaemon settings. Oper stuff is *INSECURE* because users can just do /mode +o to become operator. --- bitlbee.conf | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'bitlbee.conf') diff --git a/bitlbee.conf b/bitlbee.conf index b0de328d..919cee9d 100644 --- a/bitlbee.conf +++ b/bitlbee.conf @@ -13,6 +13,9 @@ ## stable enough to serve lots of users from one process. Because of this ## and other reasons, the use of daemon-mode is *STRONGLY* discouraged, ## don't even *think* of reporting bugs when you use this. +## ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate +## child processes. This should be pretty safe and reliable to use instead +## of inetd mode. ## # RunMode = Inetd @@ -41,6 +44,12 @@ ## # AuthPassword = ItllBeBitlBee ## Heh.. Our slogan. ;-) +## OperPassword +## +## Password that unlocks access to special operator commands. +## +# OperPassword = ChangeMe! + ## HostName ## ## Normally, BitlBee gets a hostname using getsockname(). If you have a nicer -- cgit v1.2.3