xpra icon
Bug tracker and wiki

Opened 5 years ago

Closed 5 years ago

#676 closed enhancement (wontfix)

Allow admin to restrict the user's ability to overwrite xpra config settings

Reported by: sschnitzer Owned by: sschnitzer
Priority: major Milestone:
Component: server Version: trunk
Keywords: Cc:

Description

For admin-managed environments it is not always desireable to allow users to change xpra.conf settings.
A simple solution is, to add a command line switch to the xpra server process which makes it ignore the ~/xpra.conf.
A more flexible solution is to mark options in /etc/xpra/xpra.conf individually as "forced", e.g. by using " =! " instead of " = ". Forced options cannot be overwritten by ~/xpra.conf.

Change History (4)

comment:1 Changed 5 years ago by Antoine Martin

Owner: changed from Antoine Martin to sschnitzer

I don't think we can do this:

  • you still have command line switches
  • you still have the tray menu
  • you still have the ability to change at least some options using xpra control

etc..

Also, I really don't like the idea of using a funny syntax.
If anything, I would prefer doing something this:

  • load server defaults (ie: /etc/xpra/xpra.conf on Linux)
  • load user overrides (ie: ~/.xpra/xpra.conf on Linux)
  • load option server overrides on top (ie: /etc/xpra/overrides.conf on Linux)

comment:2 Changed 5 years ago by sschnitzer

I think command line switches can be ignored. If the user has permission to start the xpra server process (which is required if he wants to pass command line options), he could most likely also start a modified xpra which ignores "forced" options.

I think the tray menu, as well as xpra control allows only a few options to be changed. I guess the client cannot switch the server to an encoding which is not listed in encodings on the server, right?

Is there any documentation available about what options from xpra.conf can be set by command line options or changed by xpra control?

I appreciate the idea of a /etc/xpra/overrides.conf.

comment:3 Changed 5 years ago by Antoine Martin

I think command line switches can be ignored. If the user has permission to start the xpra server process (which is required if he wants to pass command line options) ...


Wrong. xpra is a command which can be used for both client and server, in both cases it takes command line arguments. What makes you think that you need to "start the xpra server process .. to pass command line options" ?

I guess the client cannot switch the server to an encoding which is not listed in encodings on the server, right?


Correct.

Is there any documentation available about what options from xpra.conf can be set by command line options ..


All of them.

or changed by xpra control?


No, and none is planned. It is not a stable interface yet.
What you can do is run:

xpra control :DISPLAY help

Which should give you a list of control commands supported by that server, some of which may support the help mode themselves, ie:

xpra control :DISPLAY debug help

comment:4 Changed 5 years ago by Antoine Martin

Resolution: wontfix
Status: newclosed

Not heard back.

Note: See TracTickets for help on using tickets.