From kde-kiosk  Mon Oct 15 22:35:40 2001
From: Waldo Bastian <bastian () kde ! org>
Date: Mon, 15 Oct 2001 22:35:40 +0000
To: kde-kiosk
Subject: [Kde-kiosk] Re: kdelibs/kdecore
X-MARC-Message: https://marc.info/?l=kde-kiosk&m=100318550406666

> Wouldn't it be much more generic and flexible to have something in the line
> of
>
> bool authorize( QString object, QString method, QStringList arguments );
>
> A bit like DCOP, but simpler. Then at least it is easier to separate big
> groups of actions behind a virtual 'object'.
>
> After all, we might want to disable standard actions like 'save' or
> 'settings', shell operations like 'openURL' or 'execute', and maybe even
> only filter actions like openURL on a per-mimetype basis.
>
> I've worked a couple of years in a computer shope wher we had computers
> with printers and scanners attached for demonstration purposes. However, we
> sometimes got really insane by people trying to execute all kinds of
> applications and stuff. Of course the win9x boxes that we used back then
> didn't have any protection at the file system level, but the policy editor
> was a useful tool.

It's just a first draft and I am trying to get feedback on it to see in which 
direction things should move. Would you mind subscribing to kde-kiosk@kde.org 
and talking a bit about the things you can do with this policy editor?

Cheers,
Waldo

> PS: And another feature that will make sysadmins love you is to make
> changing global settings much more accessible by running an app in 'setup
> mode', where all settings changes are saved by KConfig to a common file
> instead of the user's personal file in $KDEHOME. Whether this setup mode
> has a GUI (would be nice) or just a command-line switch (would already be
> sufficient for now) is not that important.

Sounds like a good idea. 


_______________________________________________
Kde-kiosk mailing list
Kde-kiosk@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-kiosk