From: Bill Davidsen <davidsen@tmr.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: The price of SELinux (CPU)
Date: Wed, 05 Oct 2005 15:40:04 -0400 [thread overview]
Message-ID: <43442C14.2040206@tmr.com> (raw)
In-Reply-To: <200510041943.j94Jhj4C007314@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 04 Oct 2005 14:29:05 EDT, John Richard Moser said:
>
>
>>Aside from this, viruses and spyware and worms can now run rampant and
>>do what they want to his system, and other users' idiotic actions on a
>>multi-user system affect him. This is more user friendly? No, I think
>>it's going in the opposite direction. . . .
>
>
> Virus writers are users too, you know. :)
>
> And the other users are users as well - what if the other user's "idiotic
> action" is to nuke your 500Mbyte archive of alt.binaries.pictures.llama.sex
> that's taking up the disk space that is keeping him from running the payroll
> software? In your world, rather than him being able to fix the problem, he has
> to go find a sysadmin with the root password to fix it, causing delays and
> being less friendly....
>
> You seem to be intentionally trying to miss the basic point, which is that
> any additional security ends up trading off against other things.
>
> Non-execute stack is a Good Thing security-wise - but it breaks some code,
> forcing upgrades and/or having to track down binaries and flag them as
> "don't enforce NX stack". And then those binaries are still vulnerable....
>
> SELinux is, in general, also a Good Thing. However, the fact that the policy
> restricts what stuff can happen in the security context associated with
> mail delivery (after all, you *don't* want arbitrary binaries running then, right?)
> did some serious damage to the way I use procmail, which in some cases ended
> up running other binaries. OK, so my .procmailrc *is* a 600-line monster that
> does a lot of odd stuff - the point was that I had to add even *more* contortions
> to the way it works, which is even less user-friendly....
>
>
Doesn't everyone have executables in their .procmailrc? Mine starts with
a filter which may add one line to the mail header, quantifying exactly
how badly it sucks. That's then used to take preemptive action against
spam and other stuff I don't wnat or need to see.
That's a lot to give up.
prev parent reply other threads:[~2005-10-05 19:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 4:28 The price of SELinux (CPU) John Richard Moser
2005-10-04 4:38 ` Dan C Marinescu
2005-10-04 4:59 ` John Richard Moser
2005-10-04 5:06 ` Dan C Marinescu
2005-10-04 6:20 ` John Richard Moser
2005-10-04 6:39 ` Dan C Marinescu
2005-10-04 6:43 ` Dan C Marinescu
2005-10-04 6:51 ` Dan C Marinescu
2005-10-04 13:57 ` serue
2005-10-04 6:57 ` Dan C Marinescu
2005-10-04 7:06 ` Dan C Marinescu
2005-10-04 20:36 ` Bill Davidsen
2005-10-04 22:24 ` Dan C Marinescu
2005-10-04 5:03 ` Dan C Marinescu
2005-10-04 14:34 ` James Morris
2005-10-04 15:39 ` Valdis.Kletnieks
2005-10-04 18:29 ` John Richard Moser
2005-10-04 19:43 ` Valdis.Kletnieks
2005-10-04 20:10 ` John Richard Moser
2005-10-04 22:32 ` Valdis.Kletnieks
2005-10-04 23:00 ` Dan C Marinescu
2005-10-05 2:02 ` John Richard Moser
2005-10-05 19:42 ` Bill Davidsen
2005-10-05 19:40 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43442C14.2040206@tmr.com \
--to=davidsen@tmr.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox