BNC (software)

As Bouncer (short: BNC) on IRC is a program called, which can mediate between an IRC client and the IRC server, and thus works as a proxy.

However, the main goal of most Bouncer is not the pure intermediary between a client and a server, but the lasting as possible maintaining a connection to an IRC server or one or more IRC networks. As will be lost in several IRC networks after checkout privileges in channels and the nickname of each other can be used is the only way to "reserve" a nickname or channel priviledges to stay logged in practically permanently using the Bouncers. For this reason, Bouncer programs typically run on a server on the Internet. The user no longer needs to be constantly online using the Bouncers.

Other reasons for the use of bouncers are:

  • Protection of the client computer from attacks, such as a DoS attack or the use of exploits. Because of the IRC server, and thus the users in the IRC view only the IP address of the Bouncer host name is known, the attacks are directed only against this.
  • In IRC occur with a different DNS name (namely, that of the Bouncer hosts), the - results in a certain sense, for example, a funny, curious or leeten text - beyond the purely technical necessity beyond. Provider of rentable bouncers often have a large selection of such DNS Names, between which the tenant can often change at any time and usually arbitrary.
  • The indirect establish a connection to the server when the direct connection, etc. is not possible due to a restrictive firewall.
  • (eg WLANs), as many IRC networks own SSL server does not offer the structure of an encrypted connection between public networks due to capacity problems.
  • The holding of DCC connections. Here, since the connection between Bouncer and client is established, a Bouncerbenutzer go offline, while his bouncer keeps the DCC connection.
  • Caching channel and private messages in their absence.
  • Anonymity. Since the IP address is usually hidden behind the Bouncer, the chatter can be traced back directly.

More sophisticated Bouncer offer various extras, such as the automatic " defense" of the nicks and channel in front of strangers or distributing the channel operator status ( Chanop ) to familiar user, a party line ( independent of the IRC server chat only between the users of a Bouncers ), automatic switching to the most beneficial servers within a network, IRC and many others.

Bouncer software

There are several Bouncer programs, which mainly differ in their features. The following is a partial list. All programs listed are open source.

  • EZBounce is a bouncer, which SSL encrypted connections, IPv6 support and chat logs.
  • PsyBNC is a bouncer, which symmetrically encrypted phone calls, SSL encrypted connections, recording of queries in the absence of the user as well as IPv6 support. You can connect multiple instances psyBNC to a " botnet " with a common party line. psyBNC can be extended by its own scripting language.
  • ShroudBNC ( sBNC ) supports SSL encrypted connections and has a web interface. sBNC records queries, when the user is absent. sBNC can be extended with Tcl scripts and modules in C ; some pre Tcl scripts are also in the source package.
  • ZNC is another bouncer. He also supports SSL encrypted connections and has a web interface. ZNC can be expanded greatly through (already existing ) modules and scripts in Perl and Tcl, supports IPv6 and channel can login.

Criticism of bouncers

Bouncer put through a variety of behaviors that are not popular in some IRC networks ( this list is based on the functionality and use of most Bouncer ):

  • Networks, which offer no possibility to register nicknames and channels, often do so aware of the attitude out that Nick and Channel are in principle free, so no user has a permanent right to use a given nick or channel. However Bouncer strive against this principle by releasing hold by permanent presence Nicks and channel their " owners ".
  • In networks with IRC services that facilitate the registration of nicknames and channels, the corresponding protective functions of the bouncers are largely superfluous and can the network by senseless fights with IRC services unnecessarily.
  • Bouncer reinforce the impression of Idlens on IRC, since users who are offline, yet are still held by their presence Bouncer, but are not active. This makes it difficult sometimes keep apart when a user is actually there or is represented only by its bouncers.
  • In general, like all unguarded bots on IRC, bouncers carry the risk to behave in an uncontrolled manner in the absence of the owner, without that it can be detected and prevented in time.
141279
de