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.adoc 4.7KB

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