StudentControlPanelCompletion

Revision 9 as of 2006-07-05 18:51:06

Clear message

Summary

Roadmap for finishing the basic implementation of student-control-panel

Rationale

To control LTSP connections in a school environment, an application that interacts with the ltsp server and the clients is needed. An initial implementation of this application tailored for the Ubuntu LTSP implementation called student-control-panel was uploaded to dapper, it currently implements basic connection control (it shows users and the ip of the client they are logged in to, enables to cut the connection for one, more or all users and shows the currently running processes of a single user)

More features are needed to provide a full student control application for school environments.

Use cases

Dr. Miller teaches biology in a ltsp equipped class, he has several students he suspects to secretly browse the web while he is not looking, with student-control-panel he is able to monitor the students desktops via vnc to see if his suspicion is true.

Miriam teaches about free software in a class that uses a ltsp setup, she wants do demonstrate several free software apps she wants to start up on all students desktops. She hits ctrl-a to select all students in student-control-panel and clicks on the execute button which brings up a dialog to execute a command on all selected desktop simultaneously.

Anselmo has one student he doesnt want to be able to access the commandline from his desktop, since this specific student is known to write harmful scripts, Anselmo right clicks on the students name in student-control-panel and selects the lock down option there. Pessulus pops up and he checks the "Disable Commandline" checkbox.

Scope

Easy handling of student LTSP connections.

Design and Implementation

Killing processes

  • Add kill option for commands in processlist (basic implementation done (button currently hidden in the UI), needs some trivial code to interconnect the kill button with processlist selection)

Remote desktop access

  • Student Control Panel will use vnc for remote desktop access. A function using vncclient is already implemented in the current code but disabled in the GUI since the client side wasnt clear yet, this spec will fix that.
  • For the client implementation the x11vnc package will have to be installed in the client chroot.
    • The package will get a preseedable debconf option (suggestion: ltsp-client-mode), if this option is set to true, the postinst script installs an initscript which starts x11vnc connected to localhost:0 at boottime of the client and makes it read a custom password from a file thats located in the client chroot.
    • Student Control Panel will generate this password dynamically on every program startup (an md5sum of a unix timestamp should suffice here) and rewrite the password in the file.
  • Since the debian policy does not allow to run apt-get install from a postinst script, we cant just install x11vnc at install time of the student-control-panel package.
    • A "first start popup window" will be added to the GUI, it will have a checkbox "Dont show this window again" and a button "Install remote desktop access".

    • Choosing the latter option will execute a script /usr/share/student-control-panel/install-client-vnc.sh which will run  apt-get install x11vnc  in the client chroot with the above described option preseeded.

Execution of programs in the users session(s)

  • A student-control-panel listener service will be installed in /usr/share/dbus-1/services/ which will listen for messages from student-control-panel and execute the requested applications in the users session. DBUS has the security built in to not accept any messages except from SCP (see http://dbus.freedesktop.org/doc/dbus-specification.html#auth-protocol for tech details). This is a simple and elegant solution.

Lockdown on the fly

  • A context menu will be added to the student list to start pessulus for a user to modify settings on the fly. (Screenshots: http://www.gnome.org/~vuntz/pessulus/screenshots/), that will allow things like disabling commandline access or locking down browser functionallity if epiphany is used by the student.

Plugins

  • The UI will get a plugins menu. The directory /usr/share/student-control-panel/plugins will be read on every program start. Python scripts added to that dir will show up in that menu. student-control-panel will export the userlist of the selected users from the GUI in the variable $SCPUSERS for these scripts, this will make it very easy for people to enhance the program and to contribute the plugins back into a student-control-panel-plugins package.

Outstanding issues

  • Determine the best default options (compression, scaling of the windowsize etc) for x11vnc to be added to the initscript

CategorySpec