ngircd/src, branch rel-26-rc1 ngircd with make http://git.nakidai.ru/ngircd/atom?h=rel-26-rc1 2020-05-07T16:10:41+00:00 Allow more characters per line in MOTD and help text files 2020-05-07T16:10:41+00:00 Alexander Barton alex@barton.de 2020-05-07T16:10:41+00:00 urn:sha1:fcf2874a9d64675c64afbce58cd4cdc73de54978 Change the line buffer in the Read_TextFile() function from 127 to COMMAND_LEN (=512) bytes. Lines can't even get that long, because they have to be prefixed before being sent to the client, so this is a sane maximum. This allows for even more "fancy" and "wider" MOTDs :-) Closes #271. Show allowed channel types in ISUPPORT(005) numeric only 2020-05-07T16:03:06+00:00 Alexander Barton alex@barton.de 2020-05-07T16:03:06+00:00 urn:sha1:4b7e8db418340576c95f1edad8470b66d6fe886d Don't show the static list of all possibly available channel types ... Closes #273. SSL test server: Use port 6790, like "test server #2" 2020-05-06T22:02:00+00:00 Alexander Barton alex@barton.de 2020-05-06T21:55:23+00:00 urn:sha1:21f33e591185fcd8ea5fa02924ffca6f7bf6a686 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. Merge pull request #269 from hillu/gnutls-reload-cert 2020-05-06T21:36:19+00:00 Alexander Barton alex@barton.de 2020-05-06T21:36:19+00:00 urn:sha1:02850008f4a4e8fff5799157d21ee7924345b3e1 Add support for GnuTLS certificate reload. Thanks a lot, Hilko Bengen! Update Client_SetHostname() to not use strpbrk() 2020-05-03T22:58:24+00:00 Alexander Barton alex@barton.de 2020-05-03T22:55:25+00:00 urn:sha1:52d8fa2c09c36632c1cacd8242e22e9de920ec9f Not sure about the portability of strpbrk() in really ancient OS, and this was the only place where it became used recently in ngIRCd ... So let's play it safe! ;-) Allow hostmask cloaking when rDNS is disabled 2020-05-03T22:58:24+00:00 michi michi+ngircd@dataswamp.org 2020-04-21T11:02:08+00:00 urn:sha1:1f40776bc166ece8dad0d333905481aa28786cb5 Don't wait for the network when read buffers possibly hold commands 2020-05-03T22:46:56+00:00 Alexander Barton alex@barton.de 2020-05-03T00:55:34+00:00 urn:sha1:387a29a7fdbf00f5d792ba1450c608db8670308a There is no point in waiting up to one second for the network receiving new data when there is still a read buffer holding at least one command; we shouldn't waste time but handle it immediately! Handle commands in the read buffer before reading more data 2020-05-03T22:46:56+00:00 Alexander Barton alex@barton.de 2020-05-01T21:55:28+00:00 urn:sha1:54fac576030d7aaf8bce4a982c880fe18680741e If there are more bytes in the read buffer already than a single valid IRC command can get long (513 bytes, COMMAND_LEN), wait for this/those command(s) to be handled first and don't try to read even more data from the network (which most probably would overflow the read buffer of this connection soon). Read_Request(): Clean up code and add some more comments 2020-05-03T22:46:56+00:00 Alexander Barton alex@barton.de 2020-05-01T21:41:49+00:00 urn:sha1:9f05f5ee61d23292d55edef09439c38936b86037 No functional changes. Revert "Increase read buffer size for server connections" 2020-05-03T22:46:56+00:00 Alexander Barton alex@barton.de 2020-05-01T20:38:41+00:00 urn:sha1:629a45ee0f4469729f6a9c22a983000fcc39fe61 This reverts commit c6e3c13f27744971fcb1d2de4e561d3bcdaa5aed. This sounded like the right approach at first, but I'm not that sure that it really makes sense to have different sizes of read buffers: the per-connection read buffer only needs to keep data that is needed to parse one full command, be it plain text, encrypted and/or compressed. Then ngIRCd should handle this one command, move leftover data to the beginning of the buffer and read the next chunk from the network that is missing to get the next complete command (512 bytes at max). So I revert this for now and try to fix the logic in Read_Request(), which is broken nevertheless, as it results in servers becoming disconnected during "server burst" when "big" lists are transferred.