IRC-Junkie.org - IRC News » Hybrid

Hybrid releases 7.3.0

Kottizen — Sun, 14 Aug 2011 10:05:18 +0000

Earlier this week, Jon Lusky released a new version of ircd-hybrid. The version number has now reached 7.3.0. Among the changes you find a new Bulgarian translation, a fixed IPv6 implementation and channel modes O and S for opers-only respective SSL/TLS-only clients. Server administrators now get to choose whether they want to use SSLv3 or TLSv1 to secure connections. All spy-notice modules that previously covered reports for usage of STATS, TRACE, MOTD and ADMIN have been replaced by server-sided notices. The old LazyLinks concept has now been removed, as it was half broken. The WATCH command known from UnrealIRCd and Bahamut has been added. In addition to that, a few minor cleanups and bugs leading to crashes have been fixed.

Hybrid is used together with Ratbox (which is a fork) and CSIRCd on both EFnet and IRCsource. It has been forked many times and it’s known for its stability and quality of code.

By looking at the SVN repository it seems like the developer team behind Hybrid is working towards a 8.0 release, featuring better services support while still keeping simplicity.

Hybrid releases 7.3.0 is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

IRCd-Hybrid derivate “esphyb” releases version 1.0.4 [Updated]

phrozen77 — Tue, 05 Jan 2010 18:16:07 +0000

[Update] Version 1.0.5 has been released for a important fix regarding a crashbug in the /invite command!

esphyb, an IRCd forked from IRCd-Hybrid that is developed and used on EsperNet, is now available as version 1.0.4.

The features that have been introduced in their custom version include:

Colorless channels (+c/+C), oper-only channels (+O), identified-user channels (+R, +M)

Smarter CAPTURE/UNCAPTURE (aliased to HURT/HEAL)

Configuration-driven “services” aliases, like /NickServ and /NS

SVSMODE for usermodes +a and +r

SVSNICK for “services”-driven nick changes

WEBIRC support for web-to-IRC gateways like CGI:IRC and Mibbit

OPME and OJOIN for emergency channel management

as well as “SSL support, longer ban/exception/invite lists, longer channel names, IPv6 support and CallerID/server-side ignore”.

The changes from the previous version, 1.0.2, are the following:

BUGFIX: /invite no longer allows users to invite banned users.

BUGFIX: bump HOSTLEN to 255 per RFC1123

BUGFIX: hide hidden servers from /links, /map, and /who for non-operators

BUGFIX: Fix IP-based WEBIRC bans

FEATURE: Filter out part messages with colors or control characters from +c/+C channels

FEATURE: Add SSL-only channels (cmode +z, also includes umode +z)

FEATURE: Notice channel operators on /invite

PLATFORM: Fix build on x86-64 Linux

HELP SYSTEM: Updates for new usermodes and various corrections

The IRCd can be downloaded from here.

IRCd-Hybrid derivate “esphyb” releases version 1.0.4 [Updated] is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

IRC.EFNet.CH Supports IPv6

phrozen77 — Sun, 09 Mar 2008 21:37:12 +0000

Another EFNet server adds supports IPv6.

Recently IRC.EFNet.CH added support for the IPv6 protocol. IRC-Junkie asked IRC EFNet.CH admin Taliz for how long IPv6 has been supported on EFNet. “Ratbox is an early fork of Hybrid 7 and, if I recall correctly, has always supported IPv6. Hybrid 7 has supported IPv6 since it was released back in 2003(there were however a lot of Betas & RC’s supporting IPv6 as well, which ratbox built on, dating back to 2001).”

“Some of the first servers supporting IPv6 on EFnet were irc6.qeast.net & irc.ipv6.homelien.no, they linked around 2001. Nowadays Qeast is gone, but IPv6 is enabled on irc.homelien.no as well as a multitude of other servers like irc.efnet.nl, efnet.ipv6.xs4all.nl, irc.inter.net.il, irc.efnet.ch, irc.ipv6.he.net & irc.choopa.net.” These servers can be found in the IPv6 round robin at irc.ipv6.efnet.net.

One of the old concerns with IPv6 was that maliscious users could have access to an unlimited range of addresses for floodbots. “CIDR limits are used to control IPv4 as well as IPv6 classes,” Taliz explains. “You can for example limit /64’s to 5 connections, effectively preventing mass cloning.”

IPv4 remains by far the most popular protocol in use. “I would estimate that there are less than, or around, 2000 IPv6 clients on EFnet regularly,” Taliz ends.

IRC.EFNet.CH Supports IPv6 is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.