mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Alistair John Strachan" <s0348365@sms.ed.ac.uk>
Cc: "sena seneviratne" <auntvini@cel.usyd.edu.au>,
	"Tyler Littlefield" <compgeek13@gmail.com>,
	linux-Kernel@vger.kernel.org
Subject: Re: a newbie with the kernel--a few questions
Date: Sat, 17 Jun 2006 12:58:04 +0200	[thread overview]
Message-ID: <9a8748490606170358p4cf1068bh1ab6ba510c98f2d@mail.gmail.com> (raw)
In-Reply-To: <200606161541.39498.s0348365@sms.ed.ac.uk>

On 16/06/06, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> > At 09:12 PM 6/15/2006 -0600, you wrote:
> > >OK, I am pretty good with c. My goal here is... Well, when a user types
> > > who, I don't want it to work, unless its root. (easy to change) but I
> > > want some security like that in the kernel. Also, I want to limit it to
> > > when the user types ps, they can't get everyone's processes, but jsut
> > > there own, unless of course, they are root.
> > >Thanks,
>
> Might also be worth looking at patches like GrSecurity which make general
> policy changes (such as these) and are well tested and robust.
>

Isn't this already doable with SELinux ?

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-06-17 10:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 23:03 Tyler Littlefield
2006-06-16  2:01 ` sena seneviratne
2006-06-16  2:26   ` Vadim Lobanov
     [not found]   ` <001601c690f2$b18756c0$6401a8c0@gramdmasfury>
2006-06-16  3:36     ` sena seneviratne
2006-06-16 14:41       ` Alistair John Strachan
2006-06-17 10:58         ` Jesper Juhl [this message]
2006-06-16  2:29 ` Rik van Riel

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=9a8748490606170358p4cf1068bh1ab6ba510c98f2d@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=auntvini@cel.usyd.edu.au \
    --cc=compgeek13@gmail.com \
    --cc=linux-Kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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

all inboxes | Powered by JetHome®