Hi Heinrich,
----- Original message -----
On Thu, Nov 8, 2012 at 10:36 PM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
HI Heinrich,
On Do 08 Nov 2012 19:46:59 CET Xypron wrote:
Hello Mike,
I just read http://www.x2go.org/doku.php/wiki:advanced:multi-node:x2goserver-printing
Following the instructions means that anybody who hacks my cups server can login as sudoer to the x2goserver, because I leave the key on the doorstep (/root/.ssh/id_dsa-x2goprint).
Why doesn't the x2goserver p
My suggestion is: apt-get install x2goserver-printing should not create user x2goprint, because the user is not needed if the Cups and the X2GO server are the same.
My suggestion would be splitting up the already tiny package x2goserver-printing into two packages rather than one. The first providing the x2goprint script, the second (x2goserver-printing-multinode) creating the user.
Another option would be a debconf question, defaulting to single-node.
Reinhard, thanks for throwing that into the ring. I actually prefer that approach.
I also think that we should keep this debconf template silent, so it only gets called with dpkg-rconfigure command and a higher prio then the default.
Greets, Mike