-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
more generic command
for the exec authentication module
#3790
Comments
the full command is now configurable including arguments, and those arguments can use authentication attributes like 'username', 'info' and 'prompt'
It is now also possible to use the challenge (aka password) in the exec command: xpra shadow -d auth --no-daemon \
--bind-tcp=0.0.0.0:10000 \
--tcp-auth=exec:require-challenge=yes,client-username=yes,command='touch /tmp/HELLO-${username}-${password}' Obviously, this should not be used with system passwords but this could be quite useful for delegating token validation to external command line tools. |
Tested with the defaults and a shadow server: xpra shadow --bind-tcp=0.0.0.0:10000,auth=exec \
-d auth --no-daemon Which ends up calling: /usr/libexec/xpra/auth_dialog 'Connection request from tcp socket: IP:10000 <- IP:53168' '600' Another example: xpra shadow --bind-tcp=0.0.0.0:10000,auth=exec,client-username=yes,command='touch /tmp/HELLO-${username}' \
-d auth --no-daemon Then connecting with: xpra attach --sharing=yes 'tcp://foo:bar@localhost:10000/' And the @walakee this should be useful to you. You can chain this pseudo-authentication module after the ldap one. |
@walakee no, this would be difficult to port - for a start, the authentication module interface has changed. |
@totaam thanks for the immediate reply. Unfortunately CentOS Stream 8 seems to have an earlier EOL than CentOS 7.9. For this reason it is hard to justify the upgrade. Especially since it is not really a straight-forward process. Is there any workaround perhaps that could be used in CentOS 7.9 for the same purpose (custom script to be executed after successful LDAP authentication, with username as the parameter)? Thanks again, |
@walakee CentOS 8 is already EOLed, use RockyLinux or AlmaLinux instead. We have builds for both. |
So that we can generate more useful commands based on the
username
specified:#3781 (comment)
Obviously, we want to be careful here and not allow just any string substitution as this would be ripe for exploitation.
The text was updated successfully, but these errors were encountered: