ngircd/src, branch rel-23-rc1ngircd with make
http://git.nakidai.ru/ngircd/atom?h=rel-23-rc12015-09-03T14:22:36+00:00Make server-to-server protocol more robust2015-09-03T14:22:36+00:00Alexander Bartonalex@barton.de2015-09-03T14:22:36+00:00urn:sha1:eb9929e82c735100a0b432f878f83fce091eb636
Now ngIRCd catches more errors on the server-to-server (S2S) protocol
that could crash the daemon before. This hasn't been a real problem
because the IRC S2S protocol is "trusted" by design, but the behavior
is much better now.
Thanks to wowaname on #ngircd for pointing this out!
Reproducible builds2015-08-26T08:05:36+00:00Christoph Biedlngircd.anoy@manchmal.in-ulm.de2015-08-25T16:12:05+00:00urn:sha1:ccc899c7f4751ba72dcd7330c55614cf986f0fa3
At the moment ngircd fails the tests for reproducible builds in Debian
since it uses the __DATE__ and __TIME__ macros for the INFO command.
Instead of patching this out I decided to implement an optional
constant BIRTHTIME that allows you to set a time stamp for the "Birth
Date" information, in seconds since the epoch, like in
export CFLAGS += -DBIRTHTIME=$(shell date +%s --date="2015/08/15 23:42:22")
In the future, Debian will provide a SOURCE_DATE_EPOCH environment
variable, dealing with the situation until then will be my job.
The time format was taken from the NGIRCd_StartStr formatting in
ngircd.c so the "Birth Date" and "On-line since" lines in the INFO
output look similar:
:irc.example.net 371 nick :ngIRCd 22.1-IDENT+IPv6+IRCPLUS+PAM+SSL+SYSLOG+ZLIB-x86_64/pc/linux-gnu
:irc.example.net 371 nick :Birth Date: Tue Aug 25 2015 at 18:11:11 (CEST)
:irc.example.net 371 nick :On-line since Tue Aug 25 2015 at 18:11:33 (CEST)
:irc.example.net 374 nick :End of INFO list
The format of the time stamped is changed, but as far as I can tell, there's no
rule that is violated by that.
Bonus level: Reformat the messages so the time stamps are aligned.
Whitespace fixes (no functional changes)2015-08-01T13:15:30+00:00Alexander Bartonalex@barton.de2015-08-01T13:15:30+00:00urn:sha1:9811223fb882413645db38948ac05fa21ddd3514Fix debug message "Client ... is closing connection"2015-08-01T13:14:23+00:00Alexander Bartonalex@barton.de2015-08-01T13:14:23+00:00urn:sha1:0083fe177f727af6ab43e190e3bea8a94555348e
It should be "host:port"!
"NoticeAuth" configuration variable is deprecated now!2015-08-01T12:52:07+00:00Alexander Bartonalex@barton.de2015-08-01T12:43:38+00:00urn:sha1:85dc4d87770f821b777f5dbf6372956dbffc770cMerge pull request #217 from SaberUK/master+notice-auth2015-08-01T12:51:04+00:00Alexander Bartonalex@barton.de2015-08-01T12:51:04+00:00urn:sha1:64c265cf33d09cfb9ab5e7d0bbc8033dc85f7c64
Use "NOTICE *" before registration instead of "NOTICE AUTH".First check if channel has mode "N", then check membership2015-08-01T12:26:11+00:00Alexander Bartonalex@barton.de2015-08-01T12:21:32+00:00urn:sha1:b8482fd3cfdb429aec75575958f4d5d4e9ae22df
This should be more efficient.
Merge pull request #214 from Flupsy/channel-mode-N2015-08-01T12:24:20+00:00Alexander Bartonalex@barton.de2015-08-01T12:24:20+00:00urn:sha1:90ea23ab4fe3032824e22eb59bee305f35c4aae7
Channel mode N (users on this channel can't change their nick)Streamline ".gitignore" files2015-07-19T01:03:06+00:00Alexander Bartonalex@barton.de2015-07-19T01:03:06+00:00urn:sha1:a5ca8be6588590c6c5feb35bb0f149c0619122c4Rename NoticeAuth to NoticeBeforeRegistration.2015-07-14T13:43:19+00:00Peter Powellpetpow@saberuk.com2015-07-14T13:43:19+00:00urn:sha1:5545e1bebf31ddb9f89c80979c0be93e3fdf6f0c
The old name is still supported for compatibility reasons.