A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/02 10:46
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483353699
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [List of open ToDos/FIXMEs for this page]
User : stefanbaur
@@ -589,4 +589,12 @@
* saving to local media means you need a way to determine where to save
them
* saving to a remote server means you need some kind of login
credentials that could be abused
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 It would be cool if there was some kind of autodetection for SSH private keys, on local storage media and/or on USB media.
+ For USB media, this may require adding an automounter.
+ * Stefan once wrote a script 2500-x2go-keychange for this, but it only
handles local storage media, also, it needs to be adapted to the current TCE.
+ * 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would
probably be the proper names
+ * Maybe it would be better to split the process into 2 scripts, one that
fetches the keys from local storage/USB media, and one that patches the
sessions file
+ * 2800-x2go-thinclientconfig would also have to be changed so it uses the
keyfile(s) when in broker mode
+
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-commits
