ngircd, branch rel-26.1

ngIRCd Release 26.1

2021-01-02T13:32:48+00:00

Update AUTHORS file

2021-01-02T13:23:45+00:00

Update config.guess and config.sub to recent versions

2021-01-02T12:36:45+00:00

- config.guess: 2020-12-22 - config.sub: 2020-12-22

Update NEWS and ChangeLog files

2021-01-01T19:07:47+00:00

Update Platforms.txt

2021-01-01T19:03:58+00:00

- Add aarch64/apple/darwin (Apple CLang 12.0.0) - Add x86_64/unknown/openbsd6.7 (gcc 4.2.1) Thanks to Götz Hoffart

2021! :-)

2021-01-01T14:38:26+00:00

Happy new year!

Explicitely cast Conf_MaxPenaltyTime (time_t) to "long"

2020-12-29T20:45:09+00:00

This fixes the following compiler warning, for example on OpenBSD: conf.c: In function 'Conf_Test': conf.c:391: warning: format '%ld' expects type 'long int', but argument 2 has type 'time_t' Thanks to Götz Hoffart for reporting this!

Don't set AI_ADDRCONFIG, even when it exists

2020-12-29T20:12:43+00:00

Basically, the issue described in #281 is that the test suite uses the IPv4 address 127.0.0.1 on an IPv6-only host. But this is the "safest" thing to do in (almost) all other setups: relaying on DNS host names makes things even more complex, as different systems map 127.0.0.1 differently (including the reverse lookup; that's why we switched to 127.0.0.1 back in 2014, see commit 3f807e10457). But with AI_ADDRCONFIG set, on an IPv6-only host, we prevent 127.0.0.1 to get translated properly, even when the loopback interface has this address configured! So don't set it any more. The drawback is that the resolver possibly returns more addresses now, even of an unsupported/not connected address family; but this shouldn't do much harm in practice, as ngIRCd iterates over all returned addresses while trying to establish an outgoing connection. Closes #281.

FAQ.txt: There is no "CVS" anymore, we use Git!

2020-11-28T20:22:34+00:00

Fix typo in comment: operaor -> operator

2020-11-02T11:13:02+00:00