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

List:       kde-devel
Subject:    [patch] additions to kdelib's kinit README
From:       Luke Kenneth Casson Leighton <lkcl () lkcl ! net>
Date:       2004-08-31 15:14:57
Message-ID: 20040831151457.GK11456 () lkcl ! net
[Download RAW message or body]

please kindly include these additional comments of the disadvantages
of kdeinit.

also it might be worthwhile mentioning the existence of prelink
as an alternative to why kdeinit was created.

thank you.

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 />



--- kdelibs-3.3.0/kinit/README.orig	2004-08-31 16:08:39.000000000 +0100
+++ kdelibs-3.3.0/kinit/README	2004-08-31 16:12:21.000000000 +0100
@@ -82,3 +82,12 @@
 process name. To workaround this, use "kdekillall", from kdesdk/scripts,
 for applications started via kdeinit.
 
+Under SE/Linux, protection of one program from another is tracked by
+what program runs another (and also who does the running).  If all programs
+are named "kdeinit", no fine-grained protection can be added.
+
+Firewall programs like FireFlier that can do per-program firewall rules
+have to "glom" all rules together for different functions such as Konqueror
+using kdeinit to access ports 80 and 443, and kmail and kontact accessing
+ports 25, 110 and 143.
+


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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