[Kde-kiosk] Re: kde-kiosk Digest, Vol 15, Issue 15

[Segedunum]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 27 Jun 2004 16:02:02, Ask Holme wrote:
> Well my users can also use their browser or document editor to make a
> script that copies /usr/kde/3.2 to their own homedir removes the
> lockdown symbols and then runs kde with a different KDEDIR environment
> variable.....

That's not the same thing, but it proves my point somewhat. You need to use 
the security tools at your disposal, as well as Kiosk. Anyway, with adequate 
restrictions I would hope this wouldn't be possible.

> And if the programs in question cannot handle the permissions an admin want
> (in the question is was clearly stated that making root own the mails would
> cause kmail til crash)  

It wasn't clearly stated. Unfortunately, we don't know whether these are the 
permissions he really wanted, and we do not know what caused KMail to crash. 
It could be that he set the files to be readable only by root, in which case 
that really would be a problem. We don't know this unless he responds with 
how he tried to do this and some further background information.

> 1. is to code hack kmail so it won't crash.

How? We don't know why it crashed.

> 2. is to go for the 2. best solution and lock the obvius ways - offcourse
> the 2. way won't be bullet proof, but it will  lock off most people. 

Option 3 would be to get more information on what he has currently tried, look 
at the options and work from there. Locking off the most 'obvious' ways, and 
'most' people, is not really an option when you are looking at a multiple 
user environment. If something is a risk, then you need to lock it off. If 
there is something you haven't foreseen, then fair enough. Keeping out 'most' 
users is how most Windows environments are run - and it fails spectacularly.

> anyway the pop3 cronjob solution is allso a nice alternative.

Yer, but it needs to be managed centrally to be effective and manageable.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA4ck453OaWc7M8G0RAslTAJ9ZnKDC+Ngk9ojApShHTYpl2aq+CQCgkgE+
s7TM/E8kPL9PN4/+irCUPy8=
=tDWY
-----END PGP SIGNATURE-----