-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
confusing message when max sessions exceeded #642
Labels
Comments
Likewise, failure to execute a backend should be reported to xrdp. |
matt335672
added a commit
to matt335672/xrdp
that referenced
this issue
Dec 14, 2022
An extra method auth_uds() is added to the PAM module to allow a 'struct auth_info' to be created for a UDS login. The PAM stack is used to check the UDS user can be authorized. Also, an error code is returned from the auth module rather than a simple boolean. This allows a more complete status to be communicated to the user. See neutrinolabs#1921 and also neutrinolabs#909 and neutrinolabs#642
matt335672
added a commit
to matt335672/xrdp
that referenced
this issue
Dec 14, 2022
An extra method auth_uds() is added to the PAM module to allow a 'struct auth_info' to be created for a UDS login. The PAM stack is used to check the UDS user can be authorized. Also, an error code is returned from the auth module rather than a simple boolean. This allows a more complete status to be communicated to the user. See neutrinolabs#1921 and also neutrinolabs#909 and neutrinolabs#642
matt335672
added a commit
to matt335672/xrdp
that referenced
this issue
Dec 22, 2022
An extra method auth_uds() is added to the PAM module to allow a 'struct auth_info' to be created for a UDS login. The PAM stack is used to check the UDS user can be authorized. Also, an error code is returned from the auth module rather than a simple boolean. This allows a more complete status to be communicated to the user. See neutrinolabs#1921 and also neutrinolabs#909 and neutrinolabs#642
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When sessions limit exceeded, logwindow says "login failed for display 0". This is not user friendly. The message should be "sessions limit exceeded".
I looked at sesman, it seems sesman doesn't return the reason of login failure to xrdp. We should think about sesman design. The reason of login failure should be reported to the user not just written to log.
The text was updated successfully, but these errors were encountered: