public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Matthias Schniedermeyer <ms@citd.de>, linux-kernel@vger.kernel.org
Subject: Re: ext3 hacked filesystem (by debian exim4 exploit) available for analysis and bugreporting
Date: Fri, 29 Jul 2011 21:59:04 +0200	[thread overview]
Message-ID: <20110729195904.GC1720@ucw.cz> (raw)
In-Reply-To: <CAPweEDybuOpPVidJWg+rfs8rU8y=xo4d3H=P7XQJh_DiKrF4DQ@mail.gmail.com>

On Mon 2011-07-25 22:08:24, Luke Kenneth Casson Leighton wrote:
> On Mon, Jul 25, 2011 at 2:45 PM, Matthias Schniedermeyer <ms@citd.de> wrote:
> > On 25.07.2011 13:08, Luke Kenneth Casson Leighton wrote:
> >> folks, hi,
> >>
> >> apart from anything, files which cannot be deleted (and cannot be
> >> detected as "corrupted" by fsck.ext3) is pretty damn serious.
> >
> > You did try lsattr and checked that the files aren't 'immutable'?
> 
>  i didn't! :)  didn't know about (but should have guessed) ext3
> attributes.  they are indeed - thank you matthias.
> 
> root@quietbaby:/mnt/horsebox/tmp3# lsattr *
> ----ia------------- bin3/kill
> ----ia------------- bin3/ps
> ----ia------------- c.pl
> ----ia------------- e.conf
> ----ia------------- sbin3/sysctl
> ----ia------------- usrbin3/uptime
> ----ia------------- usrbin3/tload
> ----ia------------- usrbin3/free
> ----ia------------- usrbin3/top
> ----ia------------- usrbin3/vmstat
> ----ia------------- usrbin3/watch
> ----ia------------- usrbin3/skill
> ----ia------------- usrbin3/pmap
> ----ia------------- usrbin3/pgrep
> ----ia------------- usrbin3/slabtop
> ----ia------------- usrbin3/pwdx
> ----ia------------- usrbin3/snice
> ----ia------------- usrbin3/pkill
> ----ia------------- usrbin3/w
> 
> so - looks like it's not as bad as i thought.

Should ls -l be moddified to show something when file has immutable
(and friends) set?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2011-07-29 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 12:08 ext3 hacked filesystem (by debian exim4 exploit) available for analysis and bugreporting Luke Kenneth Casson Leighton
2011-07-25 13:45 ` Matthias Schniedermeyer
2011-07-25 21:08   ` Luke Kenneth Casson Leighton
2011-07-29 19:59     ` Pavel Machek [this message]
2011-07-29 21:31       ` Matthias Schniedermeyer
2011-07-29 22:51         ` Pádraig Brady
2011-07-30  2:47           ` Kyle Moffett
2011-07-30  9:14           ` Jim Meyering
2011-07-30 13:03             ` Luke Kenneth Casson Leighton
2011-07-30 13:15           ` Luke Kenneth Casson Leighton
2011-07-30 12:58       ` Luke Kenneth Casson Leighton

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=20110729195904.GC1720@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcl@lkcl.net \
    --cc=ms@citd.de \
    /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