From: Connor Taffe <cpaynetaffe@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Acme IRC Basic SASL Support
Date: Sat, 20 Feb 2021 19:21:39 -0600 [thread overview]
Message-ID: <93D8FA28-1CE3-46BC-BEF6-893C6D50AD6C@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
I took Russ’s Irc client at https://swtch.com/irc/ <https://swtch.com/irc/> and added enough SASL PLAIN
support to access Freenode so that I could use it as my IRC client.
It’s available at https://github.com/cptaffe/airc <https://github.com/cptaffe/airc>.
I documented the flow as best I could in this commit <https://github.com/cptaffe/airc/commit/d5aa833e6f6f874e664f938ab619aac30ae55f77> , and I’d appreciate constructive
feedback on how to improve the implementation or add more comprehensive SASL support.
My initial idea was to support CertFP, but I had difficulty getting tlsClient in libsec to work,
and reading through the code I’m not sure it supports sending the client certificate
(there’s a bit which indicates it always sends an empty cert).
Another peculiarity is that mk all fails with a symbol error because it builds Irc.o and irc.o
from irc.c on macOS, I believe this is to do with case-insensitivity in Apple’s FS. To get
around this, just run the 9l command by hand without Irc.o.
After mk install, running "Irc -n nick -p passed irc.freenode.net <http://irc.freenode.net/>" should attempt SASL PLAIN.
Speaking of IRC, is there a plan9port IRC channel?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tb7203430b1bb75f4-M26d3edd1bad27ee619cfaeaf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2598 bytes --]
next reply other threads:[~2021-02-21 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 1:21 Connor Taffe [this message]
2021-02-21 8:47 ` [9fans] " cpaynetaffe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93D8FA28-1CE3-46BC-BEF6-893C6D50AD6C@gmail.com \
--to=cpaynetaffe@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).