BitchX

From Wikipedia, the free encyclopedia

BitchX
Developed by Colten Edwards (panasync)
Latest release 1.1-final / March 26, 2004
Genre IRC client
License Revised BSD license
Website http://www.bitchx.org
BitchX ANSI splash screen (one of several in rotation).
BitchX ANSI splash screen (one of several in rotation).

BitchX is a free IRC client. The initial implementation, written by "Trench" and "HappyCrappy", was a script for the IrcII chat client. It was converted to a program on its own right by panasync (Colten Edwards). BitchX 1.1 final was released in 2004. It is written in C, and is a console application. A graphical interface is also available, which uses the GTK+ toolkit. It works on most Unix-like operating systems, and is distributed under a BSD license. It is originally based on ircII-EPIC and eventually it was merged into the EPIC IRC client. It supports IPv6[1], multiple servers and SSL, but not UTF-8. BitchX (often called just "BX" by fans) is well known for its unique default of sending random messages on a /quit.

BitchX is the current project. While there is no current release to the public on the new code base, the project is leaning towards merging back to the current base version of Epic.

Contents

[edit] Security

It was known that early versions of BitchX were vulnerable to a denial of service attack in that they could be caused to crash by passing specially-crafted strings as arguments to certain IRC commands. This was before format string attacks became a well-known class of vulnerability.[2]

The current version of BitchX, released in 2004, has security problems allowing remote IRC servers to execute arbitrary code on the client's machine (CVE-2007-336, CVE-2007-4584).

[edit] See also

[edit] External links

A customised Debian desktop, showing BitchX in the foreground.
A customised Debian desktop, showing BitchX in the foreground.

[edit] References

  1. ^ Peter Loshin (2004). IPv6: Theory, Protocol, and Practice. Morgan Kaufmann, p. 316. 
  2. ^ Ryan Russell (2002). Hack Proofing Your Network. Syngress, p. 329.