From: Kyle Moffett <mrmacman_g4@mac.com>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: Willy Tarreau <willy@w.ods.org>, linux-kernel@vger.kernel.org
Subject: Re: Why Ext2/3 needs immutable attribute?
Date: Sun, 17 Apr 2005 12:23:02 -0400 [thread overview]
Message-ID: <efa44afd521dbc92f406cbbfd18ae9bd@mac.com> (raw)
In-Reply-To: <4ae3c140504170912b36e9b1@mail.gmail.com>
On Apr 17, 2005, at 12:12, Xin Zhao wrote:
> Thanks for your reply.
>
> Yes. I know, with immutable, even root cannot modify sensitive
> files. What I am curious is if an intruder has root access, he may
> have many ways to turn off the immutable protection and modify files.
> So immutable is designed just to prevent a valid root from making
> silly mistakes?
>
> Xin
But without the proper capability, root _can't_ change the immutable
bit. Of course, that also applies to DAC checks too. Personally, I
find the immutable bit most useful at preventing accidents. I have
several scripts designed specifically to access the same file, and I
want to prevent one of my admins from accidentally editing that file
by hand. The best way is with a big comment in the file itself and
the immutable bit.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2005-04-17 16:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 15:54 Why Ext2/3 needs immutable attribute? Xin Zhao
2005-04-17 16:03 ` Willy Tarreau
2005-04-17 16:12 ` Xin Zhao
2005-04-17 16:23 ` Kyle Moffett [this message]
2005-04-17 16:27 ` Willy TARREAU
2005-04-17 19:47 ` Bernd Eckenfels
2005-04-17 23:48 ` Xin Zhao
2005-04-18 1:53 ` Bernd Eckenfels
2005-04-17 19:45 ` Bernd Eckenfels
2005-04-23 16:50 ` dean gaudet
2005-04-23 18:33 ` DervishD
2005-04-23 18:49 ` Kyle Moffett
2005-04-23 19:12 ` DervishD
2005-04-23 20:37 ` Kyle Moffett
2005-04-23 22:54 ` DervishD
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=efa44afd521dbc92f406cbbfd18ae9bd@mac.com \
--to=mrmacman_g4@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.com \
--cc=willy@w.ods.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.