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

List:       kde-devel
Subject:    Re: how do i get rid of kdeinit dominating program names - entirely
From:       Luke Kenneth Casson Leighton <lkcl () lkcl ! net>
Date:       2004-09-01 0:30:52
Message-ID: 20040901003051.GC4375 () lkcl ! net
[Download RAW message or body]

On Tuesday 31 August 2004 18:11, Waldo Bastian wrote:
> > KDE_IS_PRELINKED gets rid of _some_ uses of kdeinit.
> >
> > however it doesn't get rid of kdeinit kip_imap4.
> > it doesn't get rid of kdeinit kio_file.
>
> Defining KDE_FORK_SLAVES may help. (KDE 3.3 and later)

YESSSS  thank you thank you.

okay... can it go further than that? 

can kioslave be switched off too, into a kio_imap4 _program_?
can there be a kio_http _program_ done as well?

etc?

reason: the kio_imap4 _program_ is the only thing that should be
granted access to ports 143 (and 993).

the kio_http _program_ is the only thing that should be granted
access to ports 80 (and 443).

selinux (for policy) cannot be expected to restrict kioslave
to be allowed access to ports 25,80,110,143,443,993,8080, this, that.

and fireflier cannot be expected to do likewise (grant kioslave
access to the same ports).

it's great that kdeinit can be disabled... it looks however like
the problem is moved from kdeinit to kioslave.

l.

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]