SASL EXTERNAL doesn't seem to work properly

Board for discussions around the Ambassador chat client and extension.

Moderator: Isengrim

Post Reply
User avatar
Posts: 346
Joined: 2020-11-03, 06:47
Location: Philippines

SASL EXTERNAL doesn't seem to work properly

Post by jobbautista9 » 2021-04-13, 05:39

So I tried to use my own certificate as a means of authentication to freenode. I imported my cert into the Certificate Manager, and when I connect to freenode, it asks me whether to use my certificate, which is expected. But what I did not expect is that it still asks me for a password. I disabled "Use SASL authentication" in the preferences, and only used my certificate instead, but now I can't connect, because my IP is banned for users not using SASL.

What's even weird is that when I connect with both certificate and password, and /whois myself, it shows my certificate fingerprint. So it sees my certificate.

My certificate has a key size of 16384-bits long, maybe that could be a factor?

I'm using the standalone client.
Cyndaquil is the best starter, except in Pokemon Mystery Dungeon, which sucks. I still love PMD though!

Developer of Ambassador in Window Menu, BrowserTickTock, CacheSwitch, Chrome Navigator, Cite4Wiki, Clickity Touch 'n Push, ColorPili, EditDatContent, EditDatTitle, Esrever, Go Menu, User Agent Status, Website Navigation Bar, and Yet Another about:config Helper.

My PGP public key (My copy on

Avatar by @MaxiOrphy of Instagram.

Post Reply