From: Matthias Schniedermeyer <ms@citd.de>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 hacked filesystem (by debian exim4 exploit) available for analysis and bugreporting
Date: Mon, 25 Jul 2011 15:45:33 +0200 [thread overview]
Message-ID: <20110725134533.GA23781@citd.de> (raw)
In-Reply-To: <CAPweEDzv+vByC1s2bWRjVQdVLqw4Xf2sUf_CQgVync_YcxtdvQ@mail.gmail.com>
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'?
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2011-07-25 13:53 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 [this message]
2011-07-25 21:08 ` Luke Kenneth Casson Leighton
2011-07-29 19:59 ` Pavel Machek
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=20110725134533.GA23781@citd.de \
--to=ms@citd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
/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