A page in your DokuWiki was added or changed. Here are the details: Date : 2017/12/07 15:28 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:52.9) Gecko/20100101 Goanna/3.4 Firefox/52.9 PaleMoon/27.6.2 IP-Address : 134.3.37.90 Hostname : HSI-KBW-134-3-37-90.hsi14.kabel-badenwuerttemberg.de Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1512660446 New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] marked too much as done, un-marking User : stefanbaur @@ -1060,10 +1060,10 @@ FIXME To be checked: Does the live-config "builtin" command ''live-config.nottyautologin'' do the same as our ''nouser'' command? If yes, ''nouser'' could be removed. Note that ''live-config.nottyautologin'' **might** mean "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. FIXME autodetection for SSH Private Keys might need some more bells and whistles. <del>For USB media, this may require adding an automounter.</del> - * <del>how about a script that patches the sessions file to enable autologin for all sessions when keys have been found?</del> - * <del>2800-x2go-thinclientconfig needs to be changed so it uses the keyfile(s) when in broker mode (''--broker-ssh-key'')</del> + * 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'') * <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> -- This mail was generated by DokuWiki at https://wiki.x2go.org/