-
Notifications
You must be signed in to change notification settings - Fork 29
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
LOGINDISABLED
capability: MUST not allow LOGIN
#32
Comments
This was referenced Nov 23, 2021
nevans
changed the title
LOGINDISABLED capability: MUST not allow login
Feb 17, 2023
LOGINDISABLED
capability: MUST not allow LOGIN
nevans
added a commit
that referenced
this issue
Jun 27, 2024
This may be considered a "breaking change", but it should have no negatative effect on well behaved servers. This should merely change a NoResponseError into a LoginDisabledError. However, some broken servers have been known to hang indefinitely when issued a +CAPABILITY+ command prior to authentication. For those servers, wo offer the `enforce_logindisabled` config option. Fixes #32.
nevans
added a commit
that referenced
this issue
Jun 27, 2024
This may be considered a "breaking change", but it should have no negative effect on well behaved servers. This should merely change a NoResponseError into a LoginDisabledError. However, some broken servers have been known to hang indefinitely when issued a +CAPABILITY+ command prior to authentication. For those servers, wo offer the `enforce_logindisabled` config option. Fixes #32.
nevans
added a commit
that referenced
this issue
Jun 27, 2024
This may be considered a "breaking change", but it should have no negative effect on well behaved servers. This should merely change a NoResponseError into a LoginDisabledError. However, some broken servers have been known to hang indefinitely when issued a `CAPABILITY` command prior to authentication. For those servers, wo offer the `enforce_logindisabled` config option. Fixes #32.
nevans
added a commit
that referenced
this issue
Jun 27, 2024
This may be considered a "breaking change", but it should have no negative effect on well behaved servers. This should merely change a NoResponseError into a LoginDisabledError. However, some broken servers have been known to hang indefinitely when issued a `CAPABILITY` command prior to authentication. For those servers, we offer the `enforce_logindisabled` config option. Fixes #32.
nevans
added a commit
that referenced
this issue
Jun 27, 2024
This may be considered a "breaking change", but it should have no negative effect on well behaved servers. This should merely change a NoResponseError into a LoginDisabledError. However, some broken servers have been known to hang indefinitely when issued a `CAPABILITY` command prior to authentication. For those servers, we offer the `enforce_logindisabled` config option. Fixes #32.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
depends on:
The text was updated successfully, but these errors were encountered: