All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Colin Walters <walters@verbum.org>
Cc: Manoj Srivastava <manoj.srivastava@stdc.com>,
	selinux@tycho.nsa.gov, debian-devel@lists.debian.org
Subject: Re: Updated SELinux Release
Date: Fri, 5 Nov 2004 15:57:52 +0000	[thread overview]
Message-ID: <20041105155752.GC5565@lkcl.net> (raw)
In-Reply-To: <1099667461.25416.27.camel@nexus.verbum.private>

On Fri, Nov 05, 2004 at 10:11:01AM -0500, Colin Walters wrote:
> On Fri, 2004-11-05 at 10:28 +0000, Luke Kenneth Casson Leighton wrote:
> > On Thu, Nov 04, 2004 at 11:06:06PM -0500, Colin Walters wrote:
> > > On Thu, 2004-11-04 at 13:15 +0000, Luke Kenneth Casson Leighton wrote:
> > > 
> > > >  default: no.
> > > 
> > > Why not on by default, 
> > 
> >  i would agree with stephen that it should be compiled in,
> >  default options "selinux=no".
> 
> I don't believe Stephen said that.  He said that the performance hit in
> that case is just the LSM hooks.
 
 oh. yes.

> >  that gives people the choice, 
> 
> It doesn't make sense to make security a "choice".  The current Linux
> security model is simply inadequate.

 response 1: *shrug*.  that's their choice - and their problem.

 response 2: you don't have to tell _me_ that - i'm the mad one who is
 actively working on a debian/selinux distro!!! :)

 response 3: _is_ it the job of debian developers to dictate the minimum
 acceptable security level?

 basically what i mean is, in gentoo, it's a no-brainer: you set options
 at the beginning of your build, come back [2 weeks? :) ] later and you
 have a system with PAX stack smashing, lovely kernel, everything
 hunky-dory.

 debian doesn't GIVE users that choice [remember the adamantix
 bun-fight, anyone?] and instead settles for about the lowest possible
 common denominator - no consideration to modern security AT ALL!

> > without affecting performance.
> 
> That's just a bug, and it's being worked on.  

 cool.

> Personally I don't notice any performance problems.
 
 maybe it's just me with my weird setup [very likely], but
 running mozilla under KDE 3.3.0 with selinux 2.6.8.1-selinux1
 on a 256mb system P4 2.4Ghz) is a 10-11 second startup,
 whereas if i set selinux=0 i've seen as fast as a THREE second
 startup time.

 i've put KDE_IS_PRELINKED=1, KDE_FORK_SLAVES=1 into the
 /usr/bin/startkde and i've run prelink, but i have the nvidia drivers
 so the x-windows glx drivers are symlinks, which stops prelink from
 being able to do its job on them.

 also i recompiled kde 3.3.0 .debs with the latest gcc 3.3.

 so i'm not _entirely_ confident that my setup is a good example to
 follow (!)

-- 
--
you don't have to BE MAD   | this space    | my brother wanted to join mensa,
  to work, but   IT HELPS  |   for rent    | for an ego trip - and get kicked 
 you feel better!  I AM    | can pay cash  | out for a even bigger one.
--

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2004-11-05 15:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 15:39 Updated SELinux Release Stephen Smalley
2004-11-03 18:19 ` Karl MacMillan
2004-11-03 19:21 ` Dhruv Gami
2004-11-04  2:15   ` Colin Walters
2004-11-04  7:02     ` Manoj Srivastava
2004-11-04 13:15       ` Luke Kenneth Casson Leighton
2004-11-05  4:06         ` Colin Walters
2004-11-05 10:28           ` Luke Kenneth Casson Leighton
2004-11-05 15:11             ` Colin Walters
2004-11-05 15:51               ` Stephen Smalley
2004-11-05 15:57               ` Luke Kenneth Casson Leighton [this message]
2004-11-05 21:01                 ` Colin Walters
2005-01-03 12:53                 ` Russell Coker
2005-01-03 14:47                   ` Lorenzo Hernández García-Hierro
2004-11-05 12:29           ` Stephen Smalley
2004-11-04 14:35       ` Stephen Smalley
2004-11-04 15:38       ` James Morris
2004-11-04 15:47         ` Stephen Smalley
2004-11-04 14:24   ` Stephen Smalley
2004-11-04  0:59 ` Manoj Srivastava
2004-11-04  3:37   ` Colin Walters
2004-11-04  6:57     ` Manoj Srivastava
2004-11-04 13:38     ` Stephen Smalley
2004-11-04 18:25       ` Christopher J. PeBenito
2004-11-04 18:25         ` Stephen Smalley
2004-11-04 13:33   ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2005-03-09 21:02 Stephen Smalley
2005-06-22 18:57 ` Stephen Smalley
2005-09-07 16:23   ` Stephen Smalley
2005-01-07 20:59 Stephen Smalley
2004-08-19 19:01 Updated SELinux release Stephen Smalley

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=20041105155752.GC5565@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=debian-devel@lists.debian.org \
    --cc=manoj.srivastava@stdc.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=walters@verbum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.