User Tools

Site Tools


doc:howto:tce

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:howto:tce [2018/12/04 21:13]
stefanbaur [List of open ToDos/FIXMEs for this page] - tested nottyautologon
doc:howto:tce [2024/01/26 19:49] (current)
stefanbaur [Client Branding/Theming using SVGs] added before and after images
Line 1: Line 1:
 ====== X2Go-ThinClientEditon-Live (TCE-Live, formerly known as TCE-NG) ====== ====== X2Go-ThinClientEditon-Live (TCE-Live, formerly known as TCE-NG) ======
 <columns 75% -> <columns 75% ->
-<note important>This page is very much Work in Progess. Please leave a note on x2go-user@lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note> 
  
 <note tip>If you are looking for installation instructions for the classic, NFS-filesystem-based X2Go-ThinClient, please go [[wiki:advanced:tce:install|here]] <note tip>If you are looking for installation instructions for the classic, NFS-filesystem-based X2Go-ThinClient, please go [[wiki:advanced:tce:install|here]]
Line 12: Line 11:
 During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition then called TCE-Next Generation, or TCE-NG for short - one that is based on Debian-Live and thus does no longer rely on NFS (though NFS can still be used to deploy the image - but we do not recommend that approach).  Instead, the entire image is loaded into the RAM of the ThinClient machine.  To avoid confusion, and because it has since left the "NG" state, we now call it TCE-Live. During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition then called TCE-Next Generation, or TCE-NG for short - one that is based on Debian-Live and thus does no longer rely on NFS (though NFS can still be used to deploy the image - but we do not recommend that approach).  Instead, the entire image is loaded into the RAM of the ThinClient machine.  To avoid confusion, and because it has since left the "NG" state, we now call it TCE-Live.
  
-The disadvantage is that your ThinClient now needs at least 1 GB of RAM (see below).  +The disadvantage is that your ThinClient now needs at least 512 MB to 1 GB of RAM (see below).  Working with 256 MB is possible when you use local storage instead of netbooting (don't use the ''toram'' parameter, either), but not really recommended.
  
 However, the huge advantage is that there no longer is a need for any high-availibility setup concerning NFS (nor HTTP/HTTPS/FTP).  If you follow our advice of loading the entire image into the ThinClient's RAM, or using local storage,  all you need is an HTTP (HTTPS optional for later stages) or FTP server with a dedicated IP, if you want to use netbooting.  It is also possible to deploy the image to the ThinClient's local storage, if present, and have it update in the background. However, the huge advantage is that there no longer is a need for any high-availibility setup concerning NFS (nor HTTP/HTTPS/FTP).  If you follow our advice of loading the entire image into the ThinClient's RAM, or using local storage,  all you need is an HTTP (HTTPS optional for later stages) or FTP server with a dedicated IP, if you want to use netbooting.  It is also possible to deploy the image to the ThinClient's local storage, if present, and have it update in the background.
  
-Besides, making changes to/updating the classic, NFS-based TCE (henceforth referred to as TCE-Classic) with the entire filesystem, not just its compressed image, spread out over the NFS share was rather finicky - with the current TCE-Live, you build and deploy a new image every time you make a change, and you can test it on a single client without interrupting your production environment.  The //local storage// feature can also be used to create a portable version of both X2Go-TCE and X2goClient for Windows, sharing the same configuration, on CD/DVD/USB media.+Besides, making changes to/updating the classic, NFS-based TCE (henceforth referred to as TCE-Classic) with the entire filesystem, not just its compressed image, spread out over the NFS share was rather finicky - with the current TCE-Live, you build and deploy a new image every time you make a change, and you can test it on a single client without interrupting your production environment.  The //local storage// feature can also be used to create a portable version of both X2Go-TCE and X2GoClient for Windows, sharing the same configuration, on CD/DVD/USB media.
  
 We've also received reports that TCE-Classic wouldn't work with Jessie, or at least it was very hard to get it to work. We've also received reports that TCE-Classic wouldn't work with Jessie, or at least it was very hard to get it to work.
-Our TCE-Live works just fine with Jessie, and we expect it to work in Stretch and hopefully in Buster (Stretch+1) as well+Our TCE-Live works just fine with Jessie, Stretchand Buster as well. 
-The one catch is that the live-build package in Debian/the Debian-Live project is currently looking for a new maintainer - so there is a slim chance that live-build might be removed from Debian Buster, especially if no new maintainer steps up and the live-build replacement that is currently in the works (called live-wrapper) contains all the required functionality of live-build by then+ 
 ===== ThinClient prerequisites for all TCE-Live variants ===== ===== ThinClient prerequisites for all TCE-Live variants =====
   * At least 1 GB of RAM //unless// you use non-NTFS local storage, in that case, 512MB or even 256MB might work - but would you really want to use a Client that has 4 Megabytes of free RAM (our test result with 256 MB RAM total) and no swapspace?   * At least 1 GB of RAM //unless// you use non-NTFS local storage, in that case, 512MB or even 256MB might work - but would you really want to use a Client that has 4 Megabytes of free RAM (our test result with 256 MB RAM total) and no swapspace?
Line 29: Line 27:
   * A graphics card and input devices (Keyboard, Mouse/Trackball/Touchpad/Trackpoint/Touchscreen, ...) that are supported by the stock Debian X Server   * A graphics card and input devices (Keyboard, Mouse/Trackball/Touchpad/Trackpoint/Touchscreen, ...) that are supported by the stock Debian X Server
 ===== Build system prerequisites for all variants ===== ===== Build system prerequisites for all variants =====
-  * You need a Debian Jessie system to build the image. (Other distributions based on Debian might work, but this is untested.)+  * You need a Debian Buster system to build the image. (Other distributions based on Debian might work, but this is untested.)
   * We suggest using a 64-Bit system, however, it is possible to use a 32-Bit system if you don't want to build a 64-Bit ThinClient image.   * We suggest using a 64-Bit system, however, it is possible to use a 32-Bit system if you don't want to build a 64-Bit ThinClient image.
   * We suggest leaving at least 4 GB of free disk space so the build won't abort due to insufficient disk space while packages are downloaded, unpacked and copied around.   * We suggest leaving at least 4 GB of free disk space so the build won't abort due to insufficient disk space while packages are downloaded, unpacked and copied around.
   * Make sure your package list is up to date by running: <code>sudo apt-get update </code>   * Make sure your package list is up to date by running: <code>sudo apt-get update </code>
-  * Install the required packages by running: <code>sudo apt-get install genisoimage git-core live-build live-config-doc live-manual-html live-boot-doc</code>+  * Install the required package(s) by running: <code>sudo apt-get install genisoimage git-core live-build live-config-doc live-manual-html live-boot-doc lsb-release netcat-traditional</code> 
 +  * If you want to speed up subsequent builds, install the recommended package(s) by running: <code>sudo apt-get install apt-cacher-ng</code> 
 +  * If you want to be prepared to be able to cross-build across different architectures (e.g. building an ARM image on an Intel/AMD build host) - a feature coming soon - install the optional package(s) by running: <code>sudo apt-get install qemu-user-static</code>
  
 ===== Building your own X2Go-TCE Image ===== ===== Building your own X2Go-TCE Image =====
 ==== Configuring the Build ==== ==== Configuring the Build ====
 +Change to a directory where you want to save your builds, and save the following file as x2go-tce-config:
 <code> <code>
 +# NOTE: This file gets sourced by the actual buildscript - so place it in the same directory as the buildscript or adjust the path in the buildscript.
 +
 +# simple check for apt-cacher-ng being active - if
 +# we have a successful connect on port 3142, assume
 +# it's apt-cacher-ng and use it
 +#
 +if nc -z 127.0.0.1 3142 ; then 
 +    # bad idea with apt-cacher-ng, but will work with e.g. squid
 +    # export https_proxy=http://127.0.0.1:3128/ 
 +    # export http_proxy=http://127.0.0.1:3128/
 +    # export ftp_proxy=http://127.0.0.1:3128/
 +
 +    export LB_APT_FTP_PROXY=http://127.0.0.1:3142/
 +    export LB_APT_HTTP_PROXY=http://127.0.0.1:3142/
 +fi
 +
 +# set these to true to save source files
 +#export LB_SOURCE="true"
 +#export LBX2GO_GETSRC="true"
 +
 # Select ONE of the following git reposities # Select ONE of the following git reposities
 # this one loosely corresponds to "stable" # this one loosely corresponds to "stable"
-export LBX2GO_CONFIG='git://code.x2go.org/live-build-x2go.git::feature/openbox-magic-pixel-workaround' +#export LBX2GO_CONFIG='https://gitlab.x2go.org/x2go/live-build-x2go.git::feature/openbox-magic-pixel-workaround-buster' 
-this one loosely corresponds to "heuler" +#export LBX2GO_CONFIG='https://gitlab.x2go.org/x2go/live-build-x2go.git::feature/mate-minidesktop-buster' 
-#export LBX2GO_CONFIG='https://github.com/LinuxHaus/live-build-x2go::feature/openbox-magic-pixel-workaround' +export LBX2GO_CONFIG='https://gitlab.x2go.org/x2go/live-build-x2go.git::feature/openbox-magic-pixel-workaround-bullseye
-NOTE: Add "-stretch" to the end of the LBX2GO_CONFIG string to create a stretch build+#export LBX2GO_CONFIG='https://gitlab.x2go.org/x2go/live-build-x2go.git::feature/mate-minidesktop-bullseye' 
 +#export LBX2GO_CONFIG='https://github.com/bauritcs/live-build-x2go.git::feature/openbox-magic-pixel-workaround-bookworm
 +#export LBX2GO_CONFIG='https://github.com/bauritcs/live-build-x2go.git::feature/mate-minidesktop-bookworm' 
 +# NOTES: 1) https://github.com/bauritcs loosely corresponds to "heuler" 
 +#        2) Minidesktop builds are work in progress and not production-ready. Cont(r)act us if you need them; feel free to submit patches. 
 +#        3) Add "-stretch" to the end of the LBX2GO_CONFIG string to create a stretch build
 +#           add "-buster" to the end of the LBX2GO_CONFIG string to create a buster build, 
 +#           add "-bullseye" to the end of the LBX2GO_CONFIG string to create a bullseye build 
 +#           add "-bookworm" to the end of the LBX2GO_CONFIG string to create a bookworm build (will be in gitlab repo $SOON - use github.com/bauritcs for now)
  
 # Select ONE of the following LBX2GO_ARCH lines and comment out the others # Select ONE of the following LBX2GO_ARCH lines and comment out the others
Line 50: Line 79:
 export LBX2GO_ARCH='-a amd64 -k amd64' export LBX2GO_ARCH='-a amd64 -k amd64'
 # 32-Bit, larger memory footprint, but faster performance on i686 and newer # 32-Bit, larger memory footprint, but faster performance on i686 and newer
-# export LBX2GO_ARCH='-a i386 -k 686-pae' +#export LBX2GO_ARCH='-a i386 -k 686-pae' 
-# 32-Bit, smallest memory footprint+# 32-Bit, smallest memory footprint - not available on buster
 # export LBX2GO_ARCH='--architectures i386 --linux-flavours 586' # export LBX2GO_ARCH='--architectures i386 --linux-flavours 586'
 +# For ARM (Raspberry Pi):
 +#export LBX2GO_ARCH='-a arm64'
 +#export LBX2GO_ARCH_MODEL='Pi4' # you can also set this to 'Pi3'. Note that there must not be any whitespace between 'Pi' and the digit.
  
-# detect if the selected git repo is meant to build a stretch or jessie image+# If you want to use the stock ISO image as created by this script, add your boot parameters here 
 +# export LBX2GO_BOOTAPPEND_LIVE="boot=live components noswap lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 silent quiet pubkey=http://x2go/x2go-tce/config/authorized_keys sessionsurl=http://x2go/x2go-tce/config/sessions toram" 
 +export LBX2GO_BOOTAPPEND_LIVE="boot=live components noswap lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 silent quiet sessionsurl=https://x2go.baur-itcs.de/.config/x2go-demo/config/sessions pubkey=https://x2go.baur-itcs.de/.config/x2go-demo/config/authorized_keys toram " 
 + 
 +if echo -e "$LBX2GO_CONFIG" | grep -q "openbox"; then 
 + LBX2GO_BOOTAPPEND_LIVE+="fastpo " 
 + export LBX2GO_BOOTAPPEND_LIVE 
 +elif echo -e "$LBX2GO_CONFIG" | grep -q "minidesktop"; then 
 + LBX2GO_BOOTAPPEND_LIVE+='timezone=Europe/Berlin noautologin ' # if you use nottyautologin instead of noautologin, an autologin will be set for the account "user", which conflicts our setting for the account "x2gothinclient" 
 + export LBX2GO_BOOTAPPEND_LIVE 
 +fi 
 + 
 +# detect if the selected git repo is meant to build a buster, stretch or jessie image
 if [ -z "${LBX2GO_CONFIG##*-stretch}" ] ; then if [ -z "${LBX2GO_CONFIG##*-stretch}" ] ; then
-        export LBX2GO_DEBVERSION="stretch"+    export LBX2GO_DEBVERSION="stretch
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +elif [ -z "${LBX2GO_CONFIG##*-buster-heuler}" ] ; then 
 +    export LBX2GO_DEBVERSION="buster" 
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +elif [ -z "${LBX2GO_CONFIG##*-buster-heuler-bpo}" ] ; then 
 +    export LBX2GO_DEBVERSION="buster" 
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +elif [ -z "${LBX2GO_CONFIG##*-buster}" ] ; then 
 +    export LBX2GO_DEBVERSION="buster" 
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +elif [ -z "${LBX2GO_CONFIG##*-bullseye}" ] ; then 
 +    export LBX2GO_DEBVERSION="bullseye" 
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +elif [ -z "${LBX2GO_CONFIG##*-bookworm}" ] ; then 
 +    export LBX2GO_DEBVERSION="bookworm" 
 +    export LBX2GO_BOOTAPPEND_LIVE+=" net.ifnames=0 biosdevname=0" 
 +    export LBX2GO_ARCHIVE_AREAS="non-free-firmware "
 else else
-        export LBX2GO_DEBVERSION="jessie"+    export LBX2GO_DEBVERSION="jessie"
 fi fi
  
 # newer versions of live-build use the plural form of this parameter # newer versions of live-build use the plural form of this parameter
 if $(LANG=C lb config --help | grep -q bootloaders) ; then if $(LANG=C lb config --help | grep -q bootloaders) ; then
-        export LBX2GO_BOOTLOADERPARAMNAME="--bootloaders"+    export LBX2GO_BOOTLOADERPARAMNAME="--bootloaders"
 else else
-        export LBX2GO_BOOTLOADERPARAMNAME="--bootloader"+    export LBX2GO_BOOTLOADERPARAMNAME="--bootloader"
 fi fi
  
 # set boot loader type - leave this unchanged unless you really know what you're doing # set boot loader type - leave this unchanged unless you really know what you're doing
-export LBX2GO_BOOTLOADER="syslinux"+if echo $LBX2GO_ARCH | awk '{print $2}' | grep -q "arm" ; then 
 +    # This is part of our experimental ARM support 
 +    LBX2GO_BOOTLOADERPARAMNAME="
 +    LBX2GO_BOOTLOADER="
 +else 
 +    export LBX2GO_BOOTLOADER="syslinux" 
 +fi
  
 # These options are meant to reduce the image size. # These options are meant to reduce the image size.
 # Feel free to adapt them after consulting "man lb_config" # Feel free to adapt them after consulting "man lb_config"
-export LBX2GO_SPACE='--apt-indices none+# FIXME export LBX2GO_SPACE='--apt-indices none 
 +export LBX2GO_SPACE='--apt-indices false
                      --apt-recommends false                      --apt-recommends false
                      --cache false                      --cache false
Line 103: Line 171:
                         --distribution $LBX2GO_DEBVERSION"                         --distribution $LBX2GO_DEBVERSION"
  
 +# This is part of our experimental ARM support
 +if echo $LBX2GO_ARCH | grep -q 'arm' && ! dpkg --print-architecture | grep -q 'arm' ; then
 +    export LBX2GO_DEFAULTS+=" --bootstrap-qemu-arch arm64 \
 +                              --bootstrap-qemu-static /usr/bin/qemu-aarch64-static \
 +                              --apt-options \"--yes -oAPT::Default-Release=${LBX2GO_DEBVERSION} -oAPT::Immediate-Configure=false\" "
 +fi
 +
 +# This is part of our experimental ARM support
 +# This makes sure the resulting disk image is at least 1GB in size, even though our build currently requires way less.
 +# It's unlikely that anyone will need to boot from a smaller partition; but if we let live-build pick the minimum size automatically,
 +# we will not have enough space left to copy the firmware blobs into the right location.
 +if echo $LBX2GO_ARCH | grep -q 'arm' ; then
 +    export LBX2GO_DEFAULTS+=" --binary-filesystem fat32 \
 +                              --hdd-size 1024"
 +fi
  
-export LBX2GO_ARCHIVE_AREAS="main contrib non-free"+export LBX2GO_ARCHIVE_AREAS="main contrib non-free $LBX2GO_ARCHIVE_AREAS"
  
 # This is for minidesktop builds and currently only adds firefox-esr language packs # This is for minidesktop builds and currently only adds firefox-esr language packs
-#export LBX2GO_LANG='de'+# export LBX2GO_LANG='de'
  
 # This is to optimize squashfs size, based on a suggestion by intrigeri from the TAILS team # This is to optimize squashfs size, based on a suggestion by intrigeri from the TAILS team
 # note that this will permanently change /usr/lib/live/build/binary_rootfs # note that this will permanently change /usr/lib/live/build/binary_rootfs
-sed --'s#MKSQUASHFS_OPTIONS="${MKSQUASHFS_OPTIONS} -comp xz"#MKSQUASHFS_OPTIONS="${MKSQUASHFS_OPTIONS} -comp xz -Xbcj x86 -b 1024K -Xdict-size 1024K"#' /usr/lib/live/build/binary_rootfs+
 +
 +if dpkg --print-architecture | grep -q 'arm'; then 
 + on arm, these parameters must not be used; if they're there, we need to reinstall the package to undo our patch 
 + if grep --- '-Xbcj x86 -b 1024K -Xdict-size 1024K' /usr/lib/live/build/binary_rootfs; then 
 + apt install --reinstall live-build 
 + fi 
 + # feel free to experiment with these options, but be prepared for subtle breakage  
 + #export MKSQUASHFS_OPTIONS=' -Xbcj arm ' 
 + #export MKSQUASHFS_OPTIONS=' -b 1024K -Xdict-size 1024K ' 
 + #export MKSQUASHFS_OPTIONS=' -Xbcj arm -b 1024K -Xdict-size 1024K ' 
 + export MKSQUASHFS_OPTIONS='' 
 +else 
 + export MKSQUASHFS_OPTIONS=' -Xbcj x86 -b 1024K -Xdict-size 1024K ' 
 +fi
  
 # This removes documentation, locales and man pages # This removes documentation, locales and man pages
Line 120: Line 217:
 # This patches the squashfs file into the initrd. Only parsed when image type "netboot" is set. # This patches the squashfs file into the initrd. Only parsed when image type "netboot" is set.
 # Will require boot parameter live-media=/ instead of fetch=... # Will require boot parameter live-media=/ instead of fetch=...
-# Both TFTP client and TFTP server must support file transfers >32MB for this to work, if you want to deploy this initrd via TFTP.+# Both TFTP client and TFTP server must support file transfers >32MB for this to work, if you want to deploy this initrd via TFTP,  
 +# so e.g. atftpd will not work - tftpd-hpa, however, seems to have no problem with larger files.
 # When using iPXE, you can use http instead of TFTP. # When using iPXE, you can use http instead of TFTP.
 # This is especially helpful if you want to netboot via http and cannot use the server's IP, but must specify a DNS name - as "fetch=..." only understands IPs. # This is especially helpful if you want to netboot via http and cannot use the server's IP, but must specify a DNS name - as "fetch=..." only understands IPs.
-export LBX2GO_NOSQUASHFS="false"+#export LBX2GO_NOSQUASHFS="true"
  
 # Select ONE of the following LBX2GO_IMAGETYPE lines and comment out the others # Select ONE of the following LBX2GO_IMAGETYPE lines and comment out the others
 # to create an iso image: # to create an iso image:
-# export LBX2GO_IMAGETYPE='iso'+#export LBX2GO_IMAGETYPE='iso'
 # to create an iso image that can also be dd'ed to USB media: # to create an iso image that can also be dd'ed to USB media:
-export LBX2GO_IMAGETYPE='iso-hybrid'+export LBX2GO_IMAGETYPE='iso-hybrid'
 # to create a netboot-image: # to create a netboot-image:
-export LBX2GO_IMAGETYPE='netboot' +#export LBX2GO_IMAGETYPE='netboot' 
-# NOT RECOMMENDED: +/!\ the options below are NOT RECOMMENDED unless you use live-build from Debian Buster /!\ 
-# to create an image that can be written to a hard disk (always results +(Debian 10) or newer to create an image that can be written to a hard disk (for older  
-# in a "build failed" message, even though the build might have worked): +live-build versions, this always results in a "build failed" message, even though the build 
-# export LBX2GO_IMAGETYPE='hdd' +might have worked - use live-build from Buster or newer and things will work): 
-# to create a tar file only (seems to be broken in live-build): +#export LBX2GO_IMAGETYPE='hdd' 
-# export LBX2GO_IMAGETYPE='tar'+## This might be required for hdd builds, especially for (u)efi 
 +#export LBX2GO_BOOTLOADER="syslinux grub-pc grub-efi" 
 +# to create a tar file only (seems to be broken in older live-build versions - Buster works): 
 +#export LBX2GO_IMAGETYPE='tar' 
 + 
 +# This is part of our experimental ARM support 
 +if echo "$LBX2GO_ARCH" | grep -q "arm" ; then 
 + # enforce hdd image for arm at the moment (might need to support netboot later on too) 
 + if ! [ "$LBX2GO_IMAGETYPE" = "hdd" ] ; then 
 +         echo "WARNING: Replacing selected image type with 'hdd' That's all we currently support on ARM." 
 + export LBX2GO_IMAGETYPE="hdd" 
 + fi 
 +fi 
 + 
 +if [ "$LBX2GO_IMAGETYPE" = "netboot" ]; then 
 +        export LBX2GO_DEFAULTS+=" $LBX2GO_BOOTLOADER" 
 +fi
 </code> </code>
  
 ==== Live-Patching the Build ==== ==== Live-Patching the Build ====
-This patch is required if you need USB mount capability on the ThinClient while [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1136|Bug #1136]] is still unresolved.+To add patches that aren't part of any package yet, you can use the directory ./patchfor patches that should be added to all versions, and ./patch-minidesktopfor patches that should only be added to the MATE-MiniDesktop Edition.
  
 +You will need to create a directory structure like <code>./patch/includes.chroot/etc/</code> to create/overwrite a file in <code>/etc/</code> within the live environment.
 +
 +e.g. to override <code>/etc/x2go/x2gothinclient-minidesktop_start</code> with a custom version, run <code>mkdir -p ./patch-minidesktop/includes.chroot/etc/x2go/</code> and save the following file as <code>./patch-minidesktop/includes.chroot/etc/x2go/x2gothinclient-minidesktop_start</code>
 <code> <code>
-mkdir -p ./patch/includes.chroot/usr/lib/x2go/tce/ +#!/bin/bash
- +
-cat >./patch/includes.chroot/usr/lib/x2go/tce/x2gousbmount <<'USBMOUNTPATCH' +
- +
-#!/usr/bin/perl +
-# Copyright (C) 2007-2017 by X2Go project, http://wiki.x2go.org +
-#       Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>+
  
 +# Copyright (C) 2010-2024 by X2Go project, https://wiki.x2go.org
 +#       Oleksandr Shneyder <o.shneyder@phoca-gmbh.de>
 +#       Moritz 'Morty' Struebe <Moritz.Struebe@informatik.uni-erlangen.de>
 +#       Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
 +#       Stefan Baur <X2Go-ML-1@baur-itcs.de>
 +#
 # X2Go is free software; you can redistribute it and/or modify # X2Go is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by # it under the terms of the GNU General Public License as published by
Line 167: Line 284:
 # 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. # 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
  
-use strict; +make sure pulseaudio can be reached via TCP from the X2Go Server side... 
-use File::Path::Expand; +if /usr/bin/pactl list modules | grep -A1 'module-native-protocol-tcp' | grep -q 'auth-ip-acl=127.0.0.1;::1' ; then 
-comment out this "use" and the following two lines, and instead +        /usr/bin/pactl 'load-module' 'module-native-protocol-tcp' 'auth-ip-acl=127.0.0.1;::1' 
-# uncomment the block below if you need to do early boot stage +fi
-# debugging of the automounter, when rsyslogd isn't running yet +
-use Sys::Syslog qw( :standard :macros ); +
-openlog($0,'cons,pid','user'); +
-setlogmask( LOG_UPTO(LOG_NOTICE) ); +
-#open (B,">>/var/log/usbdebug"); +
-#sub syslog { +
-#       print B $_[0].': '.$_[1]."\n"; +
-#} +
- +
-my $user; +
-if ( -f "/etc/x2go/x2gothinclient-minidesktop_start" ) { +
-        # this is a minidesktop environment, which uses +
-        # username "x2gothinclient" regardless of whether +
-        # it runs on X2Go-TCE-Live or X2Go-TCE-NFS +
-        $user='x2gothinclient'; +
-+
-elsif ( -d "/lib/live/config" ) { +
-        # this is X2Go-TCE-Live, but not with a minidesktop +
-        # (if it were, the first condition would have matched), +
-        # so we use Debian-Live's standard username "user" +
-        $user='user'; +
-+
-else { +
-        # this is X2Go-TCE-NFS or something completely different, +
-        # so we'll play it safe and pick the username "x2gothinclient" +
-        # just like previous versions of this script did +
-        $user='x2gothinclient'; +
-+
- +
-# We need this as chown requires numeric uid/gid +
-my ($login,$pass,$uid,$gid) = getpwnam($user); +
- +
-# Some last-ditch efforts to fulfill the prerequisites for File Sharing: +
-This is stuff that should already have happened earlier in the boot process. +
-# - Also, if a directory already exists, we silently assume that ownership and +
-#   permissions are correctThis is so that users that deliberately set +
-#   different ownership/permission values don't have their settings silently +
-#   overwritten. +
- +
-unless ( -d expand_filename("~$user/mounts") ) { +
-        mkdir expand_filename("~$user/mounts")+
-        chmod 0700, expand_filename("~$user/mounts"); +
-        chown $uid, $gid, expand_filename("~$user/mounts"); +
-+
- +
-unless ( -d expand_filename("~$user/export") ) { +
-        mkdir expand_filename("~$user/export"); +
-        chmod 0700, expand_filename("~$user/export"); +
-        chown $uid, $gid, expand_filename("~$user/export"); +
-+
- +
-unless ( -d expand_filename("~$user/logins") ) { +
-        mkdir expand_filename("~$user/logins"); +
-        chmod 0700, expand_filename("~$user/logins"); +
-        chown $uid, $gid, expand_filename("~$user/logins"); +
-+
- +
-sub check_x2gothinclientmode { +
-        my $ret = 0;+
  
-        Check for x2gothinclientd first... +make sure we don't start before sessions and settings files exist - avoids race conditions 
-        my $x=`ps ax | grep x2gothinclient`+while ! [ -e ~x2gothinclient/.x2goclient/sessions ] do 
-        if ( $x=~m/thinclientd/ ) { +        sleep 1; 
-                $ret = 1; +done
-        }+
  
-        return $ret+while ! [ -e ~x2gothinclient/.x2goclient/settings ]do 
-}+        sleep 1 
 +done
  
-#    TCE-NFS                         TCE-Live                                                MMD-Live +-s /etc/x2go/x2gothinclient_bg.svg ] && X2GO_BG='--background="/etc/x2go/x2gothinclient_bg.svg' 
-if ( check_x2gothinclientmode() || ( -"/lib/live/config/2900-x2go-thinclientconfig" ) || ( -"/etc/x2go/x2gothinclient-minidesktop_start" ) ) +-s /etc/x2go/x2gothinclient_branding.svg ] && X2GO_BRAND='--branding="/etc/x2go/x2gothinclient_branding.svg'
-+
-        syslog('notice', "some kind of thinclient mode detected");+
  
-        open (F,">>/var/log/usb"); 
  
-        my $dev=$ENV{'DEVNAME'}; +/usr/lib/x2go/x2goclient --no-menu \ 
-        my $model=$ENV{'ID_MODEL'}; +                         $X2GO_BG \ 
-        my $vendor=$ENV{'ID_VENDOR'}; +                         $X2GO_BRAND \ 
-        my $action=$ENV{'ACTION'}; +                         --kbd-type=auto \ 
-        my @ldev=split("/","$dev"); +                         --set-kbd=1 \ 
-        my $ldev=@ldev[@ldev-1]; +                         --tray-icon \ 
-        # mntdir is not the directory where the mountpoint will be rooted, +                         --read-exports-from=~/export \ 
-        # but where tracking of mount states takes place +                         --no-session-edit \ 
-        my $mntdir; +                         --add-to-known-hosts 
-        if ( -d expand_filename("~$user/mounts") ) { +                         &
-                $mntdir=expand_filename("~$user/mounts"); +
-        } +
-        elsif ( -d "/var/run" ) { +
-                $mntdir="/var/run"; +
-        } +
-        elsif ( -d "/run" ) { +
-                $mntdir="/run"; +
-        } +
-        else { +
-                die "No directory found that we could use as \$mntdir..." +
-        }+
  
-        my $name="${vendor}_${model}"; 
-        $name=~s/ //g; 
-        $name=~s/\\//g; 
-        $name=~s/\///g; 
-        print F "action: $action,  device: $dev, model: $model ($ldev), total: $name\n"; 
-        mkdir("/media"); 
-        mkdir("/media/$name"); 
-        print F "$name\n"; 
- 
-        if (`lsblk -ln -oRM $dev`=~/0$/) { 
-                syslog('notice', "device is non-removable device, skipping"); 
-                exit 0; 
-        } 
- 
-        if ( $action eq "add" ) { 
- 
-                ### 
-                ### ACTION: mount device after it has been added to USB subsystem 
-                ### 
- 
-                syslog('notice', "device add action called"); 
- 
-                # prepare mount points 
-                mkdir("/media"); 
-                mkdir("/media/$name"); 
-                mkdir("/media/$name/$ldev"); 
- 
-                # mount the USB device 
-                # sync is supported by all file systems 
-                # uid is supported by vfat (via fat),ntfs,hfs,hpfs 
-                # uni_xlate is supported by vfat,ntfs 
-                # we must not trigger on iso9660 and udf, or else hybrid USB media 
-                # would only cause a mount of the iso9660 raw device, 
-                # blocking the mount of individual partitions 
-                # real optical media ->x2gocdmanager/x2gothinclient-cdmanager package 
- 
-                if ( system("mount -tntfs $dev /media/$name/$ldev -o uid=$user,sync,uni_xlate")==0 ) { 
-                        syslog('notice', "USB device $name ($ldev) successfully mounted (ntfs detected)"); 
-                        # if mounted, inform x2goclient about it... 
-                        system("touch $mntdir/$ldev.mounted"); 
-                        open (D,">",expand_filename("~$user/export/$name.$ldev")); 
-                        print D "export=/media/$name/$ldev\n"; 
-                        close (D); 
-                } 
-                elsif ( system("mount -tvfat $dev /media/$name/$ldev -o uid=$user,sync,uni_xlate")==0 ) { 
-                        syslog('notice', "USB device $name ($ldev) successfully mounted (vfat detected)"); 
-                        # if mounted, inform x2goclient about it... 
-                        system("touch $mntdir/$ldev.mounted"); 
-                        open (D,">",expand_filename("~$user/export/$name.$ldev")); 
-                        print D "export=/media/$name/$ldev\n"; 
-                        close (D); 
-                } 
-                elsif ( system("mount -t hfs $dev /media/$name/$ldev -o uid=$user,sync")==0 ) { 
-                        syslog('notice', "USB device $name ($ldev) successfully mounted (hfs detected)"); 
-                        # if mounted, inform x2goclient about it... 
-                        system("touch $mntdir/$ldev.mounted"); 
-                        open (D,">",expand_filename("~$user/export/$name.$ldev")); 
-                        print D "export=/media/$name/$ldev\n"; 
-                        close (D); 
-                } 
-                elsif ( system("mount -t hpfs $dev /media/$name/$ldev -o uid=$user,sync")==0 ) { 
-                        syslog('notice', "USB device $name ($ldev) successfully mounted (hpfs detected)"); 
-                        # if mounted, inform x2goclient about it... 
-                        system("touch $mntdir/$ldev.mounted"); 
-                        open (D,">",expand_filename("~$user/export/$name.$ldev")); 
-                        print D "export=/media/$name/$ldev\n"; 
-                        close (D); 
-                } 
-                elsif ( system("fuseext2 $dev /media/$name/$ldev -o ro,allow_other")==0 ) { 
-                        syslog('notice', "USB device $name ($ldev) successfully mounted readonly (ext*fs detected)"); 
-                        # if mounted, inform x2goclient about it... 
-                        system("touch $mntdir/$ldev.mounted"); 
-                        open (D,">",expand_filename("~$user/export/$name.$ldev")); 
-                        print D "export=/media/$name/$ldev\n"; 
-                        close (D); 
-                } 
-                else { 
-                        # the mount failed, let's assume that the device is encrypted... 
-                        my $enc=`ls -1 $mntdir | grep .encrypted`; 
-                        if ( $enc eq "" ) { 
-                                # use cryptsetup to decrypt the device... 
-                                system("/sbin/cryptsetup --key-file /etc/keys/keystick.key luksOpen $dev keystick"); 
- 
-                                # mount the ,,decrypted'' USB device via devmapper... 
-                                if ( system("mount /dev/mapper/keystick /media/$name/$ldev")==0 ) { 
-                                        # inform x2goclient about this... 
-                                        system("touch $mntdir/$ldev.encrypted"); 
-                                        system("chown -R $user /media/$name/$ldev/dsa.key"); 
-                                        open (D,">",expand_filename("~$user/logins/$name.$ldev")); 
-                                        print D "login=/media/$name/$ldev\n"; 
-                                        close (D); 
-                                        print F "encrypted mount successful ($ldev)\n"; 
-                                } 
-                                else { 
-                                        # on mount failures release the decrypted device again 
-                                        system("/sbin/cryptsetup luksClose keystick"); 
-                                        print F "mount failed ($ldev)\n"; 
-                                } 
-                        } 
-                        else { 
-                                print F "cryptodisk already present\n"; 
-                        } 
-                } 
-                if ( -e "/media/$name/$ldev" ) { 
-                        print F "detected mountpoint '/media/$name/$ldev'\n"; 
-                        print F "running '/sbin/blkid -o value -s LABEL $dev'\n"; 
-                        my $label=`/sbin/blkid -o value -s LABEL $dev`; 
-                        chomp($label); 
-                        if ($label) { 
-                                print F "symlinking '/media/$name/$ldev' and '/media/$name/$label'\n"; 
-                                unlink "/media/$name/$label" if ( -l "/media/$name/$label" ); 
-                                symlink("/media/$name/$ldev","/media/$name/$label"); 
-                                open (D,">>",expand_filename("~$user/export/$name.$ldev")); 
-                                print D "export=/media/$name/$label\n"; 
-                                close (D); 
-                        } 
-                } 
- 
-        } 
-        elsif ( $action eq "remove" ) { 
- 
-                ### 
-                ### ACTION: unmount device after it has been removed from the USB subsystem 
-                ### 
- 
-                syslog('notice', "device remove action called"); 
- 
-                # we rely on our own mount logistics here... 
-                if ( -e "$mntdir/$ldev.mounted" ) { 
-                        # inform x2goclient that the device has been removed 
-                        system ("umount -ff /media/$name/$ldev"); 
-                        unlink ("$mntdir/$ldev.mounted"); 
-                        open ( D,">",expand_filename("~$user/export/$name.$ldev.unexport")); 
-                        open (I,"<",expand_filename("~$user/export/$name.$ldev")); 
-                        while (<I>) { 
-                                $_=~s/^export=/unexport=/i; 
-                                print D $_; 
-                        } 
-                        close (I); 
-                        close (D); 
-                        syslog('notice', "USB device $name ($ldev) successfully unmounted"); 
-                } 
-                elsif ( -e "$mntdir/$ldev.encrypted" ) { 
-                        # inform x2goclient that the device has been removed 
-                        # release the encrypted device mapping 
-                        unlink ("$mntdir/$ldev.encrypted"); 
-                        open ( D,">",expand_filename("~$user/logins/$name.$ldev.unexport")); 
-                        print D "logout=/media/$name/$ldev\n"; 
-                        system("umount /media/$name/$ldev"); 
-                        system("/sbin/cryptsetup luksClose keystick"); 
-                        close (D); 
-                } 
-        } 
- 
-        close (F); 
-} else { 
- 
-        syslog('notice', "not in any thinclient mode, exiting"); 
-} 
-USBMOUNTPATCH 
-chmod 755 ./patch/includes.chroot/usr/lib/x2go/tce/x2gousbmount 
 </code> </code>
- 
 ==== Starting the Build ==== ==== Starting the Build ====
-Change to a directory where you want to save your builds, and run the following commands:<code>+In the directory where you want to save your builds, save the following file as x2go-tce-build, and run it (e.g. via //sudo bash ./x2go-tce-build//): 
 +<code> 
 +#!/bin/bash 
 + 
 +# read (source) the config file 
 +. ./x2go-tce-config 
 # Create Timestamp # Create Timestamp
 LBX2GO_TIMESTAMP=$(date +"%Y%m%d%H%M%S") LBX2GO_TIMESTAMP=$(date +"%Y%m%d%H%M%S")
 +
 +# Log all output to a logfile in /tmp
 +exec > >(tee "/tmp/$LBX2GO_TIMESTAMP.log") 2>&1
  
 # Set Directory name # Set Directory name
-LBX2GO_TCEDIR=./live-build-x2go-$LBX2GO_TIMESTAMP+LBX2GO_TCEDIR="./live-build-x2go-${LBX2GO_TIMESTAMP}-${LBX2GO_IMAGETYPE}-$(echo $LBX2GO_ARCH | awk '{print $2}')-${LBX2GO_CONFIG##*/}"
  
 if [ -z "$LBX2GO_ARCH" ] || if [ -z "$LBX2GO_ARCH" ] ||
 + ( echo "$LBX2GO_ARCH" | grep -q "arm" && [ -z "$LBX2GO_ARCH_MODEL" ] ) || 
    [ -z "$LBX2GO_SPACE" ] ||    [ -z "$LBX2GO_SPACE" ] ||
    [ -z "$LBX2GO_CONFIG" ] ||    [ -z "$LBX2GO_CONFIG" ] ||
Line 452: Line 344:
     echo -e "One or more of the following variables is unset:"     echo -e "One or more of the following variables is unset:"
     echo -e "LBX2GO_ARCH: '${LBX2GO_ARCH}'"     echo -e "LBX2GO_ARCH: '${LBX2GO_ARCH}'"
 +    echo "$LBX2GO_ARCH" | grep -q "arm" && echo -e "LBX2GO_ARCH_MODEL: '${LBX2GO_ARCH_MODEL}'"
     echo -e "LBX2GO_SPACE: '${LBX2GO_SPACE}'"     echo -e "LBX2GO_SPACE: '${LBX2GO_SPACE}'"
     echo -e "LBX2GO_DEFAULTS: '${LBX2GO_DEFAULTS}'"     echo -e "LBX2GO_DEFAULTS: '${LBX2GO_DEFAULTS}'"
Line 468: Line 361:
     cd $LBX2GO_TCEDIR     cd $LBX2GO_TCEDIR
  
 +    X2GO_LBCONFIG_STRING=$(cat <<X2GOLBCONFIGSTRING
     lb config $LBX2GO_ARCH $LBX2GO_SPACE $LBX2GO_DEFAULTS \     lb config $LBX2GO_ARCH $LBX2GO_SPACE $LBX2GO_DEFAULTS \
        --config $LBX2GO_CONFIG --binary-images $LBX2GO_IMAGETYPE \        --config $LBX2GO_CONFIG --binary-images $LBX2GO_IMAGETYPE \
-       --archive-areas "$LBX2GO_ARCHIVE_AREAS"+       --archive-areas "$LBX2GO_ARCHIVE_AREAS" 
 +       --bootappend-live "$LBX2GO_BOOTAPPEND_LIVE" 
 +X2GOLBCONFIGSTRING 
 +
 +    # Our previous way of doing this had issues with newlines and multiple blanks. So we're now doing a bit 
 +    # of sanitizing, then we eval the variable. 
 +    X2GO_LBCONFIG_STRING=$(echo "$X2GO_LBCONFIG_STRING" | tr '\n' ' ' | tr -s ' ') 
 +    eval "$X2GO_LBCONFIG_STRING" 
     # This will copy any patches we have prepared     # This will copy any patches we have prepared
     if [ -d "../patch" ] ; then     if [ -d "../patch" ] ; then
         cp -a ../patch/* config/         cp -a ../patch/* config/
     fi     fi
 +
 +    # This will copy any patches we have prepared for minidesktop
 +    if [ -d "../patch-minidesktop" ] && (echo "$LBX2GO_CONFIG" | grep -q minidesktop) ; then
 +        cp -a ../patch-minidesktop/* config/
 +    fi
 +
 +    # This checks if a bootloader directory is present (e.g. because of a custom splash.svg)
 +    # and adds all other files that might be missing (live-build won't add them automatically
 +    # if the directory already exists)
 +    if [ -d config/bootloaders ] ; then
 +        rsync -aPH --ignore-existing --exclude="splash.svg" /usr/share/live/build/bootloaders/* config/bootloaders
 +    fi
 +    # When enabled, this silences the audible beep at syslinux/isolinux/pxelinux/extlinux startup.
 +    # Note that this is an accessibility feature for blind users, so use with care.
 +    sed -e "s/$(echo -e "\07")//g" -i config/bootloaders/*/menu.cfg
 +
     # This enables an i386-only package in the sources.list file when an i386 build is requested     # This enables an i386-only package in the sources.list file when an i386 build is requested
-    if echo "$LBX2GO_ARCH| grep -q -i "i386" ; then+    if echo $LBX2GO_ARCH | grep -q -i "i386" ; then
         sed -i -e 's/# for i386 only #//' config/package-lists/desktop.list.chroot         sed -i -e 's/# for i386 only #//' config/package-lists/desktop.list.chroot
     fi     fi
-        # This is for minidesktop builds only + 
-        if [ -f config/package-lists/firefox-langpacks.list.chroot ] && [ -n "$LBX2GO_LANG" ]; then +    # This is part of our experimental ARM support 
-                for LBX2GO_SINGLE_LANG in $(echo $LBX2GO_LANG | tr ';' ' '); do +    # It adds required arm64-only packages when an arm64 build is requested 
-                        echo "LANG: '$LBX2GO_SINGLE_LANG'" +    if echo $LBX2GO_ARCH | grep -q "arm" ; then 
-                        sed -i -e 's/#firefox-esr-l10n-'$LBX2GO_SINGLE_LANG'$/firefox-esr-l10n-'$LBX2GO_SINGLE_LANG'/' config/package-lists/firefox-langpacks.list.chroot + 
-                done + # bullseye and newer do not need this 
-        fi+    if [ "${LBX2GO_DEBVERSION}" = "buster" ]; then  
 + # firmware for wifi  
 + echo "firmware-brcm80211/buster-backports" >>config/package-lists/raspi.list.chroot 
 + fi 
 + 
 + if [ "$LBX2GO_ARCH_MODEL" = "Pi3" ] ; then 
 + # modules required for Raspberry Pi 3 LAN 
 + echo "crc16" >> config/includes.chroot/etc/initramfs-tools/modules 
 + echo "mii" >> config/includes.chroot/etc/initramfs-tools/modules 
 + echo "smsc95xx" >> config/includes.chroot/etc/initramfs-tools/modules 
 + echo "usbcore" >> config/includes.chroot/etc/initramfs-tools/modules 
 + echo "usbnet" >> config/includes.chroot/etc/initramfs-tools/modules 
 + echo "fake-hwclock" >>config/package-lists/raspi.list.chroot 
 + echo "usbutils" >>config/package-lists/raspi.list.chroot 
 + 
 + # firmware for basic raspi functions - required for boot on Pi3 
 + echo "raspi3-firmware/buster" >>config/package-lists/raspi.list.chroot 
 + # standard linux kernel - for Pi3 
 + echo "linux-image-arm64/buster" >>config/package-lists/raspi.list.chroot 
 + 
 + elif [ "$LBX2GO_ARCH_MODEL" = "Pi4" ] ; then 
 + # bullseye and newer do not need this 
 + if [ "${LBX2GO_DEBVERSION}" = "buster" ]; then 
 + # firmware for basic raspi functions - required for boot on Pi4 
 + echo "raspi3-firmware/buster-backports" >>config/package-lists/raspi.list.chroot 
 + echo "raspi-firmware/buster-backports" >>config/package-lists/raspi.list.chroot 
 + 
 + # newer linux kernel - required for pi4/pi400 
 + echo "linux-image-arm64/buster-backports" >>config/package-lists/raspi.list.chroot 
 + fi 
 + else 
 + echo "WARNING: ARM Platform selected, but unknown model: '$LBX2GO_ARCH_MODEL'. Assuming no additional packages/patches are required." 
 + fi 
 +    fi 
 +  
 + 
 +    # This is for minidesktop builds only 
 +    if [ -f config/package-lists/firefox-langpacks.list.chroot ]; then 
 +            if [ -n "$LBX2GO_LANG" ]; then 
 +                    for LBX2GO_SINGLE_LANG in $(echo "$LBX2GO_LANG| tr ';' ' '); do 
 +                            echo "LANG: '$LBX2GO_SINGLE_LANG'" 
 +                            sed -i -e 's/#firefox-esr-l10n-'$LBX2GO_SINGLE_LANG'$/firefox-esr-l10n-'$LBX2GO_SINGLE_LANG'/' config/package-lists/firefox-langpacks.list.chroot 
 +                    done 
 +            else 
 +                    rm config/package-lists/firefox-langpacks.list.chroot 
 +            fi 
 +    fi
     if [ "$LBX2GO_TCE_SHRINK" = "true" ] ; then     if [ "$LBX2GO_TCE_SHRINK" = "true" ] ; then
         echo '#!/bin/sh' >./config/hooks/0112-remove-folders.hook.chroot         echo '#!/bin/sh' >./config/hooks/0112-remove-folders.hook.chroot
Line 496: Line 460:
         chmod 755 ./config/hooks/0112-remove-folders.hook.chroot         chmod 755 ./config/hooks/0112-remove-folders.hook.chroot
     fi     fi
 +
 +    if [ -n "$LB_APT_HTTP_PROXY" ] || [ -n "$LB_APT_FTP_PROXY" ]; then
 +        echo "NOTICE: apt proxy variable(s) is/are set."
 +        echo "NOTICE: Trying to use the proxy for all downloads."
 +        echo "NOTICE: If this fails, look for #SETPROXY in the $0 source."
 +        # Here, we should have reached a point where it is safe to point all proxy variables
 +        # at the apt-cacher-ng proxy.  If you're seeing errors during your build that hint
 +        # at files not being downloaded, disable these three entries.
 +        export https_proxy=$LB_APT_HTTP_PROXY
 + export http_proxy=$LB_APT_HTTP_PROXY
 +        export ftp_proxy=$LB_APT_FTP_PROXY
 +    fi
 +
 +    # This is part of our experimental ARM support
 +    # It is used when building for the ARM architecture (on Intel/AMD hardware and on ARM).
 +    # It makes some necessary changes, and also tries to speed up squashfs creation when it 
 +    # detects a crossbuild environment.
 +    if echo $LBX2GO_ARCH | grep -q 'arm'; then
 +
 +        # This command removes all references to fuseext, freerdp-nightly, and x2gothinclient from the
 +        # package list files.  Currently needed as there are no ARM packages for any of these.
 +        echo "WARNING: Removing all references to fuseext,freerdp-nightly and x2gothinclient from the build."
 +        sed -e 's/^.*fuseext.*$//g' -e 's/^.*freerdp-nightly.*$//g' -e 's/^.*x2gothinclient.*$//g' -i ./config/package-lists/*
 +
 + # This command removes the X2Go repository from the directory where additional
 +        # archives are stored.  Currently needed as the X2Go repository offers no arm64 
 +        # packages, but Debian Buster does - so that's what we're falling back to.
 +        echo "WARNING: Removing all references to the X2Go repository from the build."
 +        rm ./config/archives/*x2go*
 +
 + # The following is a hack to reduce squashfs creation time in a crossbuild environment.
 + # We're replacing mksquashfs in the changeroot with a wrapper script that drops the 
 + # original mksquashfs call into a file.
 +
 + if (uname -r | grep -q 'i.86' || uname -r | grep -q 'amd64') ; then
 + # We need to do this as a background task, waiting for the mksquashfs executable to
 + # appear in the changeroot; as the changeroot will only be created later on, once
 + # lb build is called.
 +
 + # The other background task waits until the command file has been created, then
 + # it applies some necessary patches to it, and starts the mksquashfs command natively
 + # on the build host, rather than in the changeroot environment.
 + # This is because in the changeroot, we'd be running the ARM mksquashfs in a qemu
 + # software emulation of the ARM architecture, while on the host, we can use all the
 + # native, raw CPU power and cores available to us.
 +
 + # To make sure we don't have any lingering processes in the background, we're passing
 + # our own PID along to the background tasks, and tell them to terminate if our PID
 + # disappears while they're still in their waiting/looping state.
 +
 + MASTERPID=$$
 +
 + # Replace mksquashfs in chroot with script
 + # (script will undo this upon completion)
 + (
 +     # wait until the chroot has been populated or until our parent process dies
 +     while ! [ -x ./chroot/usr/bin/mksquashfs ]; do
 + ps $MASTERPID >/dev/null || exit 1
 + sleep 1
 +     done
 +     # make sure we don't overwrite the real executable if it has already been
 +     # moved out of the way
 +     if ! [ -x ./chroot/usr/bin/mksquashfs.real ]; then
 + cp ./chroot/usr/bin/mksquashfs ./chroot/usr/bin/mksquashfs.real
 +     fi
 +    echo '#!/bin/bash' >./chroot/usr/bin/mksquashfs
 +    # log the name we've been called with and all parameters into this file
 +    echo 'echo "$0 $@" >/tmp/filesystem.squashfs.temp' >>./chroot/usr/bin/mksquashfs
 +    # once the native mksquashfs is complete, we will remove this file
 +    echo 'while [ -f /tmp/filesystem.squashfs.temp ]; do' >>./chroot/usr/bin/mksquashfs
 +    echo '        sleep 1' >>./chroot/usr/bin/mksquashfs
 +    echo 'done' >>./chroot/usr/bin/mksquashfs
 +    # so let's wait until it has been removed before deleting ourselves ...
 +    echo 'rm /usr/bin/mksquashfs' >>./chroot/usr/bin/mksquashfs
 +    # ... and moving the real executable back into its place
 +    echo 'mv /usr/bin/mksquashfs.real /usr/bin/mksquashfs' >>./chroot/usr/bin/mksquashfs
 +    chmod 755 ./chroot/usr/bin/mksquashfs
 + ) &
 +
 + # start the native mksquashfs after patching the parameters
 + (
 +     # wait until the trigger file has been created or until our parent process dies
 +     while ! [ -f ./chroot/tmp/filesystem.squashfs.temp ]; do
 + ps $MASTERPID >/dev/null || exit 1
 + sleep 1
 +     done
 +     # using any of the available filters (x86, arm, armthumb) for the 
 +     # -Xbcj command results in an unusable squashfs on arm, so we drop the 
 +     # parameter completely if it's there.
 +     # also, all absolute paths (detected by beginning with " /") need to be
 +     # prefixed with "./chroot" so the mksquashfs outside the chroot knows where
 +     # to look for the corresponding paths/files.
 +     sed -e 's/ -Xbcj x86/ /g' -e 's# /# ./chroot/#g' -i \
 + ./chroot/tmp/filesystem.squashfs.temp
 +     #needs switch from e.g. /bin/mksquashfs to $(which mksquashfs)
 +     sed -e "s#^.*mksquashfs#$(which mksquashfs)#g" -i \
 + ./chroot/tmp/filesystem.squashfs.temp
 +     # now let's make this executable
 +     chmod 755 ./chroot/tmp/filesystem.squashfs.temp
 +
 +     # we also need to add some more excludes because they shouldn't end up
 +     # in the squashfs - no idea why we don't need them while inside the chroot ...
 +     echo 'proc/*' >>./chroot/excludes
 +     echo 'sys/*' >>./chroot/excludes
 +     echo 'dev/pts/*' >>/.chroot.excludes
 +     # now let's execute the script and, if it terminates without an error,
 +     # we'll move the newly created squashfs into the chroot where the chrooted
 +     # mksquashfs command would have created it; if that worked as well, we'll
 +     # remove the script file so our dummy mksquashfs inside the chroot knows
 +     # it's time to terminate itself.
 +     ./chroot/tmp/filesystem.squashfs.temp && \
 +     mv ./filesystem.squashfs ./chroot/ && \
 +     rm ./chroot/tmp/filesystem.squashfs.temp
 + ) &
 + fi
 +    fi
 +
     if lb build ; then     if lb build ; then
         echo -e "Build is done: '$LBX2GO_TCEDIR'"         echo -e "Build is done: '$LBX2GO_TCEDIR'"
 +        ln $(realpath ./chroot/vmlinuz) ./x2go-tce-vmlinuz
 +        ln $(realpath ./chroot/initrd.img) ./x2go-tce-initrd.img
         ln ./binary/live/filesystem.squashfs ./x2go-tce-filesystem.squashfs         ln ./binary/live/filesystem.squashfs ./x2go-tce-filesystem.squashfs
 +
 +        if [ "$LBX2GO_IMAGETYPE" = "hdd" ] ; then
 +                ln ./live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').img \
 +                   ./x2go-tce-live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').img
 +        fi
 +
 +        # This is part of our experimental ARM support
 +        if [ "$LBX2GO_IMAGETYPE" = "hdd" ] && echo $LBX2GO_ARCH | grep -q "arm" ; then
 + # after the build, let's determine the name of our image file ...
 + IMAGEFILE="./x2go-tce-live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').img"
 +
 + # ... and change the partition type to reflect the file system actually in use for partition 1
 + # ("b" is FAT32)
 + sfdisk --part-type $IMAGEFILE 1 b
 +
 + # next, we need to patch two things inside the image, so we need to set up a loop device for it.
 + FREELOOP=$(losetup -f) # note that this could become a TOCTOU issue if more than 1 process tries to use loop devices
 +
 + # as the image is a full disk image containing a partition, we need to jump to the position where the first partition starts
 + losetup -o 1048576 $FREELOOP $IMAGEFILE
 +
 + # now let's mount it
 + mkdir -p ./tempmount
 + mount $FREELOOP ./tempmount
 +
 + # purge this dir, so we have enough space; we'll return to fill it later
 + rm ./tempmount/live/*
 +
 + # first, we copy the contents of the boot/firmware/ folder to the root directory, because that is where these files are needed
 + # see if inplace helps against out of space errors
 + rsync -aP --inplace ./chroot/boot/firmware/* ./tempmount
 +
 + mkdir -p ./tempmount/live/
 + rsync -aP ./binary/live/*.squashfs ./tempmount/live/
 +
 + # next, we replace the "root=" parameter with the parameters needed for live-booting
 + sed -e 's#root=/dev/mmcblk0p2 #'"$LBX2GO_BOOTAPPEND_LIVE"' #' -i ./tempmount/cmdline.txt
 +
 + # here comes the cleanup part
 + sync
 + umount $FREELOOP
 + losetup -d $FREELOOP
 + rmdir ./tempmount
 + fi
 +
         if [ "$LBX2GO_IMAGETYPE" = "netboot" ] ; then         if [ "$LBX2GO_IMAGETYPE" = "netboot" ] ; then
-            ln ./tftpboot/live/vmlinuz ./x2go-tce-vmlinuz 
-            ln ./tftpboot/live/initrd.img ./x2go-tce-initrd.img 
             if [ "$LBX2GO_NOSQUASHFS" = "true" ] ; then             if [ "$LBX2GO_NOSQUASHFS" = "true" ] ; then
                 (cd binary; echo live$'\n'live/filesystem.squashfs |cpio -o -H newc | gzip --fast) >./x2go-tce-filesystem.cpio.gz                 (cd binary; echo live$'\n'live/filesystem.squashfs |cpio -o -H newc | gzip --fast) >./x2go-tce-filesystem.cpio.gz
-                cat ./x2go-tce-initrd.img ./x2go-tce-filesystem.cpio.gz >./x2go-tce-initrd-with-fs.img +                cat ./x2go-tce-initrd.img ./x2go-tce-filesystem.cpio.gz >./x2go-tce-initrd-with-fs.img || exit 1 
-                rm ./x2go-tce-filesystem.cpio.gz ./x2go-tce-filesystem.squashfs ./x2go-tce-initrd.img+                rm ./x2go-tce-filesystem.cpio.gz 
 +                # keeping these doesn't hurt, but feel free to rm them as well 
 +                # rm ./x2go-tce-filesystem.squashfs ./x2go-tce-initrd.img
             fi             fi
         fi         fi
         if [ "$LBX2GO_IMAGETYPE" = "iso" ] || [ "$LBX2GO_IMAGETYPE" = "iso-hybrid" ] ; then         if [ "$LBX2GO_IMAGETYPE" = "iso" ] || [ "$LBX2GO_IMAGETYPE" = "iso-hybrid" ] ; then
-            ln ./binary/live/vmlinuz ./x2go-tce-vmlinuz 
-            ln ./binary/live/initrd.img ./x2go-tce-initrd.img 
             genisoimage -o ./x2go-tce-squashfs-only.iso -R -J -graft-points live/filesystem.squashfs=./x2go-tce-filesystem.squashfs             genisoimage -o ./x2go-tce-squashfs-only.iso -R -J -graft-points live/filesystem.squashfs=./x2go-tce-filesystem.squashfs
-            [ -e ./live-image-amd64.hybrid.iso ] && ln ./live-image-amd64.hybrid.iso ./original-x2go-tce-live-image-amd64.hybrid.iso +            if [ -e ./live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').hybrid.iso ] ; then 
-            [ -e ./live-image-amd64.iso ] && ln ./live-image-amd64.iso ./original-x2go-tce-live-image-amd64.iso +                    ln ./live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').hybrid.iso 
-            [ -e ./live-image-i386.hybrid.iso ] && ln ./live-image-i386.hybrid.iso ./original-x2go-tce-live-image-i386.hybrid.iso +                       ./original-x2go-tce-live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').hybrid.iso 
-            [ -e ./live-image-i386.iso ] && ln ./live-image-i386.iso ./original-x2go-tce-live-image-i386.iso+            elif [ -e ./live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').iso ] ; then 
 +                    ln ./live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').iso \ 
 +                       ./original-x2go-tce-live-image-$(echo $LBX2GO_ARCH | awk '{print $2}').iso 
 +            fi
             mv ./x2go-tce-filesystem.squashfs ./original-x2go-tce-filesystem.squashfs             mv ./x2go-tce-filesystem.squashfs ./original-x2go-tce-filesystem.squashfs
         fi         fi
Line 521: Line 650:
         stat -c %Y ./config/includes.chroot/lib >./x2go-tce-timestamp         stat -c %Y ./config/includes.chroot/lib >./x2go-tce-timestamp
         touch -m -d @$(cat x2go-tce-timestamp) x2go-tce-timestamp         touch -m -d @$(cat x2go-tce-timestamp) x2go-tce-timestamp
-        lb clean +        if [ "$LBX2GO_GETSRC" = "true" ] ; then 
-        rm -rf ./cache+                if lb source debian ; 
 +                then 
 +                        echo -e "Source files have been downloaded: '$LBX2GO_TCEDIR'" 
 +                else 
 +                        echo -e "Source download failed: '$LBX2GO_TCEDIR'" 
 +                fi 
 +        else 
 +                lb clean 
 +                rm -rf ./cache 
 +        fi
     else     else
-        # note that imagetype hdd always ends here, 
-        # due to a harmless error that can be safely ignored, but which sets the error code to != 0 
         echo -e "Build failed: '$LBX2GO_TCEDIR'"         echo -e "Build failed: '$LBX2GO_TCEDIR'"
 +        if [ "$LBX2GO_IMAGETYPE" = "hdd" ] ; then
 +                echo "Looks like you tried to build an hdd image."
 +                echo "Older (pre-Debian-Buster) releases of live-build show a harmless error during"
 +                echo "the build, that can be safely ignored - but will still get you a 'Build failed'"
 +                echo "message in turn. So if you're running an older Debian release, you might want to"
 +                echo "look at the content of your build directory - maybe your build was successful"
 +                echo "after all, and this script was merely unable to detect it (computers are dumb)."
 +        fi
     fi     fi
     cd ..     cd ..
 fi fi
 +
  
 </code> </code>
Line 539: Line 684:
     * It **might** be possible to already use HTTPS in this early stage when using iPXE.  This is untested and requires building your own iPXE image. see http://ipxe.org/crypto for details. Alternatively, use ipxe.lkrn (from [[http://boot.ipxe.org/ipxe.lkrn]]) and pxelinux.0 in combination with scripted ipxe commands in the pxelinux.cfg.     * It **might** be possible to already use HTTPS in this early stage when using iPXE.  This is untested and requires building your own iPXE image. see http://ipxe.org/crypto for details. Alternatively, use ipxe.lkrn (from [[http://boot.ipxe.org/ipxe.lkrn]]) and pxelinux.0 in combination with scripted ipxe commands in the pxelinux.cfg.
   * You will also need an HTTP/HTTPS/FTP server with a dedicated IP (no name-based virtual hosts) for the squashfs image. - **Note:** set LBX2GO_NOSQUASHFS=true and use iPXE (e.g. with ipxe.lkrn + pxelinux.0) if you cannot use an IP for your host. Another option (untested) is explained [[https://blog.jacekk.info/2016/01/debian-live-webboot-dns/|here]]   * You will also need an HTTP/HTTPS/FTP server with a dedicated IP (no name-based virtual hosts) for the squashfs image. - **Note:** set LBX2GO_NOSQUASHFS=true and use iPXE (e.g. with ipxe.lkrn + pxelinux.0) if you cannot use an IP for your host. Another option (untested) is explained [[https://blog.jacekk.info/2016/01/debian-live-webboot-dns/|here]]
-    * This image cannot be deployed via TFTP as it is too large - some TFTP servers refuse to serve files lager than 32MB, and some TFTP clients have problems with that as well.+    * This image cannot be deployed via TFTP as it is too large - some TFTP servers (atftpd in particular) refuse to serve files lager than 32MB, and some TFTP clients have problems with that as well.
     * Also, even if you have a TFTP server/client combination that handles files larger than 32 MB, it will still be waaaay slower than the HTTP/FTP transfer.     * Also, even if you have a TFTP server/client combination that handles files larger than 32 MB, it will still be waaaay slower than the HTTP/FTP transfer.
     * Note that whoever manages to spoof this server name can deploy rogue images to your ThinClients.  If this is a serious issue for you, consider using local storage media and the autoupdater instead.     * Note that whoever manages to spoof this server name can deploy rogue images to your ThinClients.  If this is a serious issue for you, consider using local storage media and the autoupdater instead.
Line 603: Line 748:
 === Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server === === Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server ===
 Again, this is assuming you already have an existing, working HTTP or FTP server setup. Again, this is assuming you already have an existing, working HTTP or FTP server setup.
-  * run X2GoClient on any computer you like, and configure a session the same way it should appear on the ThinClient <note tip>when using a Windows client, run x2goclient.exe --portable, or it will store the session information in the registry, rather than in a "sessions" file.</note>+  * run X2GoClient on any computer you like, and configure a session the same way it should appear on the ThinClient 
 + <note tip>when using a Windows client, run x2goclient.exe --portable, or it will store the session information in the registry, rather than in a "sessions" file.</note> 
   * locate the "sessions" file you just created - it should be at ~/.x2goclient/sessions   * locate the "sessions" file you just created - it should be at ~/.x2goclient/sessions
   * copy it to x2go-tce.sessions   * copy it to x2go-tce.sessions
Line 880: Line 1027:
   * ''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.   * ''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.   * ''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)+  * ''blankdpmsfix'' - This forces the TFT to 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.   * ''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 FAT/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)+  * ''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. Earlyblankdpmsfix can also be called as ''earlyblankdpmsfix=nnnn'', where ''nnnn'' is the blanking time in milliseconds (so, ''earlyblankdpmsfix=1500'' equals 1.5 seconds). (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"''   * ''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"''
 +  * ''initrdblankdpmsfix'' is the same as ''earlyblankdpmsfix'', only that it activates in the initial ramdisk already. Like ''earlyblankdpmsfix'', it can also be called as ''initrdblankdpmsfix=nnnn'' This parameter is useful if you are affected by the //black screen at boot// issue, and you are not combining squashfs and initrd into one file when netbooting. (feature available via github repo, soon via x2go repo too)
   * ''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.   * ''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   * ''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
Line 891: Line 1039:
   * ''nomagicpixel=1'' or ''nomagicpixel=2'' - you should set ''nomagicpixel=1'' while the "magic pixel" (clicking in the upper right corner of the screen will minimize a fullscreen session) is still active in thinclient mode (this feature is expected to be disabled at some point in the future). ''nomagicpixel=1'' will disable the window manager when exactly 3 windows are detected (that's the usual situation when a fullscreen session is active). It will re-enable openbox whenever more or less than 3 windows are detected. If this fails for you, you can try ''nomagicpixel=2'', which will try to trigger on the window-minimize command and restore it to fullscreen (this will cause a short screen flickering effect). Note that ''nomagicpixel=2'' will make your ThinClient unusable when trying to run the actual X2Go-TCE client as a virtual machine guest (the //X2GoServer// you connect to may be a VM guest, no problems there). To live with the magic pixel bug, simply do not add this option at all.   * ''nomagicpixel=1'' or ''nomagicpixel=2'' - you should set ''nomagicpixel=1'' while the "magic pixel" (clicking in the upper right corner of the screen will minimize a fullscreen session) is still active in thinclient mode (this feature is expected to be disabled at some point in the future). ''nomagicpixel=1'' will disable the window manager when exactly 3 windows are detected (that's the usual situation when a fullscreen session is active). It will re-enable openbox whenever more or less than 3 windows are detected. If this fails for you, you can try ''nomagicpixel=2'', which will try to trigger on the window-minimize command and restore it to fullscreen (this will cause a short screen flickering effect). Note that ''nomagicpixel=2'' will make your ThinClient unusable when trying to run the actual X2Go-TCE client as a virtual machine guest (the //X2GoServer// you connect to may be a VM guest, no problems there). To live with the magic pixel bug, simply do not add this option at all.
   * ''ntp="server1 server2 ... servern"'' - this allows you to specify your own NTP server.  If this parameter is not used, time will be synced with standard Debian NTP servers.  To disable NTP syncing entirely, use ''ntp=false'' (feature available via github repo, soon via x2go repo too)   * ''ntp="server1 server2 ... servern"'' - this allows you to specify your own NTP server.  If this parameter is not used, time will be synced with standard Debian NTP servers.  To disable NTP syncing entirely, use ''ntp=false'' (feature available via github repo, soon via x2go repo too)
 +  * ''pavol=[n:]volume%[|[n:]volume% ...]'' - Allows you to set default volume levels for one or more audio output devices. ''pavol=50%'' will set the default audio output device (#0) to 50%. ''pavol=1:99%'' will set audio output device #1 to 99%. ''pavol="0:50%|1:99%"'' will set audio output device #0 to 50%, and audio output device #1 to 99%. Note that this opion only makes sense in MATE-MiniDesktop mode, as regular TCE sessions get their volume levels restored from the host they connect to. (''pavol'' feature available via github repo, soon via x2go repo too).
   * ''pubkey=tftp|http|https|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.authorized_keys'' - Allows you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.  **Attention: Whoever manages to spoof this server name will have root access to your ThinClients.** Using HTTPS will mitigate this - an attacker would not only have to spoof the server name, but also the matching certificate.   * ''pubkey=tftp|http|https|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.authorized_keys'' - Allows you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.  **Attention: Whoever manages to spoof this server name will have root access to your ThinClients.** Using HTTPS will mitigate this - an attacker would not only have to spoof the server name, but also the matching certificate.
   *  ''session=sessionname'' - use this to specify a session by name that should be pre-selected on startup. The name must be listed in the sessions file and may only contain characters from the following charset: //a-zA-Z0-9.:/ _-// (We suggest naming the default session ''default'' and using ''session=default''.) When using a session name with blanks, please enclose the sessionname in either single or double quotes, like so: ''session="session name"'' / ''session='session name'''   *  ''session=sessionname'' - use this to specify a session by name that should be pre-selected on startup. The name must be listed in the sessions file and may only contain characters from the following charset: //a-zA-Z0-9.:/ _-// (We suggest naming the default session ''default'' and using ''session=default''.) When using a session name with blanks, please enclose the sessionname in either single or double quotes, like so: ''session="session name"'' / ''session='session name'''
Line 897: Line 1046:
   * ''tcpprintonlyfrom=x.x.x.x'' - Will allow you to specify which IP address may connect to Port 9100 and above for printing to a locally attached LPT/USB printer. This should be the IP of your CUPS server or whatever print server system you use.  Understands the same syntax as ''xinetd'''s ''only_from''   * ''tcpprintonlyfrom=x.x.x.x'' - Will allow you to specify which IP address may connect to Port 9100 and above for printing to a locally attached LPT/USB printer. This should be the IP of your CUPS server or whatever print server system you use.  Understands the same syntax as ''xinetd'''s ''only_from''
   * ''throttle=n|n:n:n:n:n'' - Will throttle down- and upload speed (''throttle=n'') or set throttling limits as follows: download:upload:smoothingtime:smoothinglength:latency. Defaults for up- and download are 10 (KiloBytes/s), 3.0 (seconds, using decimals is permitted) smoothingtime, 20 (KiloBytes), 0 (ms). for a detailed description of these parameters, see "man trickle". You can use the first 1, 2, 3, 4 or all 5 parameters. To set down- and/or upload speed to unlimited, use the letter "u" instead of a numeric value.   * ''throttle=n|n:n:n:n:n'' - Will throttle down- and upload speed (''throttle=n'') or set throttling limits as follows: download:upload:smoothingtime:smoothinglength:latency. Defaults for up- and download are 10 (KiloBytes/s), 3.0 (seconds, using decimals is permitted) smoothingtime, 20 (KiloBytes), 0 (ms). for a detailed description of these parameters, see "man trickle". You can use the first 1, 2, 3, 4 or all 5 parameters. To set down- and/or upload speed to unlimited, use the letter "u" instead of a numeric value.
 +  * ''timezone=TIMEZONE'' - can be used to define a timezone other than UTC, e.g. 'Europe/Berlin'. This especially makes sense for MATE-MiniDesktop, but is nice to have in regular TCE-Live as well, because the timestamp of the log messages will show the local time instead of UTC. This is a standard parameter of live-boot, and not specific to X2Go.
 +  * ''windowwidth=[n-nnn]'' - this is only available in MiniDesktop mode. It allows you to set the width of the X2GoClient login window (which gets moved and resized to the right side of your screen during session startup) to any value between 0 and 100. Note that widths smaller than 30 are not recommended and may cause further resizing once the session starts.
 +  * ''x3270servers="host[:port][|host[:port]...]"'' - this is only available in MiniDesktop mode. It allows you to specify one or more hosts (with optional ports) for x3270 terminal emulation sessions that will be created as desktop shortcuts on the thinclient. For a default 3270 connection, the port is 23 (telnet) and does not need to be specified. For an SSL-encrypted connection (recommended), the port is 992. Hosts may be IP addresses or DNS names, and need to be separated with a ''|''. (feature available via github repo, soon via x2go repo too)
 +  * ''x5250servers="host[:port][|host[:port]...]"'' - this is only available in MiniDesktop mode. It allows you to specify one or more hosts (with optional ports) for x5250 terminal emulation sessions that will be created as desktop shortcuts on the thinclient. For a default 5250 connection, the port is 23 (telnet) and does not need to be specified. For an SSL-encrypted connection (recommended), the port is 992. Hosts may be IP addresses or DNS names, and need to be separated with a ''|''. Note that x5250 support is currently not part of the standard image available via git, as there is no x5250 executable in Debian. You can try using x3270 instead, most modern IBM i (System i, iSeries, AS/400) systems support 3270-type connections as well. If you need native 5250 support, say, with a commercial, closed-source 5250 terminal emulator, please leave a message on the X2Go-User Mailing List and we'll tell you if and how you can integrate that into your build. (feature available via github repo, soon via x2go repo too)
   * ''xinerama=left-of|right-of|above|below|same-as'' - Allows you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen). Note that the current implementation will enforce "same-as" if it detects a touch screen driver (wacom) and no other pointing device. This is so you won't get stuck being unable to log off, for example, due to your touch device being limited to one screen.   * ''xinerama=left-of|right-of|above|below|same-as'' - Allows you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen). Note that the current implementation will enforce "same-as" if it detects a touch screen driver (wacom) and no other pointing device. This is so you won't get stuck being unable to log off, for example, due to your touch device being limited to one screen.
-  * ''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+  * ''xorg-driver=DRIVERNAME'' - will skip graphics driver autodetection and force the specified driver instead. This is a standard parameter of live-boot, and not specific to X2Go. 
 +  * ''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 is a standard parameter of live-boot, and not specific to X2Go.
   * ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.xorg.conf'' - when a client outright refuses to boot into the graphical X2Go login screen, but gets stuck at the console or a black screen instead, yet you can get the GUI to work using a regular Linux on the same hardware, you can disable the X Server's autodetection and force it to use the xorg.conf specified here.  Note that you should use a more descriptive name for the file, as described below. **Attention: Whoever manages to spoof the server name can inject rogue xorg config files into your ThinClients.**  To mitigate this risk, use HTTPS, where the attacker would have to spoof both server name and matching certificate.   * ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.xorg.conf'' - when a client outright refuses to boot into the graphical X2Go login screen, but gets stuck at the console or a black screen instead, yet you can get the GUI to work using a regular Linux on the same hardware, you can disable the X Server's autodetection and force it to use the xorg.conf specified here.  Note that you should use a more descriptive name for the file, as described below. **Attention: Whoever manages to spoof the server name can inject rogue xorg config files into your ThinClients.**  To mitigate this risk, use HTTPS, where the attacker would have to spoof both server name and matching certificate.
 +  * ''xroot=[0xaabbcc|URI1[|URI2|...]]'' - can be used to set a local desktop background image or color (in hex format, with leading 0x, not leading #). On the main screen, this is only visible during startup, while additional screens will display whatever is set for them when there is no active session. The background also becomes visible for a short moment when the optional local screensaver activates or deactivates. Specifying more than one image will cause the first image to show up on the first screen, the second image on the second screen, and so on (feature available via github repo, soon via x2go repo too). 
 +  * ''xrootmode=center|fill|scale|tile'' can be used to determine how the local desktop background image(s) should be positioned. If the parameter has been set, but something is wrong, it will default to a //grey mesh// background. (feature available via github repo, soon via x2go repo too). (feature available via github repo, soon via x2go repo too) 
 +  * ''xsaveridletime=n'' - this value determines how long the screen should have been idle before the local slideshow screensaver sets in (value given in seconds). We recommend using 60 seconds less than for the server-sided, locking screensaver. (feature available via github repo, soon via x2go repo too) 
 +  * ''xsaverimages=[URI1[|URI2|...]]'' - if you want a local, non-locking slideshow screensaver, you can specify image URLs here. These Images will be downloaded once, at boot. That way, one can display a slideshow without having to push the images across the network every time. Especially for slow links, this is the recommended way of running a slideshow screensaver. For security, combine this with a locking screensaver on the server with only one slide or a black background. (feature available via github repo, soon via x2go repo too) 
 +  * ''xsaverimgtime=n'' - this determines how long each slide of the local, non-locking screensaver will be shown. (feature available via github repo, soon via x2go repo too)
 === These are only intended to be used with TCE images stored on local media === === These are only intended to be used with TCE images stored on local media ===
   * ''bwlimit=nnn'' - Will allow you to specify a bandwidth limit (valid values: 1-100) in percent for the backgrounded update task.   * ''bwlimit=nnn'' - Will allow you to specify a bandwidth limit (valid values: 1-100) in percent for the backgrounded update task.
Line 907: Line 1065:
   * ''updateurl=rsync|https|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used. Regardless of NTFS or not, the updater requires three directories: ''/boot/X2Go-live1, /boot/X2Go-live2, /boot/X2Go-live-download''. **Attention: Whoever manages to spoof the server name can deploy rogue images to your ThinClients.**  Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files.    * ''updateurl=rsync|https|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used. Regardless of NTFS or not, the updater requires three directories: ''/boot/X2Go-live1, /boot/X2Go-live2, /boot/X2Go-live-download''. **Attention: Whoever manages to spoof the server name can deploy rogue images to your ThinClients.**  Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files. 
  
 +===== Client Branding/Theming using SVGs =====
 +It is possible to make X2Go-TCE-Live match your Corporate Design/Corporate Identity, using the "background" and "branding" parameters.
 +This is actually a feature of X2GoClient itself, so it will also work on //fat client// installations, and even on Windows and macOS.
 +
 +{{:wiki:advanced:x2goclientdefaultbranding.png?400|Before ...}} {{:wiki:advanced:x2goclientbranding.png?400| ... and after.}}
 +
 +You can find a more detailed explanation in the [[wiki:advanced:branding-theming|corresponding X2Go Wiki page]].
 ===== Querying X2Go-TCE version info =====  ===== Querying X2Go-TCE version info ===== 
 images built using the https://github.com/LinuxHaus/live-build-x2go::feature/openbox repository/branch after 2017-07-27 10:50 UTC will create a file ''/var/run/x2go-timestamps''. images built using the https://github.com/LinuxHaus/live-build-x2go::feature/openbox repository/branch after 2017-07-27 10:50 UTC will create a file ''/var/run/x2go-timestamps''.
Line 963: Line 1128:
     * create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware".     * create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware".
   * In your boot configuration file (either "name-of-your-stubborn-hardware", when using netbooting, or menu.lst, when using local or USB storage media and grub-legacy, or X2Go-live1.cfg/X2Go-live2.cfg, when using local or USB storage media and syslinux), add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware''   * In your boot configuration file (either "name-of-your-stubborn-hardware", when using netbooting, or menu.lst, when using local or USB storage media and grub-legacy, or X2Go-live1.cfg/X2Go-live2.cfg, when using local or USB storage media and syslinux), add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware''
 +
 +==== The session itself works fine, but Audio is not working ====
 +
 +First, check that the audio isn't simply muted (some cards/setups do this by default). Run ''pavucontrol'' inside the X2Go session. Check the settings on the tabs //Output Devices// and //Configuration// If that is the case, you probably need to create a script on the server that raises the volume/toggles the mute setting upon user login.
 +
 +If that doesn't help, please boot with additional boot parameter ''audioout=list'' and look at the output on /dev/tty8 (Hit Ctrl+Alt+F8) - it will give you a list of available audio output devices.  This list also gets written to ''/tmp/audiolog'' on the ThinClient.
 +
 +You might have to pick a different one from the list, by using boot parameter ''audioout='' with a particular card/output value, like: ''audioout=“alsa_card.pci-0000_00_1b.0|output:hdmi-stereo”'' (you need to copy the proper value from the list generated on your particular thinclient).
 +
 +If you need different settings for different manufacturers, you can try to tell them apart by MAC address and set separate pxe boot configuration files for them.
  
 ===== Support Tools available in X2Go-TCE ===== ===== Support Tools available in X2Go-TCE =====
Line 1114: Line 1289:
 </file> </file>
   * after you have prepared all this, execute ''service rsync start''   * after you have prepared all this, execute ''service rsync start''
-  * Note that whoever manages to spoof the server name can deploy rogue images to your ThinClients.  Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files. +  * Note that whoever manages to spoof the server name can deploy rogue images to your ThinClients.  Even though it is slower, using an HTTPS web server is the safer way of doing this. Be sure that your web server delivers a last-modified header for all files.  In future, support for rsyncd via stunnel might be added, if the rsync project does not add native SSL support to rsyncd before that.
  
 FIXME Some of the optional steps above could be moved to a separate subpage to reduce clutter. FIXME Some of the optional steps above could be moved to a separate subpage to reduce clutter.
Line 1133: Line 1308:
  
 FIXME autodetection for SSH Private Keys might need some more bells and whistles. FIXME autodetection for SSH Private Keys might need some more bells and whistles.
-<del>For USB media, this may require adding an automounter.</del> 
   * how about a script that patches the sessions file to enable autologin for all sessions when keys have been found?   * how about a script that patches the sessions file to enable autologin for all sessions when keys have been found?
   * 2800-x2go-thinclientconfig needs to be changed so it uses the keyfile(s) when in broker mode (''--broker-ssh-key'')   * 2800-x2go-thinclientconfig needs to be changed so it uses the keyfile(s) when in broker mode (''--broker-ssh-key'')
-  * <del>directory scan </del> 
-    * <del>should we abort on first match?</del> 
-  * <del>how do we treat multiple keys?</del> 
-    * <del>no keys on USB and exactly one key on disk -> use key</del> 
-    * <del>exactly one key on USB -> takes precedence over key/keys found on disk? Or present chooser based on gxmessage?</del> 
-    * <del>multiple keys -> Present chooser based on gxmessage?</del> 
-  * <del>problem with gxmessage as chooser is that it can only display 6 buttons on 640x480 (Which we should assume as minimum screen size)</del> 
-    * <del>4 key choices, back, next?</del> 
-  * <del>oooooor we might just load all keys into ssh-agent and let it figure out which one it needs?</del> 
-    * <del>next problem: How do we prompt for passwords of such keys?</del> 
   * Situation: We have a working automounter, and ''copysecring'' will copy all keys found to the live-user's homedir under .ssh:   * Situation: We have a working automounter, and ''copysecring'' will copy all keys found to the live-user's homedir under .ssh:
     * If a session is set to "Try auto login (via SSH Agent or default SSH key)" and NO keyfile is set, then X2GoClient will try **all** secret keys in .ssh. Showing a password prompt if a key is password-protected is handled by X2GoClient, so needs no extra work.     * If a session is set to "Try auto login (via SSH Agent or default SSH key)" and NO keyfile is set, then X2GoClient will try **all** secret keys in .ssh. Showing a password prompt if a key is password-protected is handled by X2GoClient, so needs no extra work.
Line 1151: Line 1315:
       * use ''~/.ssh/keyfilename'' as path and use ''copysecring'', or       * use ''~/.ssh/keyfilename'' as path and use ''copysecring'', or
       * do not use ''copysecring'' and use ''/media/vendor_model_name/sdxn/path/to/keyfile'' (or ''/media/vendor_model_name/partlabel/path/to/keyfile'', if you assigned a partition label - which is recommended for this use case) as keyfile path/name       * do not use ''copysecring'' and use ''/media/vendor_model_name/sdxn/path/to/keyfile'' (or ''/media/vendor_model_name/partlabel/path/to/keyfile'', if you assigned a partition label - which is recommended for this use case) as keyfile path/name
- 
-FIXME copying ssh private keys seems to fail in MiniDesktop-Mode - possibly because of the priming/pruning/cleanup action performed on the homedirectory by the minidesktop init scripts? 
- 
-FIXME ''2200-xserver-xorg-getxorgconf'' should be taught to understand ''file:<nowiki>//</nowiki>'' URLs. 
  
 FIXME Parsing the output of e.g. <code>udevadm info --query path /dev/sdb FIXME Parsing the output of e.g. <code>udevadm info --query path /dev/sdb
Line 1161: Line 1321:
 Authentification and "hard" identification could be implemented using OpenPGP cards, ''scdaemon'' and a script based on ''/usr/share/doc/scdaemon/examples/scd-event''. For Status ''NOCARD'', suspend the session (kill x2goclient or send a signal that means "suspend", if available, or maybe sighup nxproxy), for status ''USABLE'', run ''gpg --card-status 2>&1 | awk '$1=="Serial" && $2=="number" {print $4}''' to determine the card's serial number, then act based on that (pull new sessions file or set default user, for example, and restart x2goclient). Authentification and "hard" identification could be implemented using OpenPGP cards, ''scdaemon'' and a script based on ''/usr/share/doc/scdaemon/examples/scd-event''. For Status ''NOCARD'', suspend the session (kill x2goclient or send a signal that means "suspend", if available, or maybe sighup nxproxy), for status ''USABLE'', run ''gpg --card-status 2>&1 | awk '$1=="Serial" && $2=="number" {print $4}''' to determine the card's serial number, then act based on that (pull new sessions file or set default user, for example, and restart x2goclient).
  
-FIXME <del>Automount script expansion is in the works. Will fully support VFAT, NTFS, hfs, hpfs, will offer read-only support for ext* via fuseext2 (that way, file ownership/permissions are ignored).</del> fixed. +FIXME Automount script currently expects a LUKS password in ''/etc/keys/keystick.key'' when it believes it has found an encrypted partition on USB media. This is a problem in general, as it should be trivial to sniff out this password using a rogue client. Such a password file would have to be saved as ''./patch/includes.chroot/etc/keys/keystick.key'' (with the proper restrictive permissions) before starting the build. Adding a boot parameter instead of hardcoding it would allow for dynamic password files (by specifying an URI that points to a CGI script, for example - you could output a different password depending on the source IP range, thus locking media to a particular department, if your departments have different IP ranges), but on the other hand, would make it even easier to sniff out the password. It would only really make sense for Netboot installations, and also not for a MiniDesktop in any way, because you have to block the user from accessing the TCE's local environment/files. And you also have to make sure that people cannot boot rogue clients.  This means a DHCP setup that is locked to known MAC addresses, and physically blocking access to the ThinClient and its network wiring - because the MAC is displayed during boot, and thus trivial to clone.
- +
-FIXME <del>Maybe we should add symlinks to the mount points created by the automounter: Currently, we create ''/media/vendor_model_name/sdxn'' as a mount point. The idea is to allow the user to find their portable device using the vendor/model name description. However, this is unusable for scripting, as the ''//x//'' in ''sdxn'' may change any time. We should replace ''//sdx//'' with ''//partition//'' (or have corresponding symlinks created), but what should we do for //superfloppies// that only have ''sdx'' with no partition number? We could mount them as ''/media/vendor_model_name/partition/'' or directly at ''/media/vendor_model_name/''. Also, symlinks using labels and uuids, similar to ''/dev/by-*'' would be handy for scripting. Another problem: when replacing ''sdx'', what will happen when a user inserts two media with the same vendor/model name at the same time? Blindly replacing the string would make one of them inaccessible due to overwriting the symlink(s). We'd have to start checking active mounts and enumerate them like ''/media/vendor_model_name/1/partitionn'' or ''/media/vendor_model_name-1/partitionn''</del> Fixed. When a label is detected, a symlink is now created under ''/media/vendor_model_name/label'' that points to ''/media/vendor_model_name/partitionn''+
- +
-FIXME Automount script currently expects a LUKS password in ''/etc/keys/keystick.key'' when it believes it has found an encrypted partition on USB media. This is a problem in general, as it should be trivial to sniff out this password using a rogue client. If we want to support this feature, though, we should add code to the build script that lets the user place a password file in the image, and sets proper restrictive permissions. Adding a boot parameter instead of hardcoding it would allow for dynamic password files, but on the other hand, would make it even easier to sniff out the password.+
  
 FIXME ''x2gocdmanager'' is currently not part of the image, but should become part of it. While optical media are on their way out, they still exist and thus we should support them. However, the script is hardcoded for X2Go-TCE-NFS and needs to be adapted to work with both TCEs. FIXME ''x2gocdmanager'' is currently not part of the image, but should become part of it. While optical media are on their way out, they still exist and thus we should support them. However, the script is hardcoded for X2Go-TCE-NFS and needs to be adapted to work with both TCEs.
Line 1173: Line 1329:
 FIXME Even though we set the hostname to ''localhost'' using the corresponding boot parameter, as recommended by Debian, changing the name via DHCP does not work for all image flavours. One way to fix this might be http://blog.schlomo.schapiro.org/2013/11/setting-hostname-from-dhcp-in-debian.html FIXME Even though we set the hostname to ''localhost'' using the corresponding boot parameter, as recommended by Debian, changing the name via DHCP does not work for all image flavours. One way to fix this might be http://blog.schlomo.schapiro.org/2013/11/setting-hostname-from-dhcp-in-debian.html
  
-FIXME At least when building a stretch TCE on a jessie system, you need to add kernel parameters ''net.ifnames=0 biosdevname=0'' to the image's kernel parameters, else you will receive error messages about the hostname script being unable to find eth0. This might not be necessary when building a stretch TCE on stretch. For a jessie TCE on jessie, it is not required.+FIXME When building a stretch TCE you need to add kernel parameters ''net.ifnames=0 biosdevname=0'' to the image's kernel parameters, else you will receive error messages about the hostname script being unable to find eth0. For a jessie TCE, it is not required. This could be fixed for iso-hybrid and netboot in the buildscript, but it will only work if people are using the image 1:1 - as soon as they start using syslinux or grub manually (as actually recommended by us), they need to add these parameters themselves.
  
-FIXME <del>There might be a race condition between the scripts handling the sshd keyfile and the ssh private key file copy task (/config ...), causing one to umount the fixed disk before the other is done reading/copying. What's weird is that there already is code that is supposed to keep this from happening, but it doesn't.</del> fixed in github reposoon in x2go repo+FIXME ''bg='', ''branding='', ''broker-url='', ''ldap='', ''ldap1='', ''ldap2='', ''session='', ''throttle='', are currently unsupported in MiniDesktop-Mode. This could be changed, given enough tuits. Probably the easiest way would be to have ''/lib/live/config/2900-x2go-thinclientconfig'' exist in the MiniDesktop branches as wellmake it aware of which environment it is running in (TCE/TCE-MMD), and have it patch the appropriate files.
  
-FIXME <del>Setting the time via NTP will fail if the TC can't establish a connection to an NTP server via the internet. It would make sense to allow specifying an internal NTP server via a boot parameter.</del> fixed in github repo, soon in x2go repo+FIXME <del>''2200-xserver-xorg-getxorgconf''</del> all scripts accepting URLs in boot parameters should be taught to understand ''file:<nowiki>///</nowiki>'' URLs. Such files can be included in the image by placing them in the ''./patch/includes.chroot/'' directory (in a suitable subdirectory) and referencing them from there.
  
-FIXME <del>''copysecring'' currently does not work in MiniDesktop-Mode, as it copies the keys to the wrong user's homedir.</del> fixed in github reposoon in x2go repo+FIXME it would be cool if most of the TCE-specific boot parameters could be placed into a file that in turn can be specified as a boot parameter, to reduce clutter and boot parameter length. This could be aCGI script, even, thus making it possible to distribute different configs depending on the source IP of the ThinClient, rather than the MAC AddressSaid file would then have to be sourced by the scripts, after they have extracted everything from /proc/cmdline. This will make adding the feature easierby simply deciding that parameters from this file take precendence over boot parameters. One might argue that boot parameters should take precedence over the config file, but this sounds way more complicated to implement.
  
-FIXME ''audioout='', ''blank='', ''blankdpmsfix'', ''broker-url='', ''ldap='', ''ldap1='', ''ldap2='', ''nodpms'', ''session='', ''throttle='', ''xinerama='', are currently unsupported in MiniDesktop-Mode. This could be changedgiven enough tuitsProbably the easiest way would be to outsource as many of them as possible into scripts under ''/etc/X11/Xsession.d/'' (currently, they reside in ''/lib/live/config/2900-x2go-thinclientconfig'' which doesn't exist in the MiniDesktop branches and from there, they get written to ''~/.xsession''+FIXME A smaller image size can be achieved by removing the following packages from the squashfs: ''libxapian30 libpcsclite1 libdbus-glib-1-2 libfuse2 libpipeline1 libusb-1.0-0 libxv1 xnest xserver-xephyr rdesktop freerdp-x11 traceroute screen net-tools less ntfs-3g fuse locales cifs-utils xterm libgssglue1 libntfs-3g871 libtalloc2 libtcl8.6 libtk8.6 libutempter0 libvncclient1 libvncserver1 libwbclient0 libxcb-xf86dri0 libxcb-xv0 samba-common tcl tcl8.6 tk tk8.6 xbitmaps nfs-common rpcbind atmel-firmware bluez-firmware dahdi-firmware-nonfree hdmi2usb-fx2-firmware iso-codes ixo-usb-jtag libc-l10n libnfsidmap2 libtirpc1 firmware* x11vnc* libfreerdp* libwinpr* libapparmor1 systemd apt-utils libapt-inst2.0 acpi-support-base* acpid* acpi-support* pm-utils* powermgmt-base* gnupg gnupg-agent whiptail vim* vim-common* vim-tiny* xxd* xinetd libcroco3* libcurl3* libexif12* libgdk-pixbuf2.0-0* libgdk-pixbuf2.0-common* libgif7* libid3tag0* libimlib2* libnghttp2-14* libobrender32v5* libobt2v5* libpango-1.0-0* libpangocairo-1.0-0* libpangoft2-1.0-0* libpangoxft-1.0-0* librsvg2-2* librtmp1* libssh2-1* libstartup-notification0* libxft2* libxss1* vim-runtime* xprintidle feh xdotool openbox rsync   xserver-xorg-input-wacom* xserver-xorg-video-all* xserver-xorg-video-amdgpu* xserver-xorg-video-ati* xserver-xorg-video-nouveau* xserver-xorg-video-qxl* xserver-xorg-video-radeon* xserver-xorg-video-vmware* libdrm-amdgpu1* libdrm-nouveau2* libdrm-radeon1* libllvm3.9* libsensors4* libxatracker2*''  
 + check if this could be turned into a build parameter. Note that this makes only sense for a netboot image that uses X2Go sessions onlyand no NTFS media (neither fixed disk nor USB)Also, this causes an X startup failure during boot that needs to be worked around (by touching /home/user/.xsession). 
 +Here's a script to do all of this automatically (needs to be run as root in the builddir: 
 +<file - stripimage.sh> 
 +#!/bin/bash -e 
 +if [ $UID -ne 0 ] ; then 
 + echo "Must be root." 
 + exit 1 
 +fi 
 +unsquashfs x2go-tce-filesystem.squashfs 
 +mount --bind /proc squashfs-root/proc 
 +chroot squashfs-root apt purge -y acpi-support-base acpid acpi-support pm-utils powermgmt-base gnupg gnupg-agent whiptail vim vim-common vim-tiny xxd xinetd \ 
 +                                  libcroco3 libcurl3 libexif12 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif7 libid3tag0 libimlib2 libnghttp2-14 \ 
 +                                  libobrender32v5 libobt2v5 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 librsvg2-2 librtmp1 \ 
 +                                  libssh2-1 libstartup-notification0 libxft2 libxss1 vim-runtime rsync xserver-xorg-input-wacom xserver-xorg-video-all \ 
 +                                  xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-nouveau xserver-xorg-video-qxl \ 
 +                                  xserver-xorg-video-radeon xserver-xorg-video-vmware libdrm-amdgpu1 libdrm-nouveau2 libdrm-radeon1 libllvm3.9 libsensors4 \ 
 +                                  libxatracker2 xprintidle feh xdotool openbox libxapian30 libpipeline1 libnpth0 libksba8 libseccomp2 libsqlite3-0 libxdo3 \ 
 +                                  libnewt0.52 libslang2 keyutils libassuan0 libdatrie1 libevent-2.0-5 libthai-data libthai0 \ 
 +                                  pinentry-curses trickle libxapian30 libpcsclite1 libdbus-glib-1-2 libfuse2 libpipeline1 libusb-1.0-0 libxv1 xnest \ 
 +                                  xserver-xephyr rdesktop freerdp-x11 traceroute screen net-tools less ntfs-3g fuse locales cifs-utils xterm libgssglue1 \ 
 +                                  libntfs-3g871 libtalloc2 libtcl8.6 libtk8.6 libutempter0 libvncclient1 libvncserver1 libwbclient0 libxcb-xf86dri0 \ 
 +                                  libxcb-xv0 samba-common tcl tcl8.6 tk tk8.6 xbitmaps nfs-common rpcbind atmel-firmware bluez-firmware \ 
 +                                  dahdi-firmware-nonfree hdmi2usb-fx2-firmware iso-codes ixo-usb-jtag libc-l10n libnfsidmap2 libtirpc1 x11vnc x11vnc-data \ 
 +                                  libapparmor1 systemd apt-utils libapt-inst2.0 libfreerdp-cache1.1 libfreerdp-client1.1 libfreerdp-codec1.1 \ 
 +                                  libfreerdp-common1.1.0 libfreerdp-core1.1 libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 \ 
 +                                  libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 \ 
 +                                  libwinpr-environment0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 libwinpr-input0.1 libwinpr-interlocked0.1 \ 
 +                                  libwinpr-library0.1 libwinpr-path0.1 libwinpr-pool0.1 libwinpr-registry0.1 libwinpr-rpc0.1 libwinpr-sspi0.1 \ 
 +                                  libwinpr-synch0.1 libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-utils0.1 firmware-amd-graphics firmware-atheros \ 
 +                                  firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-crystalhd firmware-intel-sound \ 
 +                                  firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-free \ 
 +                                  firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-realtek \ 
 +                                  firmware-samsung firmware-siano firmware-ti-connectivity firmware-zd1211 
 +chroot squashfs-root dpkg -P apt tasksel tasksel-data 
 +rm squashfs-root/etc/X11/Xsession.d/60x11-openbox-start squashfs-root/etc/X11/Xsession.d/60x11-spawn-configure-slideshow-screensaver 
 +(cd squashfs-root/usr/bin/ ; ln -sf ../../bin/false xsetwacom) 
 +mkdir -p squashfs-root/home/user 
 +touch squashfs-root/home/user/.xsession 
 +umount squashfs-root/proc 
 +if ! grep '^eval $THROTTLINGCOMMANDsquashfs-root/etc/X11/Xsession.d/61x11-start-x2goclient | grep -q -- --thinclient ; then 
 +        sed -i -e 's#eval \$THROTTLINGCOMMAND x2goclient#eval \$THROTTLINGCOMMAND x2goclient --thinclient#g
 +            squashfs-root/etc/X11/Xsession.d/61x11-start-x2goclient 
 +fi 
 +if [ -f binary/live/filesystem.squashfs ] ; then 
 +        mv binary/live/filesystem.squashfs binary/live/filesystem.squashfs.old 
 +fi 
 +mkdir -p binary/live 
 +mksquashfs squashfs-root binary/live/filesystem.squashfs -comp xz -Xbcj x86 -b 1024K -Xdict-size 1024K -noappend 
 +rm -rf squashfs-root 
 +ln -f binary/live/filesystem.squashfs x2go-tce-filesystem-stripped.squashfs 
 +(cd binary; echo live$'\n'live/filesystem.squashfs |cpio -o -H newc | gzip --fast) >./tce-filesystem-stripped.cpio.gz 
 +cat ./x2go-tce-initrd.img ./tce-filesystem-stripped.cpio.gz >./x2go-tce-initrd-with-fs-stripped.img 
 +rm ./tce-filesystem-stripped.cpio.gz 
 +</file>
  
-FIXME ''nomagicpixel='' is currently unsupported in MiniDesktop-Mode and probably will be unsupported there foreveras it doesn'make sense for MiniDesktop-Mode.+FIXME for MATE-MiniDesktop, it might make sense to teach the image how to do LDAP auth (preferably with LDAPS or LDAP+TLS) and use lightdm without the auto-login. That way, a local screensaver //with// locking functionality (prompting for the actual user's LDAP password) should be possible and LDAP credential passthrough to X2GoClient should work, too (though that might require kerberos in addition to LDAP,we'll see).
  
-FIXME ''bg='' and ''branding='' are currently unsupported in MiniDesktop-Mode. Adding support for these doesn't need many tuits. A third option for the desktop background could be added as well - possibly for regular TCE mode as well, overriding our default blue.+FIXME Scripts triggered by if-up should check if a new download is really necessary.
  
-FIXME <del>''homepageurl='' (only available in MiniDesktop-Modeis currently undocumented. Supports multiple URLs separated with pipes.</del>+===== List of closed ToDos/FIXMEs for this page =====  
 +  * Feature request: In TCE (not MMD), use <code> 
 +while ! (grep "^/dev/" /etc/mtab | grep -q rw ; do # rw-mounted physical devices detected 
 + echo s >/proc/sysrq-trigger # sync all 
 + echo u >/proc/sysrq-trigger # remount all (physdevs) ro 
 +done 
 +echo o >/proc/sysrq-trigger # force fast shutdown/poweroff 
 +</codefor faster poweroff when boot parameter ''fastpo'' is set
  
 +  * ''audioout='', ''blank='', ''*blankdpmsfix'', ''nodpms'', ''xinerama='', are currently unsupported in MiniDesktop-Mode, but this is being worked on, by outsourcing them into scripts under ''/etc/X11/Xsession.d/'' (currently, they reside in ''/lib/live/config/2900-x2go-thinclientconfig'' - which doesn't exist in the MiniDesktop branches - and from there, they get written to ''~/.xsession'' - fixed in github repo, soon in x2go repo
 +  * It would be nice to have a boot parameter ''xroot=[0xaabbcc|URI1[|URI2|...]]'' for the desktop background image/color, and a boot parameter ''xrootmode=center|fill|scale|tile'' to determine how the image(s) should be positioned (if the parameter has been set, but something is wrong, it should default to the "grey mesh" background) - fixed in github repo, soon in x2go repo
 +  * It would also be nice to have boot parameters ''xsaverimages=[URI1[|URI2|...]]'', ''xsaveridletime=n'', ''xsaverimgtime=n'', for a local, non-locking slideshow screensaver (if no images are specified/downloaded by the time it activates, it should just blank the screen). That way, one could display a slideshow without having to push the images across the network every time  - fixed in github repo, soon in x2go repo
 +  * Boot parameters ''blankdpmsfix'' and ''earlyblankdpmsfix'' still leave the screen blank for too long, when used in netboot mode (especially over slow links). Two ways to solve this are to either use local storage, or to use the initrd with the squashfs merged into it.  A third, new option would be a boot parameter ''initrdblankdpmsfix'', where the un-blanking code of ''earlyblankdpmsfix'' is applied in the initrd already - fixed in github repo, soon in x2go repo
 +  * There might be a race condition between the scripts handling the sshd keyfile and the ssh private key file copy task (/config ...), causing one to umount the fixed disk before the other is done reading/copying. What's weird is that there already is code that is supposed to keep this from happening, but it doesn't. - fixed in github repo, soon in x2go repo
 +  * Setting the time via NTP will fail if the TC can't establish a connection to an NTP server via the internet. It would make sense to allow specifying an internal NTP server via a boot parameter. - fixed in github repo, soon in x2go repo
 +  * ''copysecring'' currently does not work in MiniDesktop-Mode, as it copies the keys to the wrong user's homedir. - fixed in github repo, soon in x2go repo
 +  * copying ssh private keys seems to fail in MiniDesktop-Mode - possibly because of the priming/pruning/cleanup action performed on the homedirectory by the minidesktop init scripts? -  should already be fixed in github repo, soon in x2go repo 
 +  * Automount script expansion is in the works. Will fully support VFAT, NTFS, hfs, hpfs, will offer read-only support for ext* via fuseext2 (that way, file ownership/permissions are ignored). - fixed.
 +  * ''homepageurl='' (only available in MiniDesktop-Mode) is currently undocumented. Supports multiple URLs separated with pipes. - fixed
 +  * Maybe we should add symlinks to the mount points created by the automounter: Currently, we create ''/media/vendor_model_name/sdxn'' as a mount point. The idea is to allow the user to find their portable device using the vendor/model name description. However, this is unusable for scripting, as the ''//x//'' in ''sdxn'' may change any time. We should replace ''//sdx//'' with ''//partition//'' (or have corresponding symlinks created), but what should we do for //superfloppies// that only have ''sdx'' with no partition number? We could mount them as ''/media/vendor_model_name/partition/'' or directly at ''/media/vendor_model_name/''. Also, symlinks using labels and uuids, similar to ''/dev/by-*'' would be handy for scripting. Another problem: when replacing ''sdx'', what will happen when a user inserts two media with the same vendor/model name at the same time? Blindly replacing the string would make one of them inaccessible due to overwriting the symlink(s). We'd have to start checking active mounts and enumerate them like ''/media/vendor_model_name/1/partitionn'' or ''/media/vendor_model_name-1/partitionn''. - fixed. When a label is detected, a symlink is now created under ''/media/vendor_model_name/label'' that points to ''/media/vendor_model_name/partitionn''.
 +  * ''nomagicpixel='' is unsupported in MiniDesktop-Mode and will be unsupported there forever, as it doesn't make sense for MiniDesktop-Mode (there is a task bar available, so a session that has been minimized accidentally can be re-selected by the users themselves). - unfixable.
 +  * volume control applet for MiniDesktop mode has been added  - fixed in github repo, soon in x2go repo (to save/restore volume control settings, using the "persistence" feature of live-build is probably the better way to go)
 <note>The live-config "builtin" command ''live-config.nottyautologin'' does not do the same as our ''nouser'' command. ''live-config.nottyautologin'' means "there's a login prompt, but you just need to enter username ''user'' and password ''live'' to login" - this is not what we want.  We need a solution to entirely block user logons. <note>The live-config "builtin" command ''live-config.nottyautologin'' does not do the same as our ''nouser'' command. ''live-config.nottyautologin'' means "there's a login prompt, but you just need to enter username ''user'' and password ''live'' to login" - this is not what we want.  We need a solution to entirely block user logons.
 </note> </note>
  
doc/howto/tce.1543958019.txt.gz · Last modified: 2018/12/04 21:13 by stefanbaur