IRC-Junkie.org – IRC News

All about Internet Relay Chat

William "nenolod" Pitcock quits DroneBL

William “nenolod” Pitcock, founder and long-time operator of the DroneBL DNSBL, announced via a posting on their mailinglist that he’ll discontinue his work on the service “due to time and emotional constraints” “effective immediately”.

DroneBL DNS Blacklist Logo

DroneBL DNS Blacklist Logo

The DNS Blacklist is one of the few that is especially meant to be used for IRC Networks.

He writes that coming to the decision to quit having an active role was not an easy process but he deems the project mature enough that the community “can steer it’s future development focus” and notes that he’ll continue to provide hosting for the blacklist until the community has made appropriate “alternative hosting arrangements”.

nenolod hands over the operations part of the service to Alexander “OUTsider” Maassen which he says that many already know. nenolod notes that he shouldn’t be contacted about issues considering DroneBL anymore as he’d be unable to help from now on.

Closing the announcement, nenolod writes that it is now time for him to “begin work on other endeavours”.

IRC-Junkie wishes nenolod all the best, whatever those future endeavours might be ;)

Oh and yes indeed, thanks for all the fish!

  Copyright secured by Digiprove

Atheme services packages releases version 5.1.0

The team developing the Atheme IRC services just tagged version 5.1.0 of their services package.

The new release brings a lot of bugfixes, feature additons and enhancements as well as a slew of modules that have been contributed to the project by other developers.

Also, a few changes have been made to the available IRCd protocols, mostly improvements and additions concerning InspIRCd support but also a new module which provides support for the Ithildin IRCd has been added. Support for the legacy hyperion daemon, previously used on freenode, has been dropped and support for ShadowIRCd has been updated.

Various helpfiles for the available *Serv’s have been added and updated, the same goes for all the added contributed modules. A taint subsystem has been added which “allows developers to programatically define unsupportable conditions”.

SaslServ has gained the AUTHCOOKIE SASL method which allows for integration with Iris, an AJAX IRC client that is a fork of and aims to be a drop-in replacement for qwebirc which is “designed to integrate with the Atheme IRC platform (including atheme-web) and with IRCv3 client protocol compliance in mind”.

NickServ was expanded with CERTFP support which allows for password-less authentication via SSL certificate fingerprints. The converter for Anope databases has been improved to support newer versions of Anope and has been reworked to be a bit more robust when handling encrypted passwords.

The download can be found here and the complete changelog is available here.

  Copyright secured by Digiprove

ratbox-services updated to v1.2.4

ratbox-services, the services package for ircd-ratbox, have released version 1.2.4 in their stable tree.

ratbox services logo

ratbox services logo

Version 1.2.4 is mainly a bugfix release, one feature addition that this new version got is that you now can specify both the UID/GID and the path it chroots to on startup with a parameter.

Other than that, some inconsistencies with ChanServ enforcing topics have been rectified and it now “enforces topics whenever it is in the channel”. The handling of read-errors received from servers has been fixed as well as the configure-options of both MySQL and PostgreSQL which now take a path to a binary that will provide the compiler with information it needs to compile the respective support in.

The complete changelog for ratbox-services 1.2.4 can be found here and the download can be obtained from here.

  Copyright secured by Digiprove

New Anope stable: 1.8.4

Anope developer chaz announced the immediate availability of a new Anope services release in their stable branch which is now at version 1.8.4.

Anope Logo

Anope Logo

The new release contains a number of “fixes and some further compatibility with InspIRCd 1.2″ but also some new features like tracking of deletes and clearings of XOP access lists and tracking of permanent channels have been introduced.

chaz reveals that there will be some new functionality for their module repository shortly which will “mass build” modules for each new release so prospective users don’t need to rely on the modules author to supply a pre-compiled version of his work.

Furthermore, he announces some of the changes one can look forward in an upcoming 1.9.2 development release which will have a new socket system and finally something that’ll closely resemble live SQL in the form of a “sensible and easy to use commands table which Anope will process at intervals so you can in theory do anything via SQL that you could do from an IRC client”.

In an unusual move, chaz dedicates this release to developer Adam who he says is “not only [...] a development machine but he’s a genuinely nice guy and we’re very grateful for the time and effort he puts into the project” and goes further to commend him to anyone looking for a developer: “If anyone in the real world is looking for a young developer with an incredibly bright future get in touch; he’s definitely worth your time”.

Closing the announcement he writes that “if you are interested in helping / working with us in any way please do get in touch (chaz [at] anope.org), & thank you of course to our sponsors for their selfless kindness” and wishes “Happy Easter to those who celebrate it”.

The downloads can be found here and the full changelog is available here.

Happy Easter from IRC-Junkie to all our readers!

  Copyright secured by Digiprove

Atheme / InspIRCd m_invisible brouhaha

Those who closely follow either projects development will have noticed a few “odd” looking commits to their sourcecode in the past few days.

The commits all concerned InspIRCds m_invisible module which provides similar functionality as the old mode +I in UnrealIRCd 3.1.x.

Quoting the InspIRCd wiki page about m_invisible the module

adds support for quiet (invisible) opers. A quiet oper is invisible to normal users on channels. This can be used for surveillence of botnet channels, statistics bots, etc. Note that other opers CAN see invisible opers; +Q only hides the oper from non-opers.

The brawl emerged when Atheme developer nenolod commited a few changes to the services packages that would make such a join visible to channel members by announcing that “Channel security has been compromised” because an invisible user has joined.

This commit was followed up by danieldg of the InspIRCd developer team who moved the module out of the main – and therefore by default included – modules into the seperate “inspircd-extras” repository, but only in the 2.0 beta and 2.1 pre-alpha branches.

The initial commits to Atheme have since been reverted but there now are checks for m_invisible being loaded and the services package now refuses to link if it spots the module being present.

The module, referred to as “morally unacceptable” and “not … ethical” by nenolod, has legitimate uses such as “private networks inside offices, with special uses, those do need logging and accountability, most of them even disable private messages entirely” said developer Brain when asked about his views of this whole situation. They wrote it because “users asked for the module” and his opinion is that it “should be kept, and we’re keeping it, in third party”.

Brain says to him “it’s all about choice, the choice to run the modules or not to, we aren’t going to tell people whats right and wrong” and that “people are sensible enough and educated enough to decide for themselves”.

What’s your opinion about this? Do you use m_invisible on your network? And if so, do you tell your users that such a module is loaded? Guns don’t kill, people do?

  Copyright secured by Digiprove