Am 28.06.21 um 11:13 schrieb Tobias Botens:
> during the installation of x2go on Windows 10 we are getting Windows
> UAC-Prompts.
Yes, that's because some of the applications we need to bundle with
X2GoClient.exe are "stupid" and insist on binding to 0.0.0.0, where
binding to 127.0.0.1 would suffice.
Windows detects these attempts to bind and prompts you to confirm or
deny this. You should deny them.
> We want to distribute the Software via our Software-Distribution Product. How
> can we achieve a "silent Installation" without these prompts. If needed, we
> will create the firewall-Rules manually in our deployment-process.
You can safely deny listening services on anything but 127.0.0.1 by
adding such rules manually beforehand. The only exception would be
pulseaudio, if you insist on *not* tunneling that traffic through SSH.
While X2GoClient does offer that option, tunneling through SSH is
enabled by default and I am not aware of anyone using it in "disabled" mode.
By the way, are you aware that you can run X2GoClient via a read-only
network share? That way, you don't have to push updates to the
individual PCs - update your central installation on the network share,
once, and you're all set.
Kind Regards,
Stefan Baur
--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
