A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/02 12:25
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483359802
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -182,9 +182,9 @@
<code> cd $(mktemp -d)
wget -Y off http://your-http-server-ip-here/
wget -Y off
http://your-http-server-ip-here/x2go-tce/x2go-tce-filesystem.squashfs
</code>
- In case of an FTP URL, replace http with ftp in the example above. Same goes
for https when trying to get that to work with iPXE.
+ In case of an FTP URL, replace http with ftp in the example above. Same goes
for https when trying to get that to work.
**Note that you MUST use an IP address. X2Go-TCE WILL NOT WORK with a DNS name, even though this
test here will accept IPs and DNS names alike. The only exception is when a
template actually spells out that you should input a DNS name.**
</note>
@@ -226,9 +226,9 @@
=== What options are available under FURTHER-OPTIONS-GO-HERE? ===
These two are mutually exclusive, i.e. never put both of them in the same config:
- *
''sessionsurl=http://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.sessions''
- use this to specify a sessions file. You need this unless you are using a
session broker. See below for how to add this file to your HTTP, HTTPS, or FTP
server. Note that whoever manages to spoof the server name can inject rogue
session config files into your ThinClients. To mitigate this risk, use HTTPS,
where the attacker would have to spoof both server name and matching
certificate.
+ *
''sessionsurl=https|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.sessions''
- use this to specify a sessions file. You need this unless you are using a
session
broker. See below for how to add this file to your HTTP, HTTPS, or FTP server.
Note that whoever manages to spoof the server name can inject rogue session
config files into your ThinClients. To mitigate this risk, use HTTPS, where
the attacker would have to spoof both server name and matching certificate.
* ''broker-url=ssh:<nowiki>//</nowiki>your-broker-address-here'' - this
allows you to specify an X2Go Session Broker instead of a sessions file (not limited to an
ssh-based broker, works with an http-based broker as well)
These are entirely optional:
* ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to
HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'',
useful if autodetection for the correct screen size fails, but you do get as
far as seeing the X2Go GUI
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-commits
