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

List:       kde-devel
Subject:    Re: re-enableding panel configuration
From:       Alan Ezust <alan.ezust () gmail ! com>
Date:       2005-09-28 3:26:43
Message-ID: f377591c050927202613684b3c () mail ! gmail ! com
[Download RAW message or body]

Thanks for the informative and non-snarky reply, Thiago. My, my, the
developers of kiosk are mighty sensitive - I had no idea it was even
called kiosk, or that it was considered a "security" feature (I
thought it could just be enabled by a file copied into my ~/.kde
directory from /etc/skel or something).

Realizing now it is a security feature, I can see the folly in my ways...


On 9/26/05, Thiago Macieira <thiago@kde.org> wrote:
> Alan Ezust wrote:
> >At a lab at school, they installed a version of redhat with a crippled
> > KDE. Users are not permitted to configure the clock, or the panel,
> > which means they can not add items to the panel either.
> >
> >What is the mechanism by which this is achieved? Is there a way a
> >savvy user can get around it?
>
> It's Kiosk, the KDE lockdown framework. It's designed to prevent people
> from doing what you're trying to do.
>
> And it's also designed so that savvy users don't get around it, if
> properly configured. If you find out a way of getting around it, let us
> know so that we can fix the bug.
>
> (You're asking the developers because you want to help them, right?)
>
> --
>   Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
>     PGP/GPG: 0x6EF45358; fingerprint:
>     E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
> 1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde
> wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
>
>
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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