A page in your DokuWiki was added or changed. Here are the details:
Date : 2018/04/30 10:03
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:52.9) Gecko/20100101
Goanna/3.4 Firefox/52.9 PaleMoon/27.9.0
IP-Address : 149.172.203.221
Hostname : HSI-KBW-149-172-203-221.hsi13.kabel-badenwuerttemberg.de
Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1518447511
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -880,9 +880,9 @@
* ''bg=https|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce-bg.svg'' -
use this to specify an SVG file to "brand" your X2Go-TCE with. It will replace
the blue background theme of the login screen. See below for how to add this file to your
HTTP, HTTPS, or FTP server. **Attention: Whoever manages to spoof the server name can
inject rogue images into your ThinClients.** To mitigate this risk, use HTTPS, where the
attacker would have to spoof both server name and matching
certificate.
* ''blank=n|n:n:n'' - Will disable (''blank=0'') or set screensaver timeout.
Use ''blank=n:n:n'' to set DPMS Standby/Suspend/Off values. Standby value
equals screensaver timeout value. All values are given in seconds.
* ''blankdpmsfix'' - This forces the TFT do black for a few seconds during the X
startup phase, then forces it back on again. This fixes an occasional "black
screen" issue that occurs with some flaky client/TFT hardware combinations when
using DisplayPort connectors, and could otherwise only be remediated by manually turning
the TFT off and back on again. (feature available via github repo, soon via x2go repo too)
*
''branding=https|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce-branding.svg''
- use this to specify an SVG file to "brand" your X2Go-TCE with. It will
replace the seal icon in the lower left of the login screen. See below for how to add
this file to your HTTP, HTTPS, or FTP server. **Attention: Whoever manages to
spoof the server name can inject rogue images into your ThinClients.** To
mitigate this risk, use HTTPS, where the attacker would have to spoof both
server name and matching certificate.
- * ''copysecring'' - this will scan for USB media and fixed disk media (with
USB media taking precedence) at boot for one or more of the following
directories: ''config/ssh'', 'ssh', ''.ssh''. The volume must be labeled
''X2GO-TCE-LIVE'' or ''PORTABLEAPP'' and may use any supported file system. Any
SSH Secret Keys found there will be copied into ''/home/user/.ssh'' (in the
ramdisk), with proper permissions and ownerships for the default user account.
This may come in handy when you are using SSH Secret Keys on USB media, but
need to log in and out of sessions often, and don't want to leave the USB media
plugged in all the time/don't want to have to re-insert it before each session
startup. **Attention: This poses a security risk when other people are using
your ThinClient afterwards (as they will
have access to your keys).** To mitigate this risk,be sure to power-cycle the
ThinClient once you are done. You //should// specify this parameter when
booting X2Go-TCE-Live from portable media when you want to use SSH Secret Keys,
to make sure your secret key on the VAT/NTFS partition is available. But as
stated above, be sure to power-cycle the machine once you're done.
+ * ''copysecring'' - this will scan for USB media and fixed disk media (with
USB media taking precedence) at boot for one or more of the following
directories: ''config/ssh'', 'ssh', ''.ssh''. The volume must be labeled
''X2GO-TCE-LIVE'' or ''PORTABLEAPP'' and may use any supported file system. Any
SSH Secret Keys found there will be copied into ''/home/user/.ssh'' (in the
ramdisk), with proper permissions and ownerships for the default user account.
This may come in handy when you are using SSH Secret Keys on USB media, but
need to log in and out of sessions often, and don't want to leave the USB media
plugged
in all the time/don't want to have to re-insert it before each session startup.
**Attention: This poses a security risk when other people are using your
ThinClient afterwards (as they will have access to your keys).** To mitigate
this risk,be sure to power-cycle the ThinClient once you are done. You
//should// specify this parameter when booting X2Go-TCE-Live from portable
media when you want to use SSH Secret Keys, to make sure your secret key on the
FAT/NTFS partition is available. But as stated above, be sure to power-cycle
the machine once you're done.
* ''earlyblankdpmsfix'' - This forces the TFT do black for a few seconds during the
initial boot phase (right after the squashfs was downloaded), then forces it back on
again. This fixes an occasional "black screen" issue that occurs with some
flaky client/TFT hardware combinations when using DisplayPort connectors, and could
otherwise only be remediated by manually turning the TFT off and back on again. (feature
available
via github repo, soon via x2go repo too)
* ''homepageurl="URL1[|URL2|URLn]"'' - this is only available in MiniDesktop mode. It allows you
to specify one or more web pages that show up on Browser start/when clicking the "Home" icon. URLs
need to be separated with a ''|'', and the set of URLs needs to be enclosed in double quotes. Do //not//
enclose each URL in double quotes separately! Correct example:
''homepageurl="https://www.google.de|https://wiki.x2go.org";''
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this
allows you to specify an LDAP server to connect to - note that this is not
needed for LDAP-based authentication, only when you intend to store entire
session profiles in LDAP. You should really consider using the X2Go Session
Broker instead.
* ''ldap1=ldap-backupserver-1.example.com:389'' - this allows you to specify
the first of up to two LDAP backup servers when using LDAP authentication
--
This mail was generated by DokuWiki
at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
x2go-commits@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-commits
