Closed cherio closed 5 months ago
It's not easy to decide which variables should be sanitized and which ones should not be. The safe approach is to only use a whitelist, but this is bound to break something, somewhere. I would recommend using a different authentication module instead. Otherwise, please submit a PR.
I may be missing something but wouldn't it be safe to assume that the variable whose name referenced as --auth=env:name=VAR
should be removed from the environment?
I'm not going to do this sorts of parsing gymnastics, sorry.
I was just responding to
It's not easy to decide which variables should be sanitized
simply pointing to the fact that the variable name that holds authentication password is readily available, as it is explicitly specified. I realize that because I am not familiar with the code, what seems to be obvious and simple on the surface, may not really be that straightforward.
@cherio the vfb code knows nothing about authentication modules, and the authentication modules know nothing about the command line.
Please try e1b5660f6f659d214f073fa086e6efa8764f0f8f
Describe the bug
xpra
server clears all its environment (probably for security reasons) but not before it launchesXvfb-for-Xpra-3
process. The variable containing authentication password is clearly visible in the process environment.To Reproduce Steps to reproduce the behavior:
System Information (please complete the following information):
$ xpra --version xpra v6.1-r35816 (gefa5e2cf65) beta