From: Pavel Machek <pavel@ucw.cz>
To: David Wagner <daw-news@cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SECURITY PROBLEM: filesystem permiossion bypass on FD already opened
Date: Sun, 25 Oct 2009 07:30:18 +0100 [thread overview]
Message-ID: <20091025063017.GA1480@ucw.cz> (raw)
In-Reply-To: <hbtc9t$629$1@taverner.cs.berkeley.edu>
> On the other hand, the /proc attack that Pavel explains *is* a
> security problem. But that's different.
I'm glad I convinced at least someone :-). Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-10-25 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 20:00 NiTRo
2009-10-23 20:44 ` Marcin Slusarz
2009-10-23 20:54 ` Pavel Machek
2009-10-23 22:42 ` NiTRo
2009-10-23 20:59 ` Pavel Machek
2009-10-23 22:55 ` David Wagner
2009-10-25 6:30 ` Pavel Machek [this message]
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=20091025063017.GA1480@ucw.cz \
--to=pavel@ucw.cz \
--cc=daw-news@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome