Moin, moin!
This morning I released the 2nd release candidate for the ngIRCd 18 release: ngIRCd 18~rc2.
Some documentation and our manual pages have been updated and a SSL-related regression has been fixed, that prevented the current ngIRCd to link with elder releases using SSL.
Please have a look at our GIT history or the NEWS and ChangeLog files for the whole story:
- <http://ngircd.barton.de/doc/NEWS>
- <http://ngircd.barton.de/doc/ChangeLog>
And as already stated for the 1st release candidate, please DON’T FORGET TO READ the INSTALL text, it contains valuable upgrading information regarding the new structure of ngircd.conf:
- <http://ngircd.barton.de/doc/INSTALL>
You can find this prerelease here:
- <ftp://ftp.berlios.de/pub/ngircd/>
- <ftp://ngircd.barton.de/pub/ngircd/>
There are source packages, GnuPG signatures, and a binary package for Mac OS X.
Regards
Alex
Hi All!
Here it is, the first release candidate for ngIRCd release 18!
Our last release dates back to 2010, so it’s long overdue … and in the meantime, lots of patches and enhancements have accumulated. All in all, 116 files changed and there were 3590 insertions and 2306 deletions to our codebase since release 17.1 — quite a lot.
There is new functionality with new configuration options like „MorePrivacy“, „ScrubCTCP“, „RequireAuthPing“, „ NoticeAuth“, „CloakHost“ and „CloakUserToNick“; a new channel mode „O“ („IRC Ops only“); support for ZeroConf service registration has been removed; and, quite prominent, the restructuring of the ngircd.conf configuration file.
Please have a look at our GIT history or the NEWS and ChangeLog files for the whole story:
- <http://ngircd.barton.de/doc/NEWS>
- <http://ngircd.barton.de/doc/ChangeLog>
And please DON’T FORGET TO READ the INSTALL text, it contains valuable upgrading information regarding the new structure of ngircd.conf:
- <http://ngircd.barton.de/doc/INSTALL>
This is our first release candidate; not the final release. So keep in mind that there can be bugs: please report all problems you encounter, to the mailing list or our bug tracker — thanks!
You can find this prerelease here:
- <ftp://ftp.berlios.de/pub/ngircd/>
- <ftp://ngircd.barton.de/pub/ngircd/>
There are source packages, GnuPG signatures, and a binary package for Mac OS X.
Regards
Alex
PS.: I will update my unofficial debian repository as soon as I find time …
Hi ngIRC'ers!
we discussed the layout of ngircd.conf and the massive growth of variables in the [Global] section a few weeks (months!?) ago in irc://irc.barton.de/#ngircd -- today I published a patch restructuring ngircd.conf, please review it and let me know what you think:
<https://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd-alex.git;a=shortlog;h=…>
The new layout splits the variables from [Global] into the sections [Global], [Limits], and [Options]. Left in [Global] are only configuration options that most probably every ngIRCd administrator has to adjust; all the limits (MaxConnections, …) and timeouts (PING, PONG) are stored below [Limits]; and all (optional) features are move into the [Options] section.
All moved or renamed variables ("NoPAM = yes" -> "PAM = no") are still recognized in their old location in [Global], but marked as "deprecated" and will emit a warning message when starting ngIRCd or running "ngircd --configtest". So you should be able to use your old configuration file without loss of functionality.
There have been no changes to the handling of [Operator], [Server], or [Channel] blocks.
What do you think?
Regards
Alex
PS.: this would be the new layout:
[GLOBAL]
Name
AdminInfo1
AdminInfo2
AdminEMail
Info
Listen
MotdFile
MotdPhrase
Password
PidFile
Ports
ServerGID
ServerUID
[LIMITS]
ConnectRetry
MaxConnections
MaxConnectionsIP
MaxJoins
MaxNickLength
PingTimeout
PongTimeout
[OPTIONS]
AllowRemoteOper
ChrootDir
CloakHost
CloakUserToNick
ConnectIPv4
ConnectIPv6
DNS
Ident
NoticeAuth
OperCanUseMode
OperServerMode
PAM
PredefChannelsOnly
RequireAuthPing
SSLCertFile
SSLDHFile
SSLKeyFile
SSLKeyFilePassword
SSLPorts
SyslogFacility
WebircPassword
[Operator]
…
[Server]
…
[Channel]
…
Hello, and thanks in advance for any help.
I want to set up a lightweight IRC server, and ngircd seems perfect. I can't
find some documentation on certain things, however... for example, in the
README it says
"Implemented IRC-commands are:
ADMIN, AWAY, CHANINFO, CONNECT, DIE, DISCONNECT, ERROR, HELP, INVITE, ISON,
JOIN, KICK, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NJOIN,
NOTICE,
OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, REHASH, RESTART, SERVER, SQUIT,
STATS, TIME, TOPIC, TRACE, USER, USERHOST, VERSION, WALLOPS, WHO, WHOIS,
WHOWAS."
However, I can't seem to find the syntax for any of these! I tried using
help, but that just brings up MIRC's help.
There are a couple of things I'd like to do at the moment, but am unsure of
how, for example: I made a persistent room, and want to make myself the
operator of it. I used /oper to make myself an irc admin, but /mode #channel
+o myname gives me a 'you are not channel operator name.' I can't see in the
server logs where to set this, and it seems odd that despite being an irc
operator, I can't just force the mode command.
If there is a place where things like this are documented more thoroughly
I'd lvoe that. Otherwise, I'd deeply appreciate any help you
Jon
Hello, and thanks in advance for any help (I'm not sure if this is going to
double post, forgive me if it does, my mail client bugged).
I want to set up a lightweight IRC server, and ngircd seems perfect. I can't
find some documentation on certain things, however... for example, in the
README it says
"Implemented IRC-commands are:
ADMIN, AWAY, CHANINFO, CONNECT, DIE, DISCONNECT, ERROR, HELP, INVITE, ISON,
JOIN, KICK, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NJOIN,
NOTICE,
OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, REHASH, RESTART, SERVER, SQUIT,
STATS, TIME, TOPIC, TRACE, USER, USERHOST, VERSION, WALLOPS, WHO, WHOIS,
WHOWAS."
However, I can't seem to find the syntax for any of these! I tried using
help, but that just brings up MIRC's help.
There are a couple of things I'd like to do at the moment, but am unsure of
how, for example: I made a persistent room, and want to make myself the
operator of it. I used /oper to make myself an irc admin, but /mode #channel
+o myname gives me a 'you are not channel operator name.' I can't see in the
server logs where to set this, and it seems odd that despite being an irc
operator, I can't just force the mode command.
If there is a place where things like this are documented more thoroughly
I'd lvoe that. Otherwise, I'd deeply appreciate any help you
Jon
this patch contains:
* Fix for Conf_CloakUserToNick to make it conceal user details
(extended user string).
* Adds MorePrivacy-feature
MorePrivacy censors some user information from being reported by the
server. Signon time and idle time is censored. Part and quit messages
are made to look the same. WHOWAS requests are silently dropped. All
of this is useful if one wish to conceal users that access the ngircd
servers from TOR or I2P.
View attached file for more info :)
This patch makes it possible to scrub incomming CTCP commands from
other servers and clients alike. The ngircd oper can enable it from
the config file, by adding "ScrubCTCP = yes" under [FEATURES]. It is
default off.
CTCP can be used to profile IRC users (get user clients name and
version, and also their IP addresses). This is not something we like
to happen when user pseudonymity/secrecy is important.
The server silently drops incomming CTCP requests from both other
servers and from users. The server that scrubs CTCP will not forward
the CTCP requests to other servers in the network either, which can
spell trouble if not every oper knows about the CTCP-scrubbing.
Scrubbing CTCP commands also means that it is not possible to send
files between users.
There is one exception to the CTCP scrubbing performed: ACTION ("/me
commands") requests are not scrubbed. ACTION is not dangerous to users
(unless they use OTR, which does not encrypt CTCP requests) and most
users would be confused if they were just dropped.
A CTCP request looks like this:
ctcp_char, COMMAND, arg0, arg1, arg2, .. argN, ctcp_char
ctcp_char is 0x01. (just like bold is 0x02 and color is 0x03.)
They are sent as part of a message and can be delivered to channels
and users alike.
If there is any error in what I just said, please tell me :D
Attached is the patch for ScrubCTCP. I am not that good at writing
patches. This is actually my very first one for a real project. So
please be patient with me :)
