Alexander Barton alex@barton.de wrote:
4- restore ngircds ability to talk to the irc.org irc server. ngircd can talk to 2.10 versions, but 2.11 added lots of protocol extensions that first need to be implemented. While the main goal is certainly difficult, i think that some of the protocol extensions are interesting on their own.
It definitely would be "nice" if ngIRCd would became compatible to this ircd again, but I think the protocol changes are rather hughe -- and the documentation is on the same level as for services ... :-/
Are there networks out there actually running ngIRCd and irc.org-ircd in mixed networks?
No idea. However, there are some things that are interesting/useful. E.g. i remember someone requested opless channels (+channels, http://ircnet.irchelp.org/channel.html)
5- add support for encrypted operator passwords. Note that i already implemented this in the tls-master branch, see e.g.
[..]
It's always a good thing not to store passwords in plain text, so this seems to be a good idea. But please keep in mind that ngIRCd is meant to support "legacy systems" that could lack modern libraries like OpenSSL. So backwards compatibility is a must.
Absolutely. Thats why the above patchset has an sha-1 implementation taken from xyssl which is used in case openssl is not available, ie. no mandatory dependency on openssl is introduced.
We have a few bugs listed there marked as "LATER", which all could be interesting to work on ;-) http://arthur.barton.de/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&resolution=LATER&
68 (Too many pre-defined channels configured) looks easy, just replace the static array with a dynamic array (see array.h).
In addition all other open bugs and enhancement-requests listed in Bugzilla can be found here: http://arthur.barton.de/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&resolution=---
66 can be closed -- ipv6 support was added to HEAD recently 8-)
Florian