I've been working on my BS thesis with the name "Parental mode in KDE". The name can be a bit misleading, because I was mainly working on some kdelibs internals (integration of KAuth into Kiosk) and the Kiosk Admin Tool application.
The first part of the work uncovered some nasty things in PolicyKit and ended with a simple outcome: using KAuth/PolicyKit as a back-end for Kiosk is too problematic and would require rewriting a good part of PolicyKit to make it work at all. For example: unlike Kiosk, PolicyKit doesn't have support for profiles that could be assigned to users and groups, is much slower compared to KConfig/Kiosk, and in the PolicyKit1 incarnation isn't stable enough for heavy use. See freedesktop bugs 29394 and 29069 for some details. Only positive outcome up to now is that Dario Freddi fixed some problems I found in KAuth. I wanted to do it but he was faster ;-)
Nevertheless, working with Kiosk gave me some insight into how it works and that it's in much better state than people believe. So, on to the real stuff.
Kiosk ToolThe original KioskTool for KDE 3 is probably rather well-known compared to the newer KDE 4 port that currently resides in extragear. While the older version is much more complete, even in the first few minutes of use, I encountered segfaults.
A lot of work has been done already in the unfinished KDE 4 port and what it really needed to become usable again was just a bit of polishing, refactoring and bug-hunting. So, that's what I did :) Screenshots should help.
First a few from the KDE 4 port before I started working on it.
|This is pretty much what greets you when you first start the application.|
A list of profiles... and not very informative.
|Changing some settings of a profile.|
The dialog doesn't fit on smaller netbook screens.
|Assigning user and group profiles can be rather unfriendly.|
Also, there was no way to set up the default profile structure when you don't have it already on your system. This wasn't so trivial and I resolved the problem after redoing the GUI. It will bug you about it when you run the program for the first time (and won't let you further if you don't let it create the files).
I mostly worked on the profile management and assignment part and the actual profile editor is mostly untouched.
|This is how the first screen looks now. It is obvious which profiles|
are assigned to users and their groups and which are effective.
Changes can be saved or discarded.
|Group profiles got the same treatment. It is now possible to change the order in which group|
profiles are applied.
|The profile management part now shows all the properties.|
|Assigning a profile uses the same profile view, so it's easier to pick the right one.|
|The dialog for editing profile properties now fits on the screen.|
It really needs the same model-view treatment as the management part though.
Here's the updated TODO list with things I'd like to do next:
- Fix the stuff that resides in deprecated/. This has been used for translations in the past. A new 'extractxml' that can handle the new .kiosk files is required.
But then: how to make it work with .kiosk files provided by other app developers? Maybe the script would have to be globally accessible.
- Properly separate GUI from data for the profile properties dialog.
- Document how the profile editor components work, how profile editing itself works. Apply more model-view goodness.
- The KioskSync/KioskRun classes are crufty and mostly undocumented. Suspected hidden bugs...
- Remove the PolicyKit stuff (the PKLA convertor KAction).
- Make sure all parts of kiosktool work on small screens (netbooks, etc.)
- Add editor for URL (file) restrictions
- Make it possible to select targeted KDE version?
Plenty of things to keep me busy ;-)
Kiosk in general
Kiosk in KDE 4 mostly works. It is possible to create, assign and manage Kiosk profiles that contain configuration files. That means pretty much every setting can still be locked down.
The real problems are in the action and resource restriction area, where for example restricting the desktop wallpaper resources won't have much of an effect on the dialog used for selecting them. While none of the wallpapers from the user's home directory will show up, it can be easily circumvented by simply using the Open button to pick a file manually. Other examples can be found easily.
With the Kiosk Admin Tool on the way towards greatness again, the only real problem now is that Kiosk isn't used by developers. It's quite easy: determine what could be locked down and how, pick a good name for your actions, describe them in a .kiosk file and make it install along with your application. Or maybe wait a bit for the Kiosk Admin Tool to get more polished as some of the details there might need a bit of tweaking.
Comments are welcome :)