A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/02 10:37
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=1483353090
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [List of open ToDos/FIXMEs for this page]
User : stefanbaur
@@ -579,5 +579,14 @@
* /usr/share/x2go-tcebuilder/template-scripts (scripts we ship, with a big
fat header that they should not be changed, but copied)
* store the results somewhere under /var/lib/x2go-tcebuilder/ or whatever
the proper place according to FHS and Debian would be
* turning it into a package would mean we could add dependencies as well, so
the manual apt-get install would not be neccessary
* additional scripts could be added that work "automagically" if there's
no PXE/TFTP/HTTP/FTP server yet - maybe in a separate package
x2go-tce-setup-aids.deb which then has dependencies on atftpd and
apache|lighttpd, ...
+
+ FIXME To avoid re-generating SSH Server keys on each ThinClient on every boot, they could be stored
+ * in a file on a HTTP(S)/FTP/RSYNC server
+ * on local storage (/etc/ssh)
+ * a script 1155-openssh-readsshserverkeys would have to inject them before
the server starts
+ * a script 1165-openssh-writesshserverkeys would have to save them to local
media/upload them after initial generation. Tricky parts:
+ * 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
+
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-commits
