You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Wednesday, November 12th 2003, 8:16pm

Restricted environment - kiosk mode

Hello all.

I'm trying to configure some machines as browser-only clients - computer boots into a user account and straight to konqueror. The restrictions I need are:
Konqueror will always run - even if it's been quit by the user, it will re-init.
Nothing in the kicker - it should only be available to handle multiple instances of konq - but no k menu or anything else there (well, maybe a clock is OK).
User can't use konq to browse local directories.
User can't download any files (excepting stuff that ends up in /tmp, naturally)
User can't launch any application save gv if it's embedded in konqueror.
User can't change printers.
User can't change any konq settings. Home page will always stay the same, no bookmarks, etc.
The Browse Up button in konq needs to go.

The kde version I'm working with is 3.1 as it appears in SuSE 9.0. I've looked at the README.kiosk, but it looks like whoever wrote that assumes a lot of knowledge on my part that I don't have. Anyone have any pointers? Of course, a nice HOWTO would be great, but I can work off a working config file and adapt it to my needs.

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

2

Wednesday, November 12th 2003, 10:45pm

KDE Kiosk has a mailinglist https://mail.kde.org/mailman/listinfo/kde-kiosk

I am sure you will find any help you need there.

Cheers,
_
Qt/KDE Developer
Debian User

3

Wednesday, November 12th 2003, 10:47pm

Quoted

Original von anda_skoa

KDE Kiosk has a mailinglist https://mail.kde.org/mailman/listinfo/kde-kiosk

I am sure you will find any help you need there.

Cheers,
_


Thanks for your reply. But so far, no joy there, which is why I posted here =]

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

4

Thursday, November 13th 2003, 9:49am

Quoted

Original von gloin

Quoted

Original von anda_skoa

KDE Kiosk has a mailinglist https://mail.kde.org/mailman/listinfo/kde-kiosk

I am sure you will find any help you need there.

Cheers,
_


Thanks for your reply. But so far, no joy there, which is why I posted here =]


Ah, too bad. Even the Kiosk mode maintainer is subscribed there.

Anyway, I'll give it a shot, but it is just pointers, haven't tried anything like that before.

1) Start Konqueror through a shellscript in KDE's Autostart folder.
The script has to contain a loop, e.g a while loop with always true condition, and in this loop you start konqueror with a profile you want.
If konqueror quits, the loop takes another iteration and start konqueror again.

2) I think Kicker's content is configured in kickerrc.
You can create a configuration you like and put it in the global KDE directory for configs (usually KDEPREFIX/share/config).
Then you disable changability of the file by putting [$i] into an extra line at the very beginning of the file, see this
http://www.kde.org/areas/sysadmin/config_file.php#lock_down
for details.

3) I am not sure if this has any bad side effects, but you could try to remove the file.protocol file from KDEPREFIX/share/services

4) no idea here

5) Not sure how this is handled, but perhaps removing the programs of each MIME type in Control Center->KDE components->file associations works.

6) no idea either, might work to have a fixed (see above) configuration file for kprinter

7) that should be doable with locking down konqueror's config file konquerorrc

8) KDEPREFIX/share/apps/konqueror/konqueror.rc describes which actions are present in which order in the menus/toolbars.
Remove the ones you don't need.

Cheers,
_
Qt/KDE Developer
Debian User

5

Thursday, November 13th 2003, 6:08pm

Thanks!

Some of this stuff I'm handling by setting permissions... for example, chmod 644 /home/path/to/kickerrc sets the properties to immutable.

My other question is this: can I create a kdeglobals file in a given user's home dir rather than creating a systemwide file? I'm looking for fine-grained user-level control here - maybe not as important for the instant case, but down the road I will need to create profiles for students who log in versus staff, versus admins, etc.

Looking at the action restrictions, it sure would be nice if there were a way to wildcard them - I'm looking at a hundred lines or so of code to set all the restrictions =[

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

6

Thursday, November 13th 2003, 6:56pm

Re: Thanks!

Quoted

Original von gloin

Some of this stuff I'm handling by setting permissions... for example, chmod 644 /home/path/to/kickerrc sets the properties to immutable.

Might not work for all programs, e.g. they could crash if not able to write their files.
Marking the file as immutable also has the advantage, that new settings in the higher level file are automatically used.

Quoted


My other question is this: can I create a kdeglobals file in a given user's home dir rather than creating a systemwide file?

Hmm, good question.
Try to create .kdeglobals in the user's home dir or kdeglobals in .kde/share/config


Quoted


I'm looking for fine-grained user-level control here - maybe not as important for the instant case, but down the road I will need to create profiles for students who log in versus staff, versus admins, etc.

I think you can use KDE Dir trees for that
http://www.kde.org/areas/sysadmin/fsh.php#dir_location

Quoted


Looking at the action restrictions, it sure would be nice if there were a way to wildcard them - I'm looking at a hundred lines or so of code to set all the restrictions =[


Short of creating your own version of konqueror.rc including only the actions you want, I think it is only possible to remove the ones you don't want from the original file.

Cheers,
_
Qt/KDE Developer
Debian User