<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ngircd/src, branch rel-24</title>
<subtitle>ngircd with make
</subtitle>
<id>http://git.nakidai.ru/ngircd/atom?h=rel-24</id>
<link rel='self' href='http://git.nakidai.ru/ngircd/atom?h=rel-24'/>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/'/>
<updated>2017-01-18T23:06:46+00:00</updated>
<entry>
<title>Fix handling of connection pool allocation and enlargement</title>
<updated>2017-01-18T23:06:46+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2017-01-18T23:06:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=879d5504081e09600464f503db8282e47f79abaa'/>
<id>urn:sha1:879d5504081e09600464f503db8282e47f79abaa</id>
<content type='text'>
The daemon only enlarged its connection pool when accepting new client
connections, not when establishing new outgoing server links.

Thanks to Lukas Braun (k00mi) for reporting this!

In addition this patch streamlines the connection pool allocation, so
that there is only one place in the code allocating the pool: the now
updated Socket2Index() function. The name doesn't quite fit, but this
existing and today quite useless function (because the mapping from
socket number to connection index is 1:1 today) already became called
in almost all relevant code paths, so I decided to reuse it to keep the
patch small ...probably we want to fix the naming in a second patch?

Closes #231.
</content>
</entry>
<entry>
<title>2017!</title>
<updated>2017-01-15T21:07:11+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2017-01-15T21:07:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=2bb917f05aafaf526736d0b7ade2f330835bbbe1'/>
<id>urn:sha1:2bb917f05aafaf526736d0b7ade2f330835bbbe1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Log privilege violations and failed OPER as "error" and to &amp;server</title>
<updated>2016-12-08T00:34:33+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-08T00:34:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=02c8887543b298abcc7b79d752e22cbd34ea8069'/>
<id>urn:sha1:02c8887543b298abcc7b79d752e22cbd34ea8069</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Immediately shut down connection on receiving ERROR</title>
<updated>2016-12-08T00:01:40+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-08T00:01:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=77861f6fe24a7a6be85c6f8112f08172ad7ffa67'/>
<id>urn:sha1:77861f6fe24a7a6be85c6f8112f08172ad7ffa67</id>
<content type='text'>
Don't wait for the peer to close the connection. This allows us to
forward the ERROR mesage in the network, instead of the very generic
"client closed connection" message.
</content>
</entry>
<entry>
<title>x-Line synchronization: Don't send negative durations</title>
<updated>2016-12-07T23:22:05+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-07T23:22:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=0dc3c134697444e1470c87c6f22211ba220ec4ec'/>
<id>urn:sha1:0dc3c134697444e1470c87c6f22211ba220ec4ec</id>
<content type='text'>
</content>
</entry>
<entry>
<title>List expiration: use same log level as when setting</title>
<updated>2016-12-07T23:20:38+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-07T23:20:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=d0d4de498000ff80d11aaa35509f082a80bb317e'/>
<id>urn:sha1:d0d4de498000ff80d11aaa35509f082a80bb317e</id>
<content type='text'>
And log this event to the &amp;SERVER channel, too.
</content>
</entry>
<entry>
<title>Remove leftover debug message. Oops!</title>
<updated>2016-12-07T23:18:57+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-07T23:18:57+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=85df41490710fcefd158e4e8d8175207d24feb2f'/>
<id>urn:sha1:85df41490710fcefd158e4e8d8175207d24feb2f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>G-LINES: Forbid remote modifications if "AllowRemoteOper" is not set</title>
<updated>2016-12-07T23:14:00+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-07T23:14:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=f5ff22d98febeddcc51668c49f35940cbffe599e'/>
<id>urn:sha1:f5ff22d98febeddcc51668c49f35940cbffe599e</id>
<content type='text'>
Explicitely forbid remote servers to modify "x-lines" (G-LINES) when the
"AllowRemoteOper" configuration option isn't set, even when the command
seems to originate from the remote server itself: this prevents GLINE's
to become set during server handshake in this case (what wouldn't be
possible during regular runtime when a remote IRC Op sends the command)
and what can't be undone by IRC Ops later on (because of the missing
"AllowRemoteOper" option) ...
</content>
</entry>
<entry>
<title>Fix building ngIRCd with OpenSSL 1.1</title>
<updated>2016-12-05T22:51:07+00:00</updated>
<author>
<name>Christoph Biedl</name>
<email>ngircd.anoy@manchmal.in-ulm.de</email>
</author>
<published>2016-12-05T19:26:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=daa88b765111b14047c97256bd2a9a2daabe123b'/>
<id>urn:sha1:daa88b765111b14047c97256bd2a9a2daabe123b</id>
<content type='text'>
At the moment, ngIRCd fails to build against OpenSSL 1.1 since the
configure check probes for the SSL_library_init symbol which was
removed, but probing for a different function availabe in both versions
solves that problem: SSL_new().

And as SSL_library_init is no longer needed, the patch boils down to
probing SSL_new to assert libssl is available, and disabling the
SSL_library_init invokation from OpenSSL 1.1 on, see also another
application[1] (NSCA-ng) that did pretty much the same.

Patch was compile-tested on both Debian jessie (OpenSSL 1.0.2) and
stretch (OpenSSL 1.1).

[1] &lt;https://www.nsca-ng.org/cgi-bin/repository/nsca-ng/commit/?id=8afc22031ff174f02caad4afc83fa5dff2c29f8a&gt;

(Patch by Christoph, commit message cherry-picked from the email thread
on the mailing list by Alex. Thanks!)
</content>
</entry>
<entry>
<title>gcc 6.2 warnings: fix code indentation</title>
<updated>2016-12-05T22:33:12+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2016-12-05T22:33:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=2924b3d52ac2ab89e3bc517a1f664ec056a45edd'/>
<id>urn:sha1:2924b3d52ac2ab89e3bc517a1f664ec056a45edd</id>
<content type='text'>
This fixes the following correct -Wmisleading-indentation warning
messages of gcc 6.2:

irc-write.c: In function ‘IRC_SendWallops’:
irc-write.c:521:4: warning: this ‘if’ clause does not guard...
irc-write.c:524:5: note: ...this statement, but the latter is
  misleadingly indented as if it is guarded by the ‘if’
irc-write.c:526:4: warning: this ‘if’ clause does not guard... []
irc-write.c:529:5: note: ...this statement, but the latter is
  misleadingly indented as if it is guarded by the ‘if’

irc-info.c: In function ‘IRC_STATS’:
irc-info.c:895:3: warning: this ‘else’ clause does not guard...
irc-info.c:897:4: note: ...this statement, but the latter is
  misleadingly indented as if it is guarded by the ‘else’

No functional changes, the code has been correct, but the indentation
was wrong ...
</content>
</entry>
</feed>
