From: Stefan Traby <stefan@hello-penguin.com>
To: "Vladimir V. Saveliev" <vs@namesys.botik.ru>
Cc: Chris Mason <mason@suse.com>, Marc Lehmann <pcg@goof.com>,
reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] major security bug in reiserfs (may affect SuSE Linux)
Date: Wed, 10 Jan 2001 18:03:53 +0100 [thread overview]
Message-ID: <20010110180353.B2101@stefan.sime.com> (raw)
In-Reply-To: <75150000.979093424@tiny> <3A5C8780.5B02EC8A@namesys.botik.ru>
In-Reply-To: <3A5C8780.5B02EC8A@namesys.botik.ru>; from vs@namesys.botik.ru on Wed, Jan 10, 2001 at 07:02:08PM +0300
On Wed, Jan 10, 2001 at 07:02:08PM +0300, Vladimir V. Saveliev wrote:
> Hmm, wouldn't it make existing long named files unreachable?
This is not of primary interest. Security first.
The only way to recover those files secure without risking a crash
is maybe to let fsck rename those long files after the patch.
Before the 255-limit-patch a rename(2) may work, but without a directory
lookup from userland; quite hard to do.
When I played with Marc's case, I needed to reboot 2 times because I
tried to use tab-expansion on bash to get the filename; which caused
a machine freeze.
perl -e 'rmdir "x" x 768' worked,
or under bash
rmdir <ESC>768x should work, too.
Really, the 255-limit is essential as long as "struct dirent/64" has
d_name[255] hard coded. Somebody should send Drepper a patch;
I did not understand why he accepted a NAME_MAX of 4032 patch for
reiserfs while knowing the hardcoded dirent limit.
--
ciao -
Stefan
" ( cd /lib ; ln -s libBrokenLocale-2.2.so libNiedersachsen.so ) "
Stefan Traby Linux/ia32 fax: +43-3133-6107-9
Mitterlasznitzstr. 13 Linux/alpha phone: +43-3133-6107-2
8302 Nestelbach Linux/sparc http://www.hello-penguin.com
Austria mailto://st.traby@opengroup.org
Europe mailto://stefan@hello-penguin.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-10 17:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010110023208.B296@cerebro.laendle>
2001-01-10 2:23 ` [reiserfs-list] major security bug in reiserfs (may affect SuSE Linux) Chris Mason
2001-01-10 4:43 ` David Ford
2001-01-10 5:47 ` Alexander Viro
2001-01-10 15:48 ` Chris Mason
2001-01-10 17:38 ` Alexander Viro
2001-01-10 18:48 ` Chris Mason
2001-01-11 0:47 ` Alexander Viro
2001-01-10 16:41 ` Andrea Arcangeli
2001-01-10 16:02 ` Vladimir V. Saveliev
2001-01-10 16:09 ` Chris Mason
2001-01-10 16:29 ` [reiserfs-list] major security bug in reiserfs (may affect SuSELinux) Vladimir V. Saveliev
2001-01-10 17:03 ` Stefan Traby [this message]
2001-01-10 17:11 ` [reiserfs-list] major security bug in reiserfs (may affect SuSE Linux) Stefan Traby
2001-01-10 2:40 ` Chris Mason
2001-01-11 11:05 ` Hans Reiser
2001-01-09 23:42 Marc Lehmann
2001-01-10 0:43 ` [reiserfs-list] " John Morrison
2001-01-10 0:51 ` Chris Mason
2001-01-10 0:56 ` Vladimir V. Saveliev
2001-01-10 13:08 ` Gnea
2001-01-10 11:03 ` Dirk Mueller
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=20010110180353.B2101@stefan.sime.com \
--to=stefan@hello-penguin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=pcg@goof.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.botik.ru \
/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