Hi Stefan, On Do 03 Mär 2011 00:00:32 CET Stefan Baur wrote:
Actually, that is something I don't worry about, as the users I'm currently dealing with either have no strict security requirements or their configuration file is stored in their home directory, which is not accessible to other users. I won't complain about a key file authentication system being present, though. ;-)/ when the session file was/>/ stored with a password, directly start the login process? / Maybe it is a better idea to work on a more usable solution for key authentication.
the mainstream focus should be generic. And generic in this context means: no clear text storage of passwords, no password command line option if this command line password is afterwards seen in the process list (ps aux).
For PyHoca-GUI+LTSP (I am actually aiming at an LTSP integration of PyHoca-GUI/-cli) I will start experimenting with python-setproctitle soon and see if it is possible to hide a -p <password> command line option in output of ,,ps aux'' (rdesktop does that). If so, I will discuss (re-)adding a --password option to PyHoca-GUI on this list. A --password option was already implemented in PyHoca but I had removed it for the above named security reasons.
However, another approach on the Linux side might be the usage of tools like gnome-keyring or similar.
Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpHdaiqAwxXt.pgp
Description: Digitale PGP-Unterschrift
_______________________________________________ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
