summaryrefslogtreecommitdiff
path: root/bitlbee/bitlbee.conf
blob: 394cae4211946d931db73bfae80282660d16583f (plain)
    1 ## BitlBee default configuration file
    2 ##
    3 ## Comments are marked like this. The rest of the file is INI-style. The
    4 ## comments should tell you enough about what all settings mean.
    5 ##
    6 
    7 [settings]
    8 
    9 ## RunMode:
   10 ##
   11 ##  Inetd -- Run from inetd (default)
   12 ##  Daemon -- Run as a stand-alone daemon, serving all users from one process.
   13 ##    This saves memory if there are more users, the downside is that when one
   14 ##    user hits a crash-bug, all other users will also lose their connection.
   15 ##  ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate
   16 ##    child processes. This should be pretty safe and reliable to use instead
   17 ##    of inetd mode.
   18 ##
   19 RunMode = Daemon
   20 
   21 ## User:
   22 ## 
   23 ## If BitlBee is started by root as a daemon, it can drop root privileges,
   24 ## and change to the specified user.
   25 ##
   26 # User = bitlbee
   27 
   28 ## DaemonPort/DaemonInterface:
   29 ##
   30 ## For daemon mode, you can specify on what interface and port the daemon
   31 ## should be listening for connections.
   32 ##
   33 DaemonInterface = 127.0.0.1
   34 # DaemonPort = 6667
   35 
   36 ## ClientInterface:
   37 ##
   38 ## If for any reason, you want BitlBee to use a specific address/interface
   39 ## for outgoing traffic (IM connections, HTTP(S), etc.), set it here.
   40 ##
   41 # ClientInterface = 0.0.0.0
   42 
   43 ## AuthMode
   44 ##
   45 ##  Open -- Accept connections from anyone, use NickServ for user authentication.
   46 ##    (default)
   47 ##  Closed -- Require authorization (using the PASS command during login) before
   48 ##    allowing the user to connect at all.
   49 ##  Registered -- Only allow registered users to use this server; this disables
   50 ##    the register- and the account command until the user identifies itself.
   51 ##
   52 # AuthMode = Open
   53 
   54 ## AuthPassword
   55 ##
   56 ## Password the user should enter when logging into a closed BitlBee server.
   57 ## You can also have a BitlBee-style MD5 hash here. Format: "md5:", followed
   58 ## by a hash as generated by "bitlbee -x hash <password>".
   59 ##
   60 # AuthPassword = ItllBeBitlBee   ## Heh.. Our slogan. ;-)
   61 ## or
   62 # AuthPassword = md5:gzkK0Ox/1xh+1XTsQjXxBJ571Vgl
   63 
   64 ## OperPassword
   65 ##
   66 ## Password that unlocks access to special operator commands.
   67 ##
   68 # OperPassword = ChangeMe!
   69 ## or
   70 # OperPassword = md5:I0mnZbn1t4R731zzRdDN2/pK7lRX
   71 
   72 ## HostName
   73 ##
   74 ## Normally, BitlBee gets a hostname using getsockname(). If you have a nicer
   75 ## alias for your BitlBee daemon, you can set it here and BitlBee will identify
   76 ## itself with that name instead.
   77 ##
   78 # HostName = localhost
   79 
   80 ## MotdFile
   81 ##
   82 ## Specify an alternative MOTD (Message Of The Day) file. Default value depends
   83 ## on the --etcdir argument to configure.
   84 ##
   85 # MotdFile = /etc/bitlbee/motd.txt
   86 
   87 ## ConfigDir
   88 ##
   89 ## Specify an alternative directory to store all the per-user configuration
   90 ## files. (.nicks/.accounts)
   91 ##
   92 # ConfigDir = /var/lib/bitlbee
   93 
   94 ## Ping settings
   95 ##
   96 ## BitlBee can send PING requests to the client to check whether it's still
   97 ## alive. This is not very useful on local servers, but it does make sense
   98 ## when most clients connect to the server over a real network interface.
   99 ## (Public servers) Pinging the client will make sure lost clients are
  100 ## detected and cleaned up sooner.
  101 ##
  102 ## PING requests are sent every PingInterval seconds. If no PONG reply has
  103 ## been received for PingTimeOut seconds, BitlBee aborts the connection.
  104 ##
  105 ## To disable the pinging, set at least one of these to 0.
  106 ##
  107 # PingInterval = 180
  108 # PingTimeOut = 300
  109 
  110 ## Using proxy servers for outgoing connections
  111 ##
  112 ## If you're running BitlBee on a host which is behind a restrictive firewall
  113 ## and a proxy server, you can tell BitlBee to use that proxy server here.
  114 ## The setting has to be a URL, formatted like one of these examples:
  115 ##
  116 ## (Obviously, the username and password are optional)
  117 ##
  118 # Proxy = http://john:doe@proxy.localnet.com:8080
  119 # Proxy = socks4://socksproxy.localnet.com
  120 # Proxy = socks5://socksproxy.localnet.com
  121 
  122 ## Protocols offered by bitlbee
  123 ## 
  124 ## As recompiling may be quite unpractical for some people, this option
  125 ## allows to remove the support of protocol, even if compiled in. If
  126 ## nothing is given, there are no restrictions.
  127 ## 
  128 # Protocols = jabber yahoo
  129 
  130 ## Trusted CAs
  131 ##
  132 ## Path to a file containing a list of trusted certificate authorities used in
  133 ## the verification of server certificates.
  134 ##
  135 ## Uncomment this and make sure the file actually exists and contains all
  136 ## certificate authorities you're willing to accept (default value should
  137 ## work on at least Debian/Ubuntu systems with the "ca-certificates" package
  138 ## installed). As long as the line is commented out, SSL certificate
  139 ## verification is completely disabled.
  140 ##
  141 ## The location of this file may be different on other distros/OSes. For
  142 ## example, try /etc/ssl/ca-bundle.pem on OpenSUSE.
  143 ##
  144 # CAfile = /etc/ssl/certs/ca-certificates.crt
  145 
  146 [defaults]
  147 
  148 ## Here you can override the defaults for some per-user settings. Users are
  149 ## still able to override your defaults, so this is not a way to restrict
  150 ## your users...
  151 
  152 ## To enable private mode by default, for example:
  153 
  154 ## private = 1

Generated by cgit