Branch: refs/heads/test-suite-no-DNS
Home: https://github.com/ngircd/ngircd
Commit: ef00e070ab2e1d1dd63c5079a9d2e1ce16b2ad87
https://github.com/ngircd/ngircd/commit/ef00e070ab2e1d1dd63c5079a9d2e1ce16b…
Author: Alexander Barton <alex(a)barton.de>
Date: 2014-04-18 (Fri, 18 Apr 2014)
Changed paths:
M src/testsuite/channel-test.e
M src/testsuite/check-idle.e
M src/testsuite/connect-test.e
M src/testsuite/invite-test.e
M src/testsuite/join-test.e
M src/testsuite/kick-test.e
M src/testsuite/message-test.e
M src/testsuite/misc-test.e
M src/testsuite/mode-test.e
M src/testsuite/ngircd-test1.conf
M src/testsuite/ngircd-test2.conf
M src/testsuite/opless-channel-test.e
M src/testsuite/server-link-test.e
M src/testsuite/stress-A.e
M src/testsuite/who-test.e
M src/testsuite/whois-test.e
Log Message:
-----------
Test suite: Don't use DNS lookups
Different operating systems do behave quite differently when doing DNS
lookups, for example "127.0.0.1" sometimes resolves to "localhost" and
sometimes to "localhost.localdomain" (for example OpenBSD). And other
systems resolve "localhost" to the real host name (for example Cygwin).
So not using DNS at all makes the test site much more portable.
**NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
Branch: refs/heads/master
Home: https://github.com/ngircd/ngircd
Commit: b4f7aae67e1ab3be8f01c27190316683fbe9f0d8
https://github.com/ngircd/ngircd/commit/b4f7aae67e1ab3be8f01c27190316683fbe…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-03-25 (Sun, 25 Mar 2018)
Changed paths:
M src/ngircd/conn.c
Log Message:
-----------
Correctly retry outgoing conenctions when forking a resolver failed
When ngIRCd failed to spawn a new resolver subprocess, the connection
structure was still marked as "SERVER_WAIT", and no new attempt to
connect to this server was made.
Thanks to Robert Obermeier for reporting this bug!
Closes #243.
Branch: refs/heads/master
Home: https://github.com/ngircd/ngircd
Commit: 6a622c0084ec69563609804520e2753501254503
https://github.com/ngircd/ngircd/commit/6a622c0084ec69563609804520e27535012…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-03-11 (Sun, 11 Mar 2018)
Changed paths:
M contrib/MacOSX/ngIRCd.xcodeproj/project.pbxproj
Log Message:
-----------
Update Xcode project for latest Xcode version (9.2)
This includes adding missing and deleting obsolete file references.
Commit: ac341176da5bbe99a9b07353f6e9790575ce1493
https://github.com/ngircd/ngircd/commit/ac341176da5bbe99a9b07353f6e9790575c…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-03-11 (Sun, 11 Mar 2018)
Changed paths:
M src/ngircd/irc-channel.c
Log Message:
-----------
Only send TOPIC updates to a channel when the topic actually changed
This prevents the channel from becoming flooded by unecessary TOPIC
update messages, that can happen when IRC services try to enforce a
certain topic but which is already set (at least on the local server),
for example. Therefore still forward it to all servers, but don't inform
local clients (still update setter and timestamp information, though!)
Commit: 798de94d6556bdf2c6019f368ad7441fe6e2d1be
https://github.com/ngircd/ngircd/commit/798de94d6556bdf2c6019f368ad7441fe6e…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-03-11 (Sun, 11 Mar 2018)
Changed paths:
M src/ngircd/irc.c
Log Message:
-----------
Fix use-after-free while handling ERROR during client login
This patch fixes a "use after free" bug which is hit while processing
ERROR commands while a new client is logging into the server, which
leads to only the CLIENT structure becoming freed, but not the
CONNECTION structure, too. And this leads to the daemon accessing the
already freed CLIENT structure later on ...
So now IRC_ERROR() uses the correct function Conn_Close() to correctly
free both structures.
The CONNECTION structure is cleaned up later on, and the freed CLIENT
structure can't be overwritten during normal operations, therefore this
bug normally can't crash (DoS) the service -- but you can easily hit it
when using the GCC option "-fsanitize=address", or run ngIRCd with
Valgrind.
Thanks a lot to Joseph Bisch <joseph.bisch(a)gmail.com> for discovering
and reporting this issue!
Compare: https://github.com/ngircd/ngircd/compare/91ef17aba2b0...798de94d6556
Branch: refs/heads/master
Home: https://github.com/ngircd/ngircd
Commit: d803ff052585b29defb41f7e5c3c0915f767bebc
https://github.com/ngircd/ngircd/commit/d803ff052585b29defb41f7e5c3c0915f76…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
Changed paths:
M configure.ng
Log Message:
-----------
configure.ng: Split list into separate lines
Commit: 8f0c705029501141528fbe7671e4107b4e1f395f
https://github.com/ngircd/ngircd/commit/8f0c705029501141528fbe7671e4107b4e1…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
Changed paths:
M src/portab/Makefile.ng
Log Message:
-----------
portab/Makefile: Split list into separate lines
Commit: 03acae970df0ebe713a4be791e6c75915d34a365
https://github.com/ngircd/ngircd/commit/03acae970df0ebe713a4be791e6c75915d3…
Author: Alexander Barton <alex(a)barton.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
Changed paths:
M src/ngircd/irc.c
Log Message:
-----------
User mode "C": Allow messages from servers, services, and IRC Ops
Update user mode "C" handling ("Only users that share a channel are
allowed to send messages") to behave like user mode "b" ("block private
messages and notices") and therefore allow messages from servers, services,
and IRC Operators, too.
Change proposed by "wowaname" in #ngircd, thanks!
Compare: https://github.com/ngircd/ngircd/compare/3559940e4aff...03acae970df0