shroudBNC will automatically attempt to use oidentd if it is installed on the system. But for it to work, you need to configure oidentd, allowing the user sBNC is running under to spoof the ident. If it is not installed, it should be available through the package manager for your distribution.
The global configuration of oidentd can be configured in /etc/oidentd.conf. Here is an example of what the configuration file needs to look like. Remember to edit the file with root privileges and to replace “bouncer” with the actual user on the system running sBNC.
# Configuration for oidentd
# see oidentd.conf(5)
#
default {
default {
deny spoof
deny spoof_all
deny spoof_privport
allow random
allow random_numeric
allow numeric
deny hide
}
}
user bouncer {
default {
allow spoof
allow spoof_all
allow random
allow hide
}
}
After making changes to /etc/oidentd.conf, oidentd needs to be restarted for the changes to take effect. This can usually be done with the following shell command:
/etc/init.d/oidentd restart
Oidentd will also need permission to read the file ”.oidentd.conf”, created by shroudBNC in the user's home directory1). As oidentd is usually running as “nobody” you have to chmod the file to “604”.
chmod 604 ~/.oidentd.conf
Do not forget to switch back to your sbnc user before you execute this command.
To check if you have configured it properly, users will have to reconnect to the IRC network, as the ident for users is only checked when connecting.