All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: setfiles and non-SE systems
Date: Mon, 1 Dec 2003 21:02:00 +1100	[thread overview]
Message-ID: <200312012102.00554.russell@coker.com.au> (raw)

lstat64("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lgetxattr("/", "security.selinux", 0x84789a0, 255) = -1 EOPNOTSUPP (Operation 
no
t supported)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x2 (flags O_RDWR)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0
x4001a000
_llseek(3, 0, 0xbfffe640, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(3, "/: Operation not supported\n", 27) = 27
close(3)                                = 0
munmap(0x4001a000, 4096)                = 0
write(2, "setfiles:  unable to obtain attr"..., 49) = 49

Above is part of the strace output from trying to run setfiles on a non-SE 
system (kernel 2.4.22 with the ACL patch but no SE patch).

It appears that if we had a kernel patch to provide the security.selinux name 
space as a regular xattr on non-SE systems then we could label the file 
system before installing a SE Linux kernel.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
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.

             reply	other threads:[~2003-12-01 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 10:02 Russell Coker [this message]
2003-12-01 14:42 ` setfiles and non-SE systems Stephen Smalley
2003-12-01 19:14   ` Dale Amon
2003-12-01 19:23     ` Stephen Smalley
2003-12-02  0:43       ` Dale Amon

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=200312012102.00554.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /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.