2005-10-18 10:00:55 +02:00
|
|
|
.TH BIP 1 "10 October 2005"
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.SH NAME
|
|
|
|
|
|
|
|
bip.conf \- Configuration file for BIP IRC Proxy
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
|
|
|
A BIP configuration file consists of a list of variable affectations or
|
|
|
|
sections. It contains the global options, networks definitions, users
|
|
|
|
configuration, users connections declarations. Each section is described in
|
|
|
|
this manpage.
|
|
|
|
|
|
|
|
The bip.conf skeleton should be something like this :
|
|
|
|
|
2005-10-11 18:59:45 +02:00
|
|
|
.nf
|
2005-10-10 23:56:39 +02:00
|
|
|
option1 = value;
|
|
|
|
option2 = value;
|
|
|
|
...
|
|
|
|
|
|
|
|
network {
|
|
|
|
net_opt = value;
|
|
|
|
...
|
|
|
|
server { ... };
|
|
|
|
server { ... };
|
|
|
|
};
|
|
|
|
...
|
|
|
|
|
|
|
|
user {
|
|
|
|
user_opt = value;
|
|
|
|
...
|
|
|
|
connection {
|
|
|
|
conn_opt = value;
|
|
|
|
...
|
|
|
|
channel { ... };
|
|
|
|
};
|
|
|
|
connection {
|
|
|
|
conn_opt = value;
|
|
|
|
...
|
|
|
|
channel { ... };
|
|
|
|
channel { ... };
|
|
|
|
...
|
|
|
|
};
|
|
|
|
};
|
2005-10-11 18:59:45 +02:00
|
|
|
.fi
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.SH SYNTAX RULES
|
|
|
|
|
|
|
|
The syntax is quite simple :
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- everything after the \fB#\fP character is ignored (comments)
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- each variable affectation must be finished with a \fB;\fP
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- each section { } must be finished with a \fB;\fP
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
|
2005-10-11 10:49:27 +02:00
|
|
|
If you use vim you will probably want to use vim with the provided
|
|
|
|
\fBbip.vim\fP syntax file to avoid common syntax and lexical mistakes. You can
|
|
|
|
also find an example configuration file along with BIP.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.SH GLOBAL OPTIONS
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBbacklog\fP (default: \fBtrue\fP)
|
|
|
|
Enable or disable the whole backlog system, which allows clients to see a
|
|
|
|
log replay upon connection.
|
|
|
|
|
2007-12-16 17:28:01 +01:00
|
|
|
.TP
|
|
|
|
\fBbacklog_always\fP (default: \fBfalse\fP)
|
|
|
|
If true, clients will always receive \fBbacklog_lines\fP log lines, even if
|
|
|
|
they were already sent before. That means :
|
|
|
|
If \fBbacklog_always\fP is false, backlog will be reset whenever there
|
|
|
|
is no more client connected to a network. Else backlog will not be reset.
|
|
|
|
This option should of course not be enabled if \fBbacklog_lines\fP is 0 !
|
|
|
|
If you still want to do so, don't forget to /BIP BLRESET sometimes.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
|
|
|
\fBbacklog_lines\fP (default: \fB10\fP)
|
|
|
|
If set to 0, BIP will replay all the logs since last client disconnect. Else,
|
|
|
|
it'll replay exactly \fBbacklog_lines\fP lines on each channel and privates.
|
|
|
|
Be aware that BIP will replay \fBbacklog_lines\fP lines of all privates, even
|
|
|
|
if there are more. For example if Coyote told you 12 lines and then RoadRunner
|
|
|
|
6, you'll only have a replay of the 6 RoadRunner's lines and the last 4 of
|
|
|
|
Coyote's.
|
|
|
|
|
2007-01-12 19:49:14 +01:00
|
|
|
\fBbacklog_no_timestamp\fP (default: \fBfalse\fP)
|
|
|
|
If true, backlogged line won't include the timestamp.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
2007-02-17 11:54:21 +01:00
|
|
|
\fBbacklog_reset_on_talk\fP (default: \fBfalse\fP)
|
2007-12-16 17:28:01 +01:00
|
|
|
When true, backlog will be reset upon client talk (channel/private message or
|
|
|
|
action). It means that next time you log to your bip session, the backlogging
|
|
|
|
will start at the time right after your last words on that specific network.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
2006-11-15 22:13:51 +01:00
|
|
|
.TP
|
2007-02-17 11:54:21 +01:00
|
|
|
\fBbacklog_msg_only\fP (default: \fBfalse\fP)
|
2006-11-15 22:13:51 +01:00
|
|
|
When true, bip will backlog only channel/private messages/notices. No topic
|
|
|
|
change, nick change, user quit/part/join will be backlogged upon connection.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
|
|
|
\fBclient_side_ssl\fP (default: \fBfalse\fP)
|
|
|
|
When true, clients will need to connect to BIP using SSL.
|
2007-12-29 01:35:11 +01:00
|
|
|
You'll also need to generate a SSL cert/key pair in <bipdir>/bip.pem (usually
|
2008-01-07 22:31:28 +01:00
|
|
|
~/.bip/bip.pem or /var/lib/bip/bip.pem) or <client_side_ssl_pem> if defined.
|
2008-01-07 19:48:04 +01:00
|
|
|
|
|
|
|
.TP
|
2008-01-07 20:42:40 +01:00
|
|
|
\fBclient_side_ssl_pem\fP (default: \fB<bipdir>/bip.pem\fP)
|
2008-01-07 19:48:04 +01:00
|
|
|
Set this to the full path of the cert/key pair bip should use to accept clients
|
|
|
|
SSL connections.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBip\fP
|
2005-10-11 10:49:27 +02:00
|
|
|
Ignored for the time beeing.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBlog\fP (default: \fBtrue\fP)
|
|
|
|
When true, the log system is enabled. Else, BIP will not write a single log
|
|
|
|
file. Backlog is then stored into memory.
|
|
|
|
|
2007-07-01 14:43:09 +02:00
|
|
|
.TP
|
|
|
|
\fBlog_system\fP (default: \fBtrue\fP)
|
|
|
|
When true, system messages such as connection errors are logged. Else, BIP will not write system logs.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
|
|
|
\fBlog_format\fP (default: \fB%u/%n/%Y-%m/%c.%d.log\fP)
|
|
|
|
Determines the log file name depending on :
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %u username (name in user { }; section)
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %n network name (name in connection { }; section)
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %c channel name
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %Y 4 digits year
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %m 2 digits month
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
\- %d 2 digits day
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBlog_level\fP (default: \fB1\fP)
|
|
|
|
Specify the verbosity of BIP from 0 (fatal errors) to 6 (huge debug output)
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBlog_root\fP (default: \fBHOME/.bip/logs\fP)
|
|
|
|
Main log directory. Sub-directories and files will be created from there
|
|
|
|
depending on \fBlog_format\fP.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBlog_sync_interval\fP (default: \fB5\fP)
|
|
|
|
Defines the delay between each logfiles sync to the disk. Must be a non null
|
|
|
|
positive integer.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBpid_file\fP (default: \fBHOME/.bip/bip.pid\fP)
|
|
|
|
Defines the file where BIP's pid will be stored. BIP checks if this file exists
|
|
|
|
and if the pid is still alive upon startup. If true, BIP refuses to start.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBport\fP (default: \fB7778\fP)
|
|
|
|
The port on which BIP should listen for clients.
|
|
|
|
|
|
|
|
.SH NETWORK SECTION
|
|
|
|
|
|
|
|
This section allows you to declare a network for use in the connection
|
|
|
|
sections. It may appear more than once in the configuration file.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBssl\fP (default: \fBfalse\fP)
|
|
|
|
If true, BIP will connect to this network using SSL only. You cannot mix
|
2005-10-11 10:49:27 +02:00
|
|
|
SSL servers and non-SSL servers in the same network section. This is by choice,
|
|
|
|
we believe it's a bad idea.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBname\fP
|
2005-10-11 10:49:27 +02:00
|
|
|
It's the network name used in the \fBconnection section\fP. Please note that
|
|
|
|
this value is not used in \fBlog_format\fP, since it uses the variable
|
|
|
|
\fBname\fP from the \fBconnection section\fP.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.SH SERVER SUB-SECTION
|
|
|
|
|
|
|
|
BIP will cycle through the server sections list when reconnecting to a network.
|
|
|
|
It may appear more than once in a network section.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBhost\fP
|
|
|
|
The server's hostname or IP address.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBport\fP (default: \fB6667\fP)
|
|
|
|
The server port to connect to.
|
|
|
|
|
|
|
|
.SH USER SECTION
|
|
|
|
|
|
|
|
This section allows you to define the users allowed to connect to BIP and their
|
|
|
|
options. It may appear more than once in the configuration file.
|
|
|
|
|
2007-09-28 13:21:05 +02:00
|
|
|
.TP
|
|
|
|
\fBadmin\fP (default: \fBfalse\fP)
|
|
|
|
If a user has admin set to true, he'll become a bip administrator, which allows
|
|
|
|
him for example to RELOAD bip from IRC or to see the user configuration.
|
|
|
|
|
2007-09-28 13:20:32 +02:00
|
|
|
.TP
|
|
|
|
\fBbip_use_notice\fP (default: \fBfalse\fP)
|
|
|
|
If \fBbip_use_notice\fP is true, bip's notifications to the clients will be
|
|
|
|
send as notices instead of private messages. For example, this setting applies
|
|
|
|
to disconnection notifications or /BIP command replies.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
|
|
|
\fBdefault_nick\fP
|
|
|
|
The default nick option for each \fBconnection section\fP where no \fBnick\fP
|
|
|
|
is defined. See \fBCONNECTION SECTION\fP for more details.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBdefault_realname\fP
|
2005-10-11 10:49:27 +02:00
|
|
|
The default realname option for each \fBconnection section\fP where no
|
|
|
|
\fBrealname\fP is defined. See \fBCONNECTION SECTION\fP for more details.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBdefault_user\fP
|
|
|
|
The default user option for each \fBconnection section\fP where no \fBuser\fP
|
|
|
|
is defined. See \fBCONNECTION SECTION\fP for more details.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBname\fP
|
2005-10-11 10:49:27 +02:00
|
|
|
The user name. It'll be used to authenticate to bip and in \fBlog_format\fP.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBpassword\fP
|
|
|
|
The password. It \fBMUST\fP be generated with \fBbimkpw\fP or it'll not work.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBssl_check_mode\fP (default: \fBnone\fP)
|
|
|
|
Tells whether BIP should check the server SSL certificate and against what.
|
|
|
|
Can be \fBnone\fP for no check at all, \fBca\fP to check if the cert is signed
|
|
|
|
by a Certificate Authority in repository, or \fBbasic\fP to check if cert
|
2007-10-29 00:24:48 +01:00
|
|
|
exists in repository. The repository is defined by \fBssl_check_store\fP. This
|
2007-10-29 00:38:42 +01:00
|
|
|
allows a "ssh-like" private key generation scheme. Note that in basic mode:
|
|
|
|
.br
|
|
|
|
- expired certificates that are in the store are considered valid.
|
|
|
|
.br
|
|
|
|
- CA-signed certificates are considered valid even if not in store.
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBssl_check_store\fP (default: \fBnot set\fP)
|
2005-10-10 23:56:39 +02:00
|
|
|
This repository is browsed by BIP when a SSL certificate or CA check is needed.
|
|
|
|
|
|
|
|
.SH CONNECTION SUB-SECTION
|
|
|
|
|
|
|
|
Each connection section associates a user to the networks he wants to connect
|
|
|
|
to. Thus, it must be declared in the user sections, and can be used more than
|
|
|
|
once.
|
|
|
|
|
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBaway_nick\fP (default: \fBnot set\fP)
|
2007-12-29 01:35:11 +01:00
|
|
|
If set, and if there are no more client attached, BIP will change nickname to
|
2005-10-10 23:56:39 +02:00
|
|
|
this \fBaway_nick\fP. Your nickname will be restored upon client connect.
|
|
|
|
|
2006-11-15 22:13:51 +01:00
|
|
|
.TP
|
|
|
|
\fBno_client_away_msg\fP (default: \fBnot set\fP)
|
|
|
|
This options allows you to set an away message. This away message will be set
|
|
|
|
when the last client disconnects, and removed when a client connects.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBfollow_nick\fP (default: \fBfalse\fP)
|
2005-10-10 23:56:39 +02:00
|
|
|
If set to true, when you change nick, BIP stores the new nickname as the new
|
|
|
|
default nickname value. Thus, if you are disconnected from the server, BIP will
|
|
|
|
restore the correct nickname.
|
|
|
|
|
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBignore_first_nick\fP (default: \fBfalse\fP)
|
2005-10-10 23:56:39 +02:00
|
|
|
If set to true, BIP will ignore the nickname sent by the client upon connect.
|
|
|
|
Further nickname changes will be processed as usual.
|
|
|
|
|
|
|
|
.TP
|
2005-10-11 18:59:45 +02:00
|
|
|
\fBnetwork\fP
|
2005-10-10 23:56:39 +02:00
|
|
|
The network name. See the \fBNETWORK SECTION\fP.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBnick\fP
|
|
|
|
BIP will send that string as your nickname upon connect. If not specified
|
|
|
|
and if \fBdefault_nickname\fP is specified in the \fBuser section\fP, BIP will
|
|
|
|
use that default nickname string.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBon_connect_send\fP
|
2006-09-20 22:30:25 +02:00
|
|
|
You can specify this field more than once. BIP will send the text as is to the
|
2005-10-10 23:56:39 +02:00
|
|
|
server. It'd be useful for a greet on connect or to send you NickServ password.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBpassword\fP
|
2005-10-11 10:49:27 +02:00
|
|
|
This is the irc server password, which is sent upon connection to the irc server
|
2005-10-10 23:56:39 +02:00
|
|
|
only.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBrealname\fP
|
|
|
|
BIP will send that string as the realname part (description in whois result)
|
|
|
|
upon connect. If not specified and if \fBdefault_realname\fP is specified in
|
|
|
|
the \fBuser section\fP, BIP will use that default realname string.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBsource_port\fP
|
|
|
|
If specified, tells BIP to connect from this port to the IRC server.
|
|
|
|
|
2007-09-26 22:18:50 +02:00
|
|
|
.TP
|
|
|
|
\fBssl_check_mode\fP (default: \fBthe user's option\fP)
|
|
|
|
See \fBssl_check_mode\fP option in User options.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.TP
|
|
|
|
\fBuser\fP
|
|
|
|
BIP will send that string as the user part (usually between ! and @ in a whois
|
|
|
|
result) upon connect. It's also used by the oidentd support (if enabled). If
|
|
|
|
not specified and if \fBdefault_user\fP is specified in the \fBuser section\fP,
|
|
|
|
BIP will use that default user string.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBvhost\fP
|
|
|
|
If specified, BIP will use \fBvhost\fP as the IP address to bind to when
|
|
|
|
connecting to the IRC server. It'll allow you to use a specific IP address
|
|
|
|
for this network when you have more than one. This options is totally useless
|
|
|
|
to people who only have one IP address.
|
|
|
|
|
|
|
|
.SH CHANNEL SUB-SUB-SECTION
|
|
|
|
|
|
|
|
This section defines the list of channels to join for a user on a particular
|
|
|
|
network. It is to be found in the connection sections and appear more than once
|
|
|
|
in a connection section.
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBname\fP
|
|
|
|
The channel name (#bip, &bip, ...).
|
|
|
|
|
|
|
|
.TP
|
|
|
|
\fBkey\fP
|
|
|
|
The channel key if needed.
|
|
|
|
|
2007-09-27 01:08:10 +02:00
|
|
|
.TP
|
|
|
|
\fBbacklog\fP (default: \fBtrue\fP)
|
|
|
|
Enable or disable backlogging of this particular channel.
|
|
|
|
Setting this to true will NOT enable the backlog system, see the User section.
|
|
|
|
|
2005-10-10 23:56:39 +02:00
|
|
|
.SH SEE ALSO
|
|
|
|
|
|
|
|
bip, bipmkpw
|
|
|
|
|
|
|
|
.SH AUTHOR
|
|
|
|
|
2005-10-11 10:49:27 +02:00
|
|
|
bip authors:
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
Arnaud 'nohar' Cornet
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-18 10:00:55 +02:00
|
|
|
Loic 'Kyoshiro' Gomez
|
2005-10-10 23:56:39 +02:00
|
|
|
|
|
|
|
Thanks to jj, YS and lafouine, for hanging around while we were coding.
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-10 23:56:39 +02:00
|
|
|
Crypto shamelessly taken from Christophe 'sexy' Devine.
|
2005-10-11 18:59:45 +02:00
|
|
|
.br
|
2005-10-18 10:00:55 +02:00
|
|
|
This man page is written by Loic 'Kyoshiro' Gomez.
|
2005-10-11 10:49:27 +02:00
|
|
|
|