Skip to content
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

Improve error messages on OPER/CHALLENGE failure #420

Merged
merged 3 commits into from
Nov 6, 2023
Merged

Conversation

aaronmdjones
Copy link
Member

No description provided.

Copy link
Contributor

@jillest jillest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These may not have been omissions but deliberately ensuring existing monitor bots and scripts kept working. EFNet had quite a few of them.

This doesn't mean solanum should not improve this, though.

I suspect this is a copy/paste omission when duplicating the code from
modules/m_oper.c when it was created.
…d o:line

The snotice sent to other opers can be misleading. For example, it will say
host mismatch even if the host is correct but the username is wrong, or if
the oper name given does not exist in the configuration.
The snotice sent to other opers can be misleading. For example, it will say
host mismatch even if the host is correct but the username is wrong, or if
the oper name given does not exist in the configuration.
@spb spb merged commit fd241b5 into main Nov 6, 2023
9 checks passed
@spb spb deleted the amdj/oper-snotice-fixups branch November 6, 2023 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants