[prev in list] [next in list] [prev in thread] [next in thread] 

List:       klik-devel
Subject:    [klik-devel] How to sandbox easily your klik2 application
From:       Lionel Tricon <lionel.tricon () free ! fr>
Date:       2007-06-29 21:59:32
Message-ID: 200706292359.32466.lionel.tricon () free ! fr
[Download RAW message or body]

Hi all,

Some news about klikutils. I have recently changed the way how klikutils is 
called to offer an easy way to the end-user to sandbox an application into a 
private directory. It's just for testing purpose of course.

If you create a <what you want>.jail directory on the Desktop (or even 
several), klikutils will ask you on startup if you want to jail your 
application into this one. With that, everything will be put into this 
specific directory and nothing will be modified from your own data.

A bad news is that it seems, for the moment, impossible to put data into an 
iso file mounted in loopback. Mountlo is not mature enough for the moment i 
fear. So the solution of a directory is a workaround.

An another change is that you can put the klikutils directory into your own 
private directory.

For example, on Ubuntu/Kubuntu :

# cd ~
# tar xzvf ~/Desktop/klikutils-static-20070629_2.tgz
# sudo chown root:root .klikutils/bin/fusermount
# sudo chmod 4755 .klikutils/bin/fusermount

If you are under KDE, you can update the menu files by 
running .klikutils/install_menu_kde.sh to avoid to have to call an 
application from a command line.

You can download the last version on http://lionel.tricon.free.fr/KLIK/ as 
usual. Don't hesitate to test it ; it works well on Kubuntu 7.04 and suse 
10.1

Have a good week-end,
Lionel
_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel
[prev in list] [next in list] [prev in thread] [next in thread]