Skip to content

SASL EXTERNAL does not work (SASL username + password works but we usually use a certifcate)Β #335

Description

@a-diker

SASL EXTERNAL not included as a feature for ircv3 [ plain (+) but external (-) ]

This is a very important feature for new servers and old servers that require extra certs for connections and authentication.
Mainly authentication, as passwords are not recommended.

Some quick examples:gui interface has the following sasl support, and the text field
but if requirement even external sasl support for the: example of extra authentication on a network like my_spun_up_IRCNETWORK.irc. client has no option or selection or console support for SASL External after research and a deeper look.

sasl external example in the field

This service requires public-key SASL authentication using either the EXTERNAL or ECDSA-NIST256P-CHALLENGE (but not PLAIN) mechanisms.

++++ See my guide for setting up CertCP if required although not important.

**Some examples of implementation: **

Required Authentication

Some clients lack SOCKS4a or later support. In this case the user will need to change your torrc file to map a private IP address the service address instead and disable TLS hostname verification in your client.

Wonderful application but would be glad to help!

SASL External into this client πŸ‘ would be a boost!

Want to add personally or with the help of creator/others same ircv3 support as weechat for unix or linux based systems.

Support within Limechat client for IRCv3.
Limechat SASL External: No
Limechat SASL Plain: Yes
Limechat SCRAM-SHA-256: No

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions