Elektra backend for KDE

[Waldo Bastian]

On Tuesday 21 February 2006 12:11, Aaron J. Seigo wrote:
> On Tuesday 21 February 2006 10:59, Zack Rusin wrote:
> > I think we had a discussion before about relaying on environment
> > variables too much in the past ;)
>
> yes, for situations where third parties need to extend them at application
> installation time (e.g. XDG_*_DIRS). this is a different situation.
>
> > Do we consider the following scenario a problem: Kiosk settings are
> > being propagated from the backend specified in the environment
> > variable, user sets the variable to something that doesn't exists
> > (non-existing ldap backend, non-existing directory, whatever) and gets
> > control over the full installation. Is that an issue?
>
> once they are set for the X session, they can't adjust them. they could get
> to a terminal and change them for applications run from that command line,
> but one can also block access to the command line. it's pretty safe in that
> regard.
>
> a global config file for this would be even more safe, and i did consider
> it, but that would result in more hits to disk (== slower), something i'm
> hoping to avoid as much as possible here.

Currently /etc/kderc is read and contains additional paths and KIOSK info. It 
wouldn't be a stretch to include this information there as well.

Cheers,
Waldo
-- 
Linux Client Architect - Channel Platform Solutions Group - Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060224/caea96fb/attachment.sig>