- DALnet-src - nomad.dal.net

Installation of Bahamut
by chipmunk＠keemail.me 08 Jan '23

08 Jan '23

Greetings Support, I installed bahamut today for testing purpose, but I need help on which folder to perform ./configure command. bahamut@linux:~/bahamut-2.2.2$ ./configure bash: ./configure: No such file or directory

2 1

Channel Mode Suggestion
by coding＠teamscript.net 23 Oct '21

23 Oct '21

Hello, i would like to know for technical and aesthetic questions to change channels modes? In this case the +e, -e, +j, -j mode and the other modes to modify them because it floods the living room. Concrete example below: [00:25:31] × Mode: KoolKain / +day 10:60 [00:25:32] × Mode: KoolKain / +day 10:60 [00:25:32] × Mode: KoolKain / +day 10:60 [00:25:33] × Mode: KoolKain / +day 10:60 [00:25:38] × Mode: KoolKain / -j [00:25:39] × Mode: KoolKain / -j [00:25:40] × Mode: KoolKain / -j [00:25:41] × Mode: KoolKain / -j [00:25:41] × Mode: KoolKain / -j [00:25:42] × Mode: KoolKain / -j [00:25:42] × Mode: KoolKain / -j I managed to change the mode + and - n, t, i, s, p, c, k, M, R, E Thank you. Friendly

1 0

Announcing Bahamut v2.2.0 release
by Emilio Escobar 08 Jul '21

08 Jul '21

Hi folks, From the coders@ team, wanted to proudly announce that we have just released v2.2.0. Key features include host masking and half-ops. Full details and change log included here: https://github.com/DALnet/bahamut/releases/tag/v2.2.0 Please reach out to us via #bahamut if you have any questions and report any bugs/requests via GitHub. Cheers, Emilio /skill - merlin.* admin & coders staff.

1 0

Bahamut release 2.1.5 announcement
by Emilio Escobar 28 May '20

28 May '20

Hi Bahamut community, The DALnet Coders Team is happy to announce that we have just released v2.1.5 of bahamut. This version includes quite a bit of new features and bug fixes as listed: Check for local openssl installation first & rpath it too (PR 90) USE_SYSLOG: Include nick!user@host in SSL errors (PR 91) Add IRCERR_SSL to irc_get_sockerr() function (PR 91) Treat normal connection closes by SSL users as such (PR 91) Added new EXEMPT_WEBIRC XFLAG to exempt webirc users (PR 96) Add half-ops support (PR 97) Small fix to spamfilter's IDs (PR 98) Check for default install directories in the configure script (PR 99) Don't show servers to non-opers if show_links isn't enabled (PR 100) Add the list of required packages to INSTALL (PR 102) Add missing names to doc/Bahamut-team (PR 102) Change SVSUHM to support optional parameter to control umode +H (PR 95) Add NO_LOCAL_CMODE_h define to disable local cmode +h/-h (PR 97) Small fix to m_aj() for JOIN 0 (PR 104) Fix for a potential bug on AJ where 0 (partall) argument is used (PR 112) Fix a bug on QUIT where xflags weren't always checked (PR 113) Improve user host-masking support for WHO & RWHO (PR 122) Add SVSCTRL command to let services control services join requests (PR 130) Added MAX_MSG_TIME XFLAG, sets a maximum amount of messages that can be sent to a channel in x seconds (PR 92) Add in MAX_MSG_TIME to DEFAULT for m_svsxcf (PR 101) Notify opers if the KILL flag was used on a spamfilter (PR 106) Hide user's real host during topic changes if hostmasked (PR 117) Fix our incorrect handling of IRC color code sequences (PR 118) Update bahamut development credits with current team members (PR 119) Fix SSL regression bug; only use libcrypto-compat code if SSL is enabled (thanks Colby Ross) (PR 120) Add documentation for connect block "uflags" token (PR 121) Add missing "P" to CHANMODES list (thanks, RuneB) (PR 125) Fix /whois channel name truncation (thanks, brandon) (PR 126) Allow squelched users to send messages to the services and stats addresses (PR 127) Specify which channel the user cannot join (+R) or speak in (+M) (PR 128) Fix compilation issues with OpenSSL version < 1.1.0 (PR 153) Add AUDITORIUM flag to CHANMODES to comply with RFC (PR 108) Spelling correction to rehash notification (PR 93) Release tarball information: Link: http://www.dal.net/download/bahamut-2.1.5.tar.gz <http://www.dal.net/download/bahamut-2.1.5.tar.gz> SHA1 sum: 242d8cc6783804abee6b5e34f07b47925d021ccf MD5 sum: 7fd7864ad03a2ce025dc8e0f161ec296 We would like to thank everyone who contributed towards this release. Without the community involvement, this would have not been possible. Please make sure to collaborate with the team via our GitHub page: https://github.com/DALnet/bahamut <https://github.com/DALnet/bahamut> Regards, ——— Emilio / skill skill(a)dal.net

1 0

I hope all is well
by sloopycanihaveanewnamesir 20 May '20

20 May '20

I hope you had a good weekend. I'm glad we had a chance to chat at the convention. I am writing to ask/enquire/let you know/confirm/check/invite you to/to update you on/ask for a favor... Sorry it took me so long to get back to you. The parts in bold/in red/in blue are my comments/are the changes we made. Please find my two main questions below. I didn't/don't fully understand [something]. Could you please explain that again? Please keep me informed/posted/updated/in the loop. Let me know if this is OK with you. I'm sorry but it's out of my hands Any feedback you can give me on this would be greatly/highly/much appreciated. ... please do not hesitate to contact me. Sorry I couldn't be of more help. Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

[SPAM] Crash ircd
by Abc 20 May '20

20 May '20

I have a crash problem on the bahamut-2.1.4 version in syslog I have this: May 20 08:57:34 vps817615 kernel: [46927.436280] ircd [6234]: segfault at 57 ip 00007ff2d43ce927 sp 00007ff2d27bbd68 error 6 in libc-2.19.so [7ff2d4337000 + 1a1000] have you ever encountered this problem ? Cordially. KoolKain -- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus Spam detection software, running on the system "momomail.dal.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I have a crash problem on the bahamut-2.1.4 version in syslog I have this: May 20 08:57:34 vps817615 kernel: [46927.436280] ircd [6234]: segfault at 57 ip 00007ff2d43ce927 sp 00007ff2d27bbd68 error 6 in libc-2.19.so [7ff2d4337000 + 1a1000] [...] Content analysis details: (5.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.4319] 0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) -0.5 CUSTOM_IRC_DOWNSCORE BODY: dal.net IRC custom word whitelist 0.0 HTML_IMAGE_ONLY_32 BODY: HTML: images with 2800-3200 bytes of words 0.0 HTML_MESSAGE BODY: HTML included in message 1.0 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS 3.0 HEXHASH_WORD Multiple instances of word + hexadecimal hash 0.4 KHOP_HELO_FCRDNS Relay HELO differs from its IP's reverse DNS 0.0 T_REMOTE_IMAGE Message contains an external image

2 1

build error with --disable-openssl set
by Colby Ross 09 Feb '20

09 Feb '20

Hello. I am unable to build bahamut-2.1.4 from source if I pass --disable-openssl to configure. It configures, but fails on the make phase. I am using irc for a ham radio project that does not require ssl. Builds with ssl enabled work fine with some of the same compiler warnings, but does not build with it disabled. The output is below. Thank you. Building src make[1]: Entering directory '/root/b/bahamut-2.1.4/src' gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c blalloc.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c bsd.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c channel.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c clientlist.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c clones.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c confparse.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c fdlist.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c fds.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c hash.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c hide.c channel.c: In function ‘send_channel_modes.part.12’: channel.c:1602:39: warning: ‘%s’ directive writing up to 511 bytes into a region of size between 387 and 501 [-Wformat-overflow=] ircsprintf(buf, ":%s SJOIN %ld %s %s %s :", me.name, ^~ chptr->channelts, chptr->chname, modebuf, parabuf); ~~~~~~~ In file included from ../include/h.h:32, from channel.c:26: ../include/ircsprintf.h:10:20: note: ‘sprintf’ output between 15 and 1151 bytes into a destination of size 512 #define ircsprintf sprintf channel.c:1602:5: note: in expansion of macro ‘ircsprintf’ ircsprintf(buf, ":%s SJOIN %ld %s %s %s :", me.name, ^~~~~~~~~~ gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c inet_addr.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c ircd.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c klines.c gcc -I../include -g -O2 -Wall -fno-strict-aliasing -fgnu89-inline -c libcrypto-compat.c ircd.c: In function ‘s_die’: ircd.c:187:24: warning: ‘/.maxclients’ directive writing 12 bytes into a region of size between 1 and 4096 [-Wformat-overflow=] ircsprintf(tmp, "%s/.maxclients", dpath); ^~~~~~~~~~~~ In file included from ../include/h.h:32, from ircd.c:40: ../include/ircsprintf.h:10:20: note: ‘sprintf’ output between 13 and 4108 bytes into a destination of size 4096 #define ircsprintf sprintf ircd.c:187:5: note: in expansion of macro ‘ircsprintf’ ircsprintf(tmp, "%s/.maxclients", dpath); ^~~~~~~~~~ libcrypto-compat.c:14:24: error: unknown type name ‘DH’ void DH_get0_pqg(const DH *dh, ^~ libcrypto-compat.c:15:24: error: unknown type name ‘BIGNUM’ const BIGNUM **p, const BIGNUM **q, const BIGNUM **g) ^~~~~~ libcrypto-compat.c:15:42: error: unknown type name ‘BIGNUM’ const BIGNUM **p, const BIGNUM **q, const BIGNUM **g) ^~~~~~ libcrypto-compat.c:15:60: error: unknown type name ‘BIGNUM’ const BIGNUM **p, const BIGNUM **q, const BIGNUM **g) ^~~~~~ libcrypto-compat.c: In function ‘DH_get0_pqg’: libcrypto-compat.c:18:16: error: request for member ‘p’ in something not a structure or union *p = dh->p; ^~ libcrypto-compat.c:20:16: error: request for member ‘q’ in something not a structure or union *q = dh->q; ^~ libcrypto-compat.c:22:16: error: request for member ‘g’ in something not a structure or union *g = dh->g; ^~ libcrypto-compat.c: At top level: libcrypto-compat.c:25:17: error: unknown type name ‘DH’ int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g) ^~ libcrypto-compat.c:25:25: error: unknown type name ‘BIGNUM’; did you mean ‘SIGBUS’? int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g) ^~~~~~ SIGBUS libcrypto-compat.c:25:36: error: unknown type name ‘BIGNUM’; did you mean ‘SIGBUS’? int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g) ^~~~~~ SIGBUS libcrypto-compat.c:25:47: error: unknown type name ‘BIGNUM’; did you mean ‘SIGBUS’? int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g) ^~~~~~ SIGBUS libcrypto-compat.c:54:24: error: unknown type name ‘DH’ void DH_get0_key(const DH *dh, const BIGNUM **pub_key, const BIGNUM **priv_key) ^~ libcrypto-compat.c:54:38: error: unknown type name ‘BIGNUM’ void DH_get0_key(const DH *dh, const BIGNUM **pub_key, const BIGNUM **priv_key) ^~~~~~ libcrypto-compat.c:54:62: error: unknown type name ‘BIGNUM’ void DH_get0_key(const DH *dh, const BIGNUM **pub_key, const BIGNUM **priv_key) ^~~~~~ libcrypto-compat.c: In function ‘DH_get0_key’: libcrypto-compat.c:57:22: error: request for member ‘pub_key’ in something not a structure or union *pub_key = dh->pub_key; ^~ libcrypto-compat.c:59:23: error: request for member ‘priv_key’ in something not a structure or union *priv_key = dh->priv_key; ^~ libcrypto-compat.c: At top level: libcrypto-compat.c:62:17: error: unknown type name ‘DH’ int DH_set0_key(DH *dh, BIGNUM *pub_key, BIGNUM *priv_key) ^~ libcrypto-compat.c:62:25: error: unknown type name ‘BIGNUM’; did you mean ‘SIGBUS’? int DH_set0_key(DH *dh, BIGNUM *pub_key, BIGNUM *priv_key) ^~~~~~ SIGBUS libcrypto-compat.c:62:42: error: unknown type name ‘BIGNUM’; did you mean ‘SIGBUS’? int DH_set0_key(DH *dh, BIGNUM *pub_key, BIGNUM *priv_key) ^~~~~~ SIGBUS libcrypto-compat.c:83:19: error: unknown type name ‘DH’ int DH_set_length(DH *dh, long length) ^~ make[1]: *** [Makefile:49: libcrypto-compat.o] Error 1 make[1]: *** Waiting for unfinished jobs.... klines.c: In function ‘klinestore_compact’: klines.c:479:38: warning: ‘%s’ directive output may be truncated writing up to 4095 bytes into a region of size 512 [-Wformat-truncation=] ircsnprintf(buf1, sizeof(buf1), "%s/.klines_c", dpath); ^~ ~~~~~ In file included from ../include/h.h:32, from klines.c:42: ../include/ircsprintf.h:15:21: note: ‘snprintf’ output between 11 and 4106 bytes into a destination of size 512 #define ircsnprintf snprintf klines.c:479:5: note: in expansion of macro ‘ircsnprintf’ ircsnprintf(buf1, sizeof(buf1), "%s/.klines_c", dpath); ^~~~~~~~~~~ ircd.c: In function ‘main’: ircd.c:787:24: warning: ‘/.maxclients’ directive writing 12 bytes into a region of size between 1 and 4096 [-Wformat-overflow=] ircsprintf(tmp, "%s/.maxclients", dpath); ^~~~~~~~~~~~ In file included from ../include/h.h:32, from ircd.c:40: ../include/ircsprintf.h:10:20: note: ‘sprintf’ output between 13 and 4108 bytes into a destination of size 4096 #define ircsprintf sprintf ircd.c:787:5: note: in expansion of macro ‘ircsprintf’ ircsprintf(tmp, "%s/.maxclients", dpath); ^~~~~~~~~~ klines.c: In function ‘klinestore_init’: klines.c:556:60: warning: ‘%s’ directive output may be truncated writing up to 4095 bytes into a region of size 512 [-Wformat-truncation=] ircsnprintf(journalfilename, sizeof(journalfilename), "%s/.klines", dpath); ^~ ~~~~~ In file included from ../include/h.h:32, from klines.c:42: ../include/ircsprintf.h:15:21: note: ‘snprintf’ output between 9 and 4104 bytes into a destination of size 512 #define ircsnprintf snprintf klines.c:556:5: note: in expansion of macro ‘ircsnprintf’ ircsnprintf(journalfilename, sizeof(journalfilename), "%s/.klines", dpath); ^~~~~~~~~~~ make[1]: Leaving directory '/root/b/bahamut-2.1.4/src' Building doc make[1]: Entering directory '/root/b/bahamut-2.1.4/doc' make[1]: Nothing to be done for 'build'. make[1]: Leaving directory '/root/b/bahamut-2.1.4/doc' Building tools make[1]: Entering directory '/root/b/bahamut-2.1.4/tools' gcc -I../include -g -O2 -Wall -fno-strict-aliasing -c mkpasswd.c gcc -Wl,-export-dynamic -o mkpasswd mkpasswd.o -lz -lssl -lcrypto -ldl -lcrypt -lresolv -lnsl make[1]: Leaving directory '/root/b/bahamut-2.1.4/tools' ****************************************************************************** * For help with bahamut, please refer to http://bahamut.dal.net/ * * If you encouter serious security related bugs, please mail coders(a)dal.net * * For other bug reports and inquiries, please mail dalnet-src(a)dal.net * * Thank you for choosing Bahamut! - The DALnet coding team * ******************************************************************************

2 1

SSL Support
by Jacob Cowen 01 Nov '19

01 Nov '19

Good Morning! My name is Jacob Cowen and I am an engineer/tester for the Navy. I am attempting to provide a solution to replace existing chat services and Bahamaut was introduced to me as an option. The DALNet introduction states that Bahamut 2.x supports many newer IRCd features such as SSL encryption. This section is critical as Bahamut needs to provided S2S encryption/security as well as C2S. Is there a section where this is written out how to implement and configure security/encryption or is there someone who can spell it out for me? Thank you and have a great day! V/r Jacob Cowen Systems Engineer, KES, Inc. NIWC Pacific, Code 53623, PMW 160 661.706.8378 NIPR: <mailto:jcowen@spawar.navy.mil> jcowen(a)spawar.navy.mil Work: <mailto:jcowen@kes.com> jcowen(a)kes.com

2 1

Keeptopic.
by Hadi FR 23 Sep '19

23 Sep '19

Hello, I tried to assist a user in #help today with a topic command, and he says that the channel has Sticky Topic in the options which means "Keeptopic" is already ON. Based on /ChanServ HELP SET_KEEPTOPIC and the Documents we have for ChanServ. While enabling Keeptopic option to a channel that means the channel will keep the topic until someone recreate another topic. Unfortunately, I tested this by myself to the channel #Fiuba that the user mentioned to me today, and I still dont see the Keeptopic options doing the required function. Once everyone leave the channel. The topic become empty, is that normal ? Thank you regards, h -------------------------------------------------------------------- DALnet Documentation Team - Member

1 0

Bahamut 2.1.4 release
by Emilio Escobar 28 Nov '18

28 Nov '18

Hi everyone, We're pleased to announce the release of Bahamut 2.1.4. With it it includes some bug fixes including the fixing of a security bug. We highly encourage everyone to test/upgrade based on individual and/or network upgrade procedures. More information here: https://www.dal.net/news/shownews.php?id=160 regards, Emilio DALnet Coders

1 0