9pfs/solanum-vs-hackint-and-charybdis
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Comparing some git repos with each other
3598 commits 4 branches 0 tags 40 MiB
C 92.3%
Shell 5.3%
M4 1.5%
Makefile 0.4%
Lex 0.2%
Other 0.3%
Find a file
Ed Kellett 7b6410135b
m_modules: make modreload work like restart 
/modrestart used to be implemented as a normal command and could crash
when used remotely because it would reload m_encap, which was on the
call stack at the time. This was fixed in 41390bfe5f. However,
/modreload has exactly the same problem, so I'm giving it the
same treatment.

Incidentally: This bug was first discovered in ircd-seven, where the
`/mod*` commands themselves live in the core, so m_encap was the only way
the crash could happen (and it didn't most of the time, because m_encap
would only be moved if you got unlucky). But `/mod*` are in modules in
charybdis, so /modrestart would have unloaded the code it was in the
middle of executing. With that in mind, I'm not sure how it ever
appeared to work.
2019-11-17 18:01:51 +00:00
authd librb: Fix type of dst for rb_inet_pton_sock() 2019-08-31 16:10:50 +01:00
bandb Fix Clang 6 compiler warnings 2019-09-15 11:28:48 +01:00
doc Propagate OPER 2019-09-13 10:08:27 +01:00
extensions Merge pull request #287 from edk0/filter 2019-10-22 18:33:51 +00:00
help Add help for GRANT 2019-09-15 00:35:55 +01:00
include m_modules: make modreload work like restart 2019-11-17 18:01:51 +00:00
ircd m_modules: make modreload work like restart 2019-11-17 18:01:51 +00:00
librb librb: Fix nossl 2019-09-15 12:33:56 +01:00
m4 Remove more $Id tags. 2016-03-06 02:58:32 -06:00
modules m_modules: make modreload work like restart 2019-11-17 18:01:51 +00:00
scripts makerelease: fix DATECODE output 2016-05-14 17:28:49 -05:00
ssld ssld: avoid clang static analysis warning 2017-08-04 20:51:53 +01:00
tests tests/Makefile.am: check-local: don't depend on extensions/* 2019-10-07 03:49:00 +00:00
testsuite testsuite: Update startall.sh 2016-03-28 00:09:01 -04:00
tools mkpasswd: avoid strdup(NULL) and the like if rb_crypt() fails 2016-12-20 17:29:37 +00:00
wsockd wsockd: avoid clang static analysis warning 2017-07-29 22:39:53 +01:00
.appveyor-build.sh appveyor: make the build less hacky 2016-03-25 18:25:00 -05:00
.appveyor.yml appveyor: correct version 2016-05-15 01:13:50 +00:00
.gitignore tests: Verify behaviour if services authenticates a user after SASL is aborted 2019-02-23 13:02:15 +00:00
.mailmap mailmap: Sam is Christine now apparently. 2016-03-17 14:48:46 -05:00
.travis.yml Add hyperscan to CI deps 2019-10-06 19:35:17 +01:00
autogen.sh *sigh* comment these out until travis is fixed. 2016-04-10 17:12:42 -05:00
configure.ac Fix build when hyperscan is missing 2019-10-06 19:24:34 +01:00
CREDITS CREDITS: update to match reality 2017-08-17 08:37:10 +03:00
LICENSE Remove more $Id tags. 2016-03-06 02:58:32 -06:00
Makefile.am tests: add C TAP harness 2017-07-29 22:46:05 +01:00
NEWS.md Version 4.1.3-dev 2019-08-31 21:14:27 +01:00
README.md Revert "no really, it's dead people" 2017-07-27 18:51:24 +01:00
shtool Add these for now until travis actually gets their shit together. 2016-04-10 17:07:33 -05:00

README.md

charybdis POSIX Build Status Windows Build Status

Charybdis is an IRCv3 server designed to be highly scalable. It implements IRCv3.1 and some parts of IRCv3.2.

It is meant to be used with an IRCv3-capable services implementation such as Atheme or Anope.

necessary requirements

  • A supported platform
  • A working dynamic library system
  • A working lex and yacc - flex and bison should work

platforms

Charybdis is designed with portability in mind, but does not target older systems nor those of solely academic interest.

Do note that operating systems are only supported if they are supported by their vendor.

Tier 1

These platforms are the best supported, and should always work. They are actively tested. If you encounter problems, please file a bug.

  • FreeBSD 10.x and above (i386 and amd64)
  • Linux 2.6.x and above with glibc or musl (i386, x86_64, and ARM)
  • Mac OS X 10.7 and above
  • Windows Vista/Server 2008 and above (x86 or x64)

Tier 2

These platforms are supported and occasionally tested, and most features should work, but this is not guaranteed. If you find any problems, file a bug, but as these are not regularly tested platforms, a timely resolution may not be possible.

  • DragonflyBSD 4.4 and above (i386)
  • Linux with uClibc (i386 or x86_64)
  • NetBSD 6.1.x and above (i386, amd64)
  • OpenBSD 5.6 and above (i386, amd64)
  • Solaris 10 and above (i386)

Tier 3

Anything else that hasn't been tested. Charybdis may or may not work on it; patches welcome if they don't.

platform specific errata

These are known issues and workarounds for supported platforms.

  • **Mac OS X and macOS **: you must set the LIBTOOLIZE environment variable to point to glibtoolize before running autogen.sh: $ brew install libtool $ LIBTOOLIZE="/opt/local/bin/glibtoolize" $ export LIBTOOLIZE $ ./autogen.sh

  • FreeBSD: if you are compiling with ipv6 you may experience problems with ipv4 due to the way the socket code is written. To fix this you must: "sysctl net.inet6.ip6.v6only=0"

  • Solaris: you may have to set your PATH to include /usr/gnu/bin and /usr/gnu/sbin before /usr/bin and /usr/sbin. Solaris's default tools don't seem to play nicely with the configure script.

building from git

We no longer supply a prebuilt configure script in git, due to use of automake and libtool causing problems. You will need to run autogen.sh to build the autotools files prior to building charybdis.

feature specific requirements

  • For SSL/TLS client and server connections, one of:

    • OpenSSL 1.0.0 or newer (--enable-openssl)
    • LibreSSL (--enable-openssl)
    • mbedTLS (--enable-mbedtls)
    • GnuTLS (--enable-gnutls)

  • For certificate-based oper CHALLENGE, OpenSSL 1.0.0 or newer. (Using CHALLENGE is not recommended for new deployments, so if you want to use a different TLS library, feel free.)

  • For ECDHE under OpenSSL, on Solaris and RHEL/Fedora (and its derivatives such as CentOS) you will need to compile your own OpenSSL on these systems, as they have removed support for ECC/ECDHE. Alternatively, consider using another library (see above).

tips

  • To report bugs in charybdis, visit us at irc.charybdis.io #charybdis

  • Please read doc/index.txt to get an overview of the current documentation.

  • Read the NEWS file for what's new in this release.

  • The files, /etc/services, /etc/protocols, and /etc/resolv.conf, SHOULD be readable by the user running the server in order for ircd to start with the correct settings. If these files are wrong, charybdis will try to use 127.0.0.1 for a resolver as a last-ditch effort.

git access

  • The Charybdis GIT repository can be checked out using the following command: git clone https://github.com/charybdis-ircd/charybdis

  • Charybdis's GIT repository depot can be browsed over the Internet at the following address: https://github.com/charybdis-ircd/charybdis