-
Notifications
You must be signed in to change notification settings - Fork 65
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Store capability values from CAP v3.2 handshakes + honor SASL v3.2 me…
…chanism lists (#322) * Store capability values in 'CAP LS 302' negotiations. So it can be retrieved later (eg. to know what SASL mechanisms are available). https://ircv3.net/specs/extensions/capability-negotiation.html#the-cap-ls-subcommand * Honor SASL v3.2 mechanism lists From https://ircv3.net/specs/extensions/sasl-3.2#usage : > Clients SHOULD pick a mechanism present in the CAP LS reply they get from the server and attempt to use that mechanism for authentication after they request the sasl capability. * Update handler.network.cap.available on CAP NEW/DEL * Clear available caps when connecting && cleanup sasl code Co-authored-by: ItsOnlyBinary <[email protected]>
- Loading branch information
1 parent
6effe43
commit a2697c9
Showing
3 changed files
with
29 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters