From kde-devel Tue Aug 31 15:14:57 2004 From: Luke Kenneth Casson Leighton Date: Tue, 31 Aug 2004 15:14:57 +0000 To: kde-devel Subject: [patch] additions to kdelib's kinit README Message-Id: <20040831151457.GK11456 () lkcl ! net> X-MARC-Message: https://marc.info/?l=kde-devel&m=109396538305764 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--LQksG6bCIzRHxTLp" --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. -- lkcl.net
lkcl@lkcl.net
--LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=f --- 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. + --LQksG6bCIzRHxTLp Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --LQksG6bCIzRHxTLp--