public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xin Zhao <uszhaoxin@gmail.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why Ext2/3 needs immutable attribute?
Date: Sun, 17 Apr 2005 12:12:13 -0400	[thread overview]
Message-ID: <4ae3c140504170912b36e9b1@mail.gmail.com> (raw)
In-Reply-To: <20050417160306.GB777@alpha.home.local>

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


On 4/17/05, Willy Tarreau <willy@w.ods.org> wrote:
> On Sun, Apr 17, 2005 at 11:54:34AM -0400, Xin Zhao wrote:
> > Why not simply unset the write bit for all three groups of users?
> > That seems to be enough to prevent file modification.
> >
> > Immutable seems to only add one more protection level in case of
> > misconfiguration on standard access right bits.  Is that right?
> 
> With immutable, even root cannot modify the file accidentely. It is
> very useful for critical configuration files.
> 
> Willy
> 
>

  reply	other threads:[~2005-04-17 16:12 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 [this message]
2005-04-17 16:23     ` Kyle Moffett
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=4ae3c140504170912b36e9b1@mail.gmail.com \
    --to=uszhaoxin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox