All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: linux-kernel@vger.kernel.org
Subject: CAP_LINUX_IMMUTABLE question
Date: Tue, 7 Aug 2001 12:08:50 +0100	[thread overview]
Message-ID: <20010807120850.A18750@dev.sportingbet.com> (raw)

Hi there

I am currently trying to tie down the capability bounding set on one of my
servers.  CAP_SYS_RAWIO and CAP_SYS_MODULE have been a great success (although
dropping CAP_SYS_RAWIO seems to prevent reading /proc/sys/kernel/cap-bound).

I now want to drop CAP_LINUX_IMMUTABLE, and have (I think) done that.  However,
it seems to make no difference to my ability to set or clear the immutable
attribute.  I tried this on ext2 and ext3 filesystems just to be on the safe
side.

[root@henry /boot]# lcap CAP_LINUX_IMMUTABLE
[root@henry /boot]# lsattr ./vmlinux-2.4.2-2smp
---i--------- ./vmlinux-2.4.2-2smp
[root@henry /boot]# chattr -i ./vmlinux-2.4.2-2smp
[root@henry /boot]# lsattr ./vmlinux-2.4.2-2smp
------------- ./vmlinux-2.4.2-2smp
[root@henry /boot]# chattr +i ./vmlinux-2.4.2-2smp
[root@henry /boot]# lsattr ./vmlinux-2.4.2-2smp
---i--------- ./vmlinux-2.4.2-2smp

I thought that giving up CAP_SYS_RAWIO may have forfeited my ability to drop
any further caps, so I rebooted and dropped CAP_SYS_MODULE and
CAP_LINUX_IMMUTABLE first, just to be on the safe side.  This made no visible
difference.

Am I doing anything obviously dumb?

Sean

             reply	other threads:[~2001-08-07 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 11:08 Sean Hunter [this message]
2001-08-07 16:50 ` CAP_LINUX_IMMUTABLE question Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2006-12-28 21:52 Aaron Cohen

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=20010807120850.A18750@dev.sportingbet.com \
    --to=sean@dev.sportingbet.com \
    --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 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.