Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.

Explain SASL access only IP ranges #430

Merged
merged 1 commit into from
Feb 14, 2020
Merged

Explain SASL access only IP ranges #430

merged 1 commit into from
Feb 14, 2020

Conversation

glguy
Copy link
Contributor

@glguy glguy commented Feb 9, 2020

No description provided.

@bigpresh
Copy link
Contributor

bigpresh commented Feb 9, 2020

Looks sensible, and a good complement to freenode/ircd-seven#182 to make the explanation of SASL-only ranges easier to find.

In fact, I wonder if this content should be moved up above the list of client configuration links, so we more fully describe what SASL auth is and why it's required from some ranges, before telling you how to set it up in your client?

@glguy
Copy link
Contributor Author

glguy commented Feb 9, 2020

@bigpresh my reasoning for putting it at the bottom of the page is that I think most users are configuring SASL voluntarily because they want a cloak applied upon connection rather than because they are acting through a restricted IP.

I'm open to having it wherever it makes sense to everyone though

@tomaw tomaw merged commit d168ffb into freenode:master Feb 14, 2020
@glguy glguy deleted the patch-1 branch February 14, 2020 22:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants