ngircd/src, branch rel-19.2-rc1 ngircd with make http://git.nakidai.ru/ngircd/atom?h=rel-19.2-rc1 2012-06-08T23:58:40+00:00 Rename "CloakModeHost" option to "CloakHostModeX" 2012-06-08T23:58:40+00:00 Alexander Barton alex@barton.de 2012-06-08T23:57:17+00:00 urn:sha1:7b6b492bdd259c25c4477e33392510872107ca6a Introduce new configuration option "CloakModeHost" 2012-06-08T23:58:25+00:00 Christoph Biedl ngircd.anoy@manchmal.in-ulm.de 2012-06-08T23:55:22+00:00 urn:sha1:aa7db2c0e9e1112591cbdb3d346342d34ca21a6a This closes bug #124. Correctly handle asynchronously re-established server links 2012-06-08T23:03:48+00:00 Alexander Barton alex@barton.de 2012-06-08T23:03:48+00:00 urn:sha1:684e50f0a4d827965b61c4b9feeda403ec3c3b87 Don't try to establish an outgoing server link after DNS lookup when this server re-connected on its own in the meantime. In addition, log a warning message if we try to update the connection index of an already connected server structure -- and ignore it. Up to now, both behaviour could lead to a race when the remote server connects to this daemon while it still prepares the outgoing connection: - The local server prepares the new outgoing connection ... - in the meantime the remote server becomes connected and registered. - Now the new outgoing connection overwrites the (correct) socket handle, - then the 2nd connection becomes disconnected: "already registered", - and the 1st connection becomes unhandled ("gets lost") because the configuration structure is reset because of the wrong socket handle. This patch hopefully fixes all these problems. Log a debug message when SIGUSR2 is handled 2012-06-08T20:08:52+00:00 Alexander Barton alex@barton.de 2012-06-08T20:08:52+00:00 urn:sha1:4a90959cb563e7c6ca57d32779074b448982c94f NoticeAuth: Fix test if IDENT reply has been invalid 2012-06-01T22:32:19+00:00 Alexander Barton alex@barton.de 2012-06-01T22:32:19+00:00 urn:sha1:e7e47e77a3886c258368a14a8c0bb393280aac64 This fixes conn.c: In function ‘cb_Read_Resolver_Result’: conn.c:2252: warning: comparison between pointer and integer IDENT reply: only allow alphanumeric characters in user name 2012-06-01T22:24:53+00:00 Alexander Barton alex@barton.de 2012-06-01T22:24:53+00:00 urn:sha1:695df6532ec717e5571e1ddc2c88a8c968603c5a Only alphanumeric characters are allowed in the user name, so ignore all IDENT replies that would violate this rule and use the one supplied by the USER command. USER command: only allow alphanumeric characters in user name 2012-06-01T21:57:51+00:00 Alexander Barton alex@barton.de 2012-06-01T21:57:51+00:00 urn:sha1:6680b536c4da7dc27e11490fe098e98cb0393fa2 Only alphanumeric characters are allowed in the user name, so terminate the connection if any "strage" characters have been supplied by the user. This is how other IRC daemons (like ircd2.11 and ircd-seven) behave ... Change wording of "TLS initialized" message 2012-05-23T15:12:31+00:00 Alexander Barton alex@barton.de 2012-05-23T15:08:42+00:00 urn:sha1:c0d059cd0ed4403e50820437d9a4cce1648c6b5a Don't use the word "socket" to identify the connection number, but use the word "connection" like on all the other messages logged. Pidfile_Create(): Don't leak file descriptor on error path 2012-05-22T11:31:08+00:00 Alexander Barton alex@barton.de 2012-05-22T11:29:31+00:00 urn:sha1:7faa3ed7d6613f23e998604461f543e763278f7e Detected by cppcheck: [src/ngircd/ngircd.c:502]: (error) Resource leak: pidfd Numeric 005 (ISUPPORT), CHANMODES: add missing mode "r" 2012-05-01T11:42:57+00:00 Alexander Barton alex@barton.de 2012-05-01T11:42:57+00:00 urn:sha1:5e5377a0631841db7d16e0d4693a3d4cee9b75f6