New issue
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 an option to stop the connection when SASL fails. #514
Conversation
I guess it's fine, I'm a bit sceptic of the internal flag and related code duplication but whatever. @dequis ? |
(should update abi constant) |
@@ -79,6 +79,7 @@ struct _IRC_SERVER_REC { | |||
int cap_complete:1; /* We've done the initial CAP negotiation */ | |||
|
|||
guint sasl_timeout; /* Holds the source id of the running timeout */ | |||
int sasl_success:1; /* Did we authenticate successfully ? */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put this after cap_complete:1
, otherwise it won't take advantage of the bitfield.
That seems ok, but i'm a bit worried about that |
Should the policy also be enforced on a global "per-client" level? |
Renaming to _on_failure seems ok (but i don't feel too strongly about it)
What do you mean? It looks like a global setting to me. I think that's fine. |
Ack. I think I wrote the wrong question: should it be possible to control this on a per connection level. |
I don't think we need to have this as a per-connection setting. It's more of a personal preference, similar to "do i care about appearing decloaked or not" |
Should this also set |
Maybe the sasl failure is temporary |
No description provided.