Skip to content


Subversion checkout URL

You can clone with
Download ZIP
a modular IRC proxy written in C++/TCL
C++ Tcl Shell C PHP Objective-C
Branch: master

Fix special character issue in account.tcl.

Signed-off-by: Gunnar Beutner <>
latest commit 9a4e865447
@thommey thommey authored committed
Failed to load latest commit information.
bncidentd Update copyright.
bnctcl Fix special character issue in account.tcl.
debian Bump version to 1.3.9.
m4 * Fix 'make dist'
php Update copyright.
pkg Bump version to 1.3.9.
src Fix crash in CIRCConnection::ParseLineArgV
third-party Update copyright.
.gitignore * Updated git ignores.
AUTHORS * Imported thom\mey's TCL event patch
COPYING git-svn-id: b3a6972a-4407-041…
ChangeLog * Shut up libtool info messages about shared libs
GPLHeader.txt Update copyright.
GPLHeaderTcl.txt Update copyright.
LICENSE git-svn-id: b3a6972a-4407-041…
LICENSE.Exceptions git-svn-id: b3a6972a-4407-041… * Copyright info about third-party code updated
README Updated documentation.
README.copyright * Updated copyright information
README.faq Updated documentation.
README.iface2 git-svn-id: b3a6972a-4407-041…
README.lean Updated documentation.
README.motd git-svn-id: b3a6972a-4407-0410…
README.settings Updated documentation.
README.ssl Updated documentation. Fixed autogen script. Bump version to 1.3beta7. * Moved match/mmatch code into third-party/ directory
sbnc-start Fixed sbnc-start.
sbnc.sln * win32: Added Visual Project files for the 'mmatch' sub-project.
sbnc.vcxproj Fixed DLL vs. EXE heap problem.
sbnc.vcxproj.filters * win32: Added Visual Project files for the 'mmatch' sub-project.
sbnc_version.h Bump version to 1.3.9.
ssl.conf * Moved win32 resource files into src/ git-svn-id: b3a6972a-4407-0410…


shroudBNC 1.3

shroudBNC is a modular IRC proxy written in C++. It is capable of proxying
IRC connections for multiple users. Using TCL scripts it can be extended.


Please read the INSTALL file for more details about how to install shroudBNC.


Just connect to the bouncer using your favorite IRC client. You will have to set
your username (i.e. e-mail address in most clients) to the accountname you've
chosen for your bouncer account. If for some reason you can't change your
client's username you can specify the username in the password setting (of the form

Once you're connected you should type /msg -sBNC help to get a list of available commands.

shroudBNC supports oidentd in order to provide unique idents for each bouncer
user. You will need to enable ident-spoofing for the Unix account you're using
to run shroudBNC if you want each user to have their own ident. Read oidentd's
manual or for more details.


The tcl module is automatically built and installed if the configure script
was able to find the appropriate tcl libraries and headers.

If the configure script was unable to find the TCL libraries/headers and you
are sure that they are installed you might use the --with-tcl parameter to
specify the location of the file manually; e.g.:

./configure --with-tcl=/usr/local/ActiveTcl/tcl8.4

Log files

shroudBNC automatically re-creates log files if they disappear during runtime. It
also re-opens them if their inode of dev numbers change. Therefore rotating logs
is as easy as moving the existing logs to a different location.


It is vital that you understand that any bouncer admin has access to:

a) the shell account where the bouncer is running
b) any user connections

Using the TCL module any admin can perform shell commands (using the exec
command) and send IRC commands for any user's connection. Thus you should
choose your admins wisely. Do not load arbitrary scripts and make sure you
understand any scripts you want to load.


I'd like to thank all the beta testers who have been using shroudBNC so far.
Feature requests and bug reports are welcome; please use our issue tracker at

In case you encounter problems while compiling and/or using shroudBNC you can
contact us on IRC:

Server: / 6667
Channel: #sbnc

Third Party Software

This product includes software developed by the OpenSSL Project
   for use in the OpenSSL Toolkit (

For a more detailed list of third-party code in this project please refer to
the README.copyright file.
Something went wrong with that request. Please try again.