thanks
... for the answer. We just retested it today in our environment, and the issue is still as described. Especially we did:
1) user_A starts a xfce x2go session on hostA, without starting x2godesktopsharing.
2) user_B logs in at hostA, using "connect to local desktop. It sees a X session under its own user name, and a port. user_B can click on "full access" and gets access to the session.
Second test:
- user_A starts x2godesktopsharing, but leave the default setting (do not allow access, with cross).
- user_B sees same behaviour as described above
Third test:
- user_A starts x2godesktopsharing, but and enables access (green icon in menu bar)
- user_B now sees two sessions in the session list: one with his own user name, one with user_As user name. Both have the same port. If user_B selects the one which has user_A as its name, he can only connect to view, and eventually, this connection gets refused. (In the mean time, user_A sees a question dialog asking user_B for access in the session.)
But still, user_B sees a session with his own name, and can connect to it and gets full access to the xfce session started by user_A.