We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for SASL auth to the bot.
Here is the spec: https://ircv3.net/specs/extensions/sasl-3.1.html
Steps to authenticate successfully (and assuming no ircd errors):
CAP REQ :sasl
CAP ACK :sasl
AUTHENTICATE PLAIN
AUTHENTICATE +
AUTHENTICATE <base64 encoded 'username\0username\0password'> SASL PLAIN
903 :SASL authentication successful
CAP END
Each step would need its own error handling and then fallback to nickserve auth or just have users set which auth method to use.
The text was updated successfully, but these errors were encountered:
This feature depends on the bot's ability to respond to events other than privmsg, so I guess it's blocked until the event reaction stuff is reworked.
Sorry, something went wrong.
No branches or pull requests
Add support for SASL auth to the bot.
Here is the spec: https://ircv3.net/specs/extensions/sasl-3.1.html
Steps to authenticate successfully (and assuming no ircd errors):
CAP REQ :sasl
CAP ACK :sasl
AUTHENTICATE PLAIN
if ACK comes backAUTHENTICATE +
responseAUTHENTICATE <base64 encoded 'username\0username\0password'> SASL PLAIN
request903 :SASL authentication successful
responseCAP END
messageEach step would need its own error handling and then fallback to nickserve auth or just have users set which auth method to use.
The text was updated successfully, but these errors were encountered: