All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: wakkerma@debian.org
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: straceing SE Linux
Date: Wed, 27 Feb 2002 10:47:02 +0100	[thread overview]
Message-ID: <20020227101339.9FAA5F8E3@lyta.coker.com.au> (raw)

I'm working on hacking strace to trace LSM system calls as used by SE Linux.

Firstly what name should I use to refer to this syscall?  lsm() as the 
library code uses or security() after the sys_security() definition in the 
kernel?

The next issue is that there is one system call defined for LSM (number 223 
on Intel).  The first parameter of this call is the id of the security 
service to manage.  I would like to display selinux() for a SE system call 
lids() for a LIDS call, etc.  However it seems that this would require a 
change to the strace structure.

Should I do so, or am I on the wrong track by wanting to display these as 
different function calls depending on the id parameter?

-- 
Signatures >4 lines are rude.  If you send email to me or to a mailing list
that I am subscribed to which has >4 lines of legalistic junk at the end
then you are specifically authorizing me to do whatever I wish with the
message (the sig won't be read).

--
You have received this message because you are subscribed to the selinux 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.

             reply	other threads:[~2002-02-27 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27  9:47 Russell Coker [this message]
2002-02-27 11:31 ` Metrix
2002-02-27 13:36   ` your mail Stephen Smalley
2002-02-27 13:53 ` straceing SE Linux Stephen Smalley
2002-02-27 16:04   ` Russell Coker
2002-02-27 18:30     ` 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=20020227101339.9FAA5F8E3@lyta.coker.com.au \
    --to=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    --cc=wakkerma@debian.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.