See IRCv3 Specifications to learn more about IRCv3 capabilities. The second guide is the advanced guide, which goes over the changes made to these configs as individual changes with the. After getting that set up the rest of the guide will go over how to use these configs. It starts by handing you a git repo of weechat config files to give you a better default. The first part is all about how to use weechat. Capabilities supported by WeeChat are: account-notify, away-notify, cap-notify, extended-join, multi-prefix, server-time, userhost-in-names. This weechat guide is broken into two parts. The last line request some IRCv3 capabilities. set irc.server_default.capabilities "account-notify,away-notify,cap-notify,multi-prefix,server-time,znc.in/self-message" set irc.server_default.sasl_username r3m If you are developing a WeeChat relay client and want to be compatible with all WeeChat versions, you should support both separators (for example if a user with WeeChat 2.5 runs /upgrade to a version 2.6, both separators could be used at same. With WeeChat 2.6, a tilde is used to separate foreground from background color. If you aren't adverse to commandline interface / TUI clients, perhaps give WeeChat a try Its /Filter plugin/command is quite versatile and would allow what you want and more. Network Default settings /set irc.server_default.sasl_mechanism PLAIN (1) The use of comma as separator was used until WeeChat 2.5. As /ignore is (usually) a client-side feature, it really depends on the IRC client you use. so I am still learning this stuff.You need at least WeeChat 2.8-dev Enable mouse /mouse enable Is my assumption correct? Does this mean that Weechat has a bug? I'm fairly new to CA's, certificates etc. This would also explain why the problems with connecting to the relay vanish when I add the intermediate AlphaSSL certificate to the system's certificates. And this is probably not a problem in the browser, because it ships with that intermediate certificate. If I read this correctly, then Weechat apparently isn't sending out the intermediate certificate, while node.js is. Verify error:num=21:unable to verify the first certificate Verify error:num=20:unable to get local issuer certificate A recommended (but not mandatory) X terminal emulator for running WeeChat is rxvt-unicode. I:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CAĪnd here is what happens if I try to open a TLS socket to Weechat's relay: CONNECTED(00000003) I:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2ġ s:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2 Here's what happens when I access the node.js server (slightly modified for privacy reasons): CONNECTED(00000003)ĭepth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CAĭepth=1 C = BE, O = GlobalSign nv-sa, CN = AlphaSSL CA - SHA256 - G2ĭepth=0 C = DE, OU = Domain Control Validated, CN = Ġ s:/C=DE/OU=Domain Control Validated/CN= I used openssl s_client -connect to get some information. crt file to /usr/share/ca-certificates and then run dpkg-reconfigure ca-certificates to be able to open a TLS socket to the Weechat relay. I had to manually copy the intermedia CA certificate. What's even weirder is that browsers do not seem to have this problem, since Glowing Bear (HTML5 WeeChat relay client) does not have this problem. For some reason, when I try to open a TLS socket to it, it appears that the intermediate EuroDNS AlphaSSL CA certificate isn't sent out properly, because the clients report errors that they can't verify my domain's certificate. , ldvx version 12: added ignoretags to avoid colorizing nicks if tags are present, nesthib version 11: inputtextdisplay hook and modifier to colorize nicks in input bar, xt version 10: hook config option for updating blacklist, xt version 0.9: hook new. Weechat's relay protocol, however, doesn't. What is strange is that I can access the node.js server through HTTPS without problems by using any HTTPS client. maybe try debugging with sclient or similar things. maybe try using a reverse proxy sunch nginx or stunnel. I also have my own domain, which I registered at EuroDNS, as well as an AlphaSSL certificate, also from EuroDNS.īoth Weechat's relay protocol and node.js are set up to use TLS (node.js is configured to refuse HTTP requests, only HTTPS is allowed). try launching weechat with a clean profile ( weechat -d /tmp/foo) try connecting to a weechat on a different machine. Changes proposed in this specification will also fix the following issues: 398: autocomplete. Purpose of this specification is to make many identifiers case sensitive in data objects managed by the user, API and internal functions. I have a private server at home that runs a node.js instance and weechat. Many identifiers are case insensitive in WeeChat and should not be.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |