|
| 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 = Inetd |
| 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 #0.0.0.0 |
| 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 | +## AuthBackend |
| 55 | +## |
| 56 | +## By default, the authentication data for a user is stored in the storage |
| 57 | +## backend. If you want to authenticate against another authentication system |
| 58 | +## (e.g. ldap), you can specify that here. |
| 59 | +## |
| 60 | +## Beware that this disables password changes and causes passwords for the |
| 61 | +## accounts people create to be stored in plain text instead of encrypted with |
| 62 | +## their bitlbee password. |
| 63 | +## |
| 64 | +## Currently available backends: |
| 65 | +## |
| 66 | +## - storage (internal storage) |
| 67 | +## - pam (Linux PAM authentication) |
| 68 | +## - ldap (LDAP server configured in the openldap settings) |
| 69 | +# |
| 70 | +# AuthBackend = storage |
| 71 | +# |
| 72 | + |
| 73 | +## AuthPassword |
| 74 | +## |
| 75 | +## Password the user should enter when logging into a closed BitlBee server. |
| 76 | +## You can also have a BitlBee-style MD5 hash here. Format: "md5:", followed |
| 77 | +## by a hash as generated by "bitlbee -x hash <password>". |
| 78 | +## |
| 79 | +# AuthPassword = ItllBeBitlBee ## Heh.. Our slogan. ;-) |
| 80 | +## or |
| 81 | +# AuthPassword = md5:gzkK0Ox/1xh+1XTsQjXxBJ571Vgl |
| 82 | + |
| 83 | +## OperPassword |
| 84 | +## |
| 85 | +## Password that unlocks access to special operator commands. |
| 86 | +## |
| 87 | +# OperPassword = ChangeMe! |
| 88 | +## or |
| 89 | +# OperPassword = md5:I0mnZbn1t4R731zzRdDN2/pK7lRX |
| 90 | + |
| 91 | +## AllowAccountAdd |
| 92 | +## |
| 93 | +## Whether to allow registered and identified users to add new accounts using |
| 94 | +## 'account add' |
| 95 | +## |
| 96 | +# AllowAccountAdd 1 |
| 97 | + |
| 98 | +## HostName |
| 99 | +## |
| 100 | +## Normally, BitlBee gets a hostname using getsockname(). If you have a nicer |
| 101 | +## alias for your BitlBee daemon, you can set it here and BitlBee will identify |
| 102 | +## itself with that name instead. |
| 103 | +## |
| 104 | +# HostName = localhost |
| 105 | + |
| 106 | +## MotdFile |
| 107 | +## |
| 108 | +## Specify an alternative MOTD (Message Of The Day) file. Default value depends |
| 109 | +## on the --etcdir argument to configure. |
| 110 | +## |
| 111 | +# MotdFile = /etc/bitlbee/motd.txt |
| 112 | + |
| 113 | +## ConfigDir |
| 114 | +## |
| 115 | +## Specify an alternative directory to store all the per-user configuration |
| 116 | +## files. (.nicks/.accounts) |
| 117 | +## |
| 118 | +# ConfigDir = /var/lib/bitlbee |
| 119 | + |
| 120 | +## Ping settings |
| 121 | +## |
| 122 | +## BitlBee can send PING requests to the client to check whether it's still |
| 123 | +## alive. This is not very useful on local servers, but it does make sense |
| 124 | +## when most clients connect to the server over a real network interface. |
| 125 | +## (Public servers) Pinging the client will make sure lost clients are |
| 126 | +## detected and cleaned up sooner. |
| 127 | +## |
| 128 | +## PING requests are sent every PingInterval seconds. If no PONG reply has |
| 129 | +## been received for PingTimeOut seconds, BitlBee aborts the connection. |
| 130 | +## |
| 131 | +## To disable the pinging, set at least one of these to 0. |
| 132 | +## |
| 133 | +# PingInterval = 180 |
| 134 | +# PingTimeOut = 300 |
| 135 | + |
| 136 | +## Using proxy servers for outgoing connections |
| 137 | +## |
| 138 | +## If you're running BitlBee on a host which is behind a restrictive firewall |
| 139 | +## and a proxy server, you can tell BitlBee to use that proxy server here. |
| 140 | +## The setting has to be a URL, formatted like one of these examples: |
| 141 | +## |
| 142 | +## (Obviously, the username and password are optional) |
| 143 | +## |
| 144 | +# Proxy = http://john: [email protected]:8080 |
| 145 | +# Proxy = socks4://socksproxy.localnet.com |
| 146 | +# Proxy = socks5://socksproxy.localnet.com |
| 147 | + |
| 148 | +## Protocols offered by bitlbee |
| 149 | +## |
| 150 | +## As recompiling may be quite unpractical for some people, this option |
| 151 | +## allows to remove the support of protocol, even if compiled in. If |
| 152 | +## nothing is given, there are no restrictions. |
| 153 | +## |
| 154 | +# Protocols = jabber yahoo |
| 155 | + |
| 156 | +## Trusted CAs |
| 157 | +## |
| 158 | +## Path to a file containing a list of trusted certificate authorities used in |
| 159 | +## the verification of server certificates. |
| 160 | +## |
| 161 | +## Uncomment this and make sure the file actually exists and contains all |
| 162 | +## certificate authorities you're willing to accept (default value should |
| 163 | +## work on at least Debian/Ubuntu systems with the "ca-certificates" package |
| 164 | +## installed). As long as the line is commented out, SSL certificate |
| 165 | +## verification is completely disabled. |
| 166 | +## |
| 167 | +## The location of this file may be different on other distros/OSes. For |
| 168 | +## example, try /etc/ssl/ca-bundle.pem on OpenSUSE. |
| 169 | +## |
| 170 | +# CAfile = /etc/ssl/certs/ca-certificates.crt |
| 171 | + |
| 172 | +[defaults] |
| 173 | + |
| 174 | +## Here you can override the defaults for some per-user settings. Users are |
| 175 | +## still able to override your defaults, so this is not a way to restrict |
| 176 | +## your users... |
| 177 | + |
| 178 | +## To enable private mode by default, for example: |
| 179 | + |
| 180 | +## private = 1 |
0 commit comments