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

List:       kde
Subject:    [kde] Problem with startkde ~/.kde/env/*.sh and environment
From:       Stephen Dowdy <sdowdy () ucar ! edu>
Date:       2007-05-31 21:48:47
Message-ID: 465F42BF.5080009 () ucar ! edu
[Download RAW message or body]

I have a script that exists as ~/.kde/env/add_dns.sh

This script contains:

export LOCALDOMAIN="foo.bar blah.blah boo.hoo"

I can see from adding diagnostic statements into /usr/bin/startkde that this
script is indeed sourced and that, after sourcing, the environment contains
"LOCALDOMAIN".

I see that this variable is no longer in the environment when attempting
to reference it from the mini-cli.  Other variables i setup in add_dns.sh or
other ~/.kde/env/*.sh scripts *DO* exist.

I suspect that since this worked in Debian Sarge (kde 3.3.2), but no longer
does in Debian Etch (KDE 3.5.5) that someone got the bright idea to sanitize
the environment for potential security issues.  (clearly LOCALDOMAIN *could*
be used to compromise an end-user's environment).

However, i don't want to be "protected from myself", but i can NOT figure out
where this sanitizing process occurs and more importantly, how to DISABLE it.
(or effectively work around it)

Any clues greatly appreciated!

--stephen
-- 
Stephen Dowdy  -  Systems Administrator  -  NCAR/RAL
303.497.2869   -  sdowdy@ucar.edu        -  http://www.ral.ucar.edu/~sdowdy/

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
[prev in list] [next in list] [prev in thread] [next in thread]