ngircd/src/testsuite, branch rel-26.1

Test suite: Wait 2 seconds after reloading the daemon

2020-11-01T16:25:39+00:00

On reload, all listening ports are closed, configuration updated, and then opened again. Which leads to subsequent tests running while the daemon isn't listening on any ports, and that's why the tests fail. The "proper" way whould be to loop and check for open ports, but waiting is what the start-server.sh script does right now, so stick with this in reload-server.sh for now as well. This fixes the issue, at least on my RaspberryPi ... Closes #280.

testsuite: Add missing files to EXTRA_DIST

2020-05-22T15:23:42+00:00

26~rc1 as extracted from tarball cannot be built/tested with SSL support because of a missing script and certificates.

SSL test server: Use port 6790, like "test server #2"

2020-05-06T22:02:00+00:00

Don't use the "standard" IRC SSL port 6697, as this easily collides with real (ng)IRCd instances running on the same machine. And by reusing port 6790, which is already used by the "test server #2", we don't need any other port than the test suite already uses.

updating testsuite to support ssl-tests

2020-04-24T22:04:38+00:00

Test suite: Test multiple "Modes" lines in [Channel] sections

2020-03-29T00:16:37+00:00

Predefined channles: Fix handling of legacy configuration options

2020-03-28T23:45:59+00:00

Fix the handling of legacy "Key" and "MaxUsers" [Channel] settings: - Activate them before evaluating the "Modes" parameter, to allow the latter to override those legacy options. - Enforce setting the respective +k/+l mode(s) to support the legacy "Mode = kl" notation, which was valid but is an invalid MODE string: key and limit are missing! So set them manually when "k" or "l" are detected in the first MODE parameter. - Sort modes +kl alphabetically, adjust test suite accordingly.

Make test suite compatible with Haiku

2019-11-03T14:15:59+00:00

Implement new configuration option "MaxPenaltyTime" (#251)

2018-11-28T13:13:09+00:00

This option configures the maximum penalty time increase in seconds, per penalty event. Set to -1 for no limit (the default), 0 to disable penalties altogether. ngIRCd doesn't use penalty increases higher than 2 seconds during normal operation, so values higher than 1 rarely make sense. Disabling (or reducing) penalties can greatly speed up "make check" runs for example, see below, but are mostly a debugging feature and normally not meant to be used on production systems! Some example timings running "make check" from my macOS workstation: - MaxPenaltyTime not set: 4:41,79s - "MaxPenaltyTime = 1": 3:14,71s - "MaxPenaltyTime = 0": 25,46s Closes #249.

Send_Message: Fix handling of "empty" targets

2016-01-07T00:54:11+00:00

Clients can specify multiple targets for the "PRIVMSG", "NOTICE", and "SQUERY" commands, separated by commas (e. g. "PRIVMSG a,#b,c :text"). Since commit 49ab79d0 ("Limit the number of message targes, and suppress duplicates"), ngIRCd crashed when the client sent the separator character only as target(s), e. g. "," or ",,,," etc.! This patch fixes the bug and adds a test case for this issue. Thanks to Florian Westphal for spotting the issue!

Limit the number of message targes, and suppress duplicates

2016-01-04T21:15:46+00:00

This prevents an user from flooding the server using commands like this: PRIVMSG nick1,nick1,nick1,... Duplicate targets are suppressed silently (channels and clients). In addition, the maximum number of targets per PRIVMSG/NOTICE/... command are limited to MAX_HNDL_TARGETS (25). If there are more, the daemon sends the new 407 (ERR_TOOMANYTARGETS_MSG) numeric, containing the first target that hasn't been handled any more. Closes #187.