Experimental IRC client, daemon and bot
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README 4.7 KiB

6 years ago
5 years ago
5 years ago
6 years ago
5 years ago
5 years ago
6 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
6 years ago
6 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125
  1. uirc3
  2. =====
  3. The unethical IRC trinity. This project consists of an experimental IRC client,
  4. daemon, and bot. It's all you're ever going to need for chatting.
  5. All of them have these potentially interesting properties:
  6. - full IPv6 support
  7. - TLS support, including client certificates
  8. - minimal dependencies
  9. - very compact and easy to hack on
  10. - permissive license
  11. degesch
  12. -------
  13. The IRC client. It is largely defined by being built on top of GNU Readline.
  14. Its interface should however feel familiar for weechat or irssi users.
  15. This is the youngest and largest application within the project. It has most of
  16. the stuff you'd expect of an IRC client, such as being able to set up multiple
  17. servers, powerful configuration system, integrated help, mIRC text formatting,
  18. CTCP queries, automatic splitting of overlong messages, autocomplete, logging
  19. to file, and command aliases.
  20. kike
  21. ----
  22. The IRC daemon. It is designed to be used as a regular user application rather
  23. than a system-wide daemon. If all you want is a decent, minimal IRCd for
  24. a small network of respectful users (or bots), or testing, this one will do it.
  25. Notable features:
  26. - TLS autodetection (why doesn't everyone have this?)
  27. - IRCop authentication through TLS client certificates
  28. - epoll/kqueue support; it should be able to handle quite a number of users
  29. - partial IRCv3 support
  30. Not supported:
  31. - server linking (which also means no services); I consider existing protocols
  32. for this purpose ugly and tricky to implement correctly
  33. - online changes to configuration; the config system from degesch could be used
  34. - limits of almost any kind, just connections and mode +l
  35. ZyklonB
  36. -------
  37. The IRC bot. It builds upon the concept of my other VitaminA IRC bot. The main
  38. characteristic of these two bots is that they run plugins as coprocesses, which
  39. allows for enhanced reliability and programming language freedom.
  40. While originally intended to be a simple C99 rewrite of the original bot, which
  41. was written in the GNU dialect of AWK, it fairly quickly became a playground
  42. where I added everything that seemed nice, and it eventually got me into writing
  43. the rest of this package.
  44. Notable features:
  45. - resilient against crashes, server disconnects and timeouts
  46. - SOCKS support (even though socksify can add that easily to any program)
  47. Building
  48. --------
  49. Build dependencies: CMake, pkg-config, help2man, awk, sh, liberty (included)
  50. Runtime dependencies: openssl, curses (degesch),
  51. readline or libedit >= 2013-07-12 (degesch)
  52. $ git clone --recursive https://github.com/pjanouch/uirc3.git
  53. $ mkdir uirc3/build
  54. $ cd uirc3/build
  55. $ cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug \
  56. -DWANT_READLINE=ON -DWANT_LIBEDIT=OFF
  57. $ make
  58. To install the application, you can do either the usual:
  59. # make install
  60. Or you can try telling CMake to make a package for you. For Debian it is:
  61. $ cpack -G DEB
  62. # dpkg -i uirc3-*.deb
  63. Note that for versions of CMake before 2.8.9, you need to prefix cpack with
  64. `fakeroot' or file ownership will end up wrong.
  65. Running
  66. -------
  67. `degesch' has in-program configuration. Just run it and read the instructions.
  68. For the rest you might want to generate a configuration file:
  69. $ zyklonb --write-default-config
  70. $ kike --write-default-config
  71. After making any necessary edits to the file (there are comments to aid you in
  72. doing that), simply run the appropriate program with no arguments:
  73. $ zyklonb
  74. $ kike
  75. `ZyklonB' stays running in the foreground, therefore I recommend launching it
  76. inside a Screen or tmux session.
  77. `kike', on the other hand, immediately forks into the background. Use the PID
  78. file or something like `killall' if you want to terminate it. You can run it
  79. as a `forking' type systemd user service.
  80. Client Certificates
  81. -------------------
  82. `kike' uses SHA1 fingerprints of TLS client certificates to authenticate users.
  83. To get the fingerprint from a certificate file in the required form, use:
  84. $ openssl x509 -in public.pem -outform DER | sha1sum
  85. Contributing and Support
  86. ------------------------
  87. Use this project's GitHub to report any bugs, request features, or submit pull
  88. requests. If you want to discuss this project, or maybe just hang out with
  89. the developer, feel free to join me at irc://anathema.irc.so, channel #anathema.
  90. Disclaimer
  91. ----------
  92. I am not an antisemitist, I'm just being an offensive asshole with the naming.
  93. And no, I'm not going to change the names.
  94. License
  95. -------
  96. `uirc3' is written by Přemysl Janouch <p.janouch@gmail.com>.
  97. You may use the software under the terms of the ISC license, the text of which
  98. is included within the package, or, at your option, you may relicense the work
  99. under the MIT or the Modified BSD License, as listed at the following site:
  100. http://www.gnu.org/licenses/license-list.html