From: Daryl Tester <dt-lkml@handcraftedcomputers.com.au>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Sven Wegener <sven.wegener@stealer.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM?: "permission denied" when accessing /proc/self/fd/* after setuid
Date: Fri, 08 Aug 2008 12:29:26 +0930 [thread overview]
Message-ID: <489BB68E.7040508@handcraftedcomputers.com.au> (raw)
In-Reply-To: <489BAE70.5080909@handcraftedcomputers.com.au>
Daryl Tester wrote:
> Alexey Dobriyan wrote:
>> Something similar was fixed in 2.6.22, but let me check.
Oh, hang on, that's just for directory access. That still
leaves the issue of the open() vs dup() semantics. Nuts.
Cheers,
--dt
prev parent reply other threads:[~2008-08-08 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 6:16 PROBLEM?: "permission denied" when accessing /proc/self/fd/* after setuid Daryl Tester
2008-08-07 15:20 ` Sven Wegener
2008-08-08 0:38 ` Daryl Tester
2008-08-08 0:50 ` Alexey Dobriyan
2008-08-08 2:24 ` Daryl Tester
2008-08-08 2:59 ` Daryl Tester [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=489BB68E.7040508@handcraftedcomputers.com.au \
--to=dt-lkml@handcraftedcomputers.com.au \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sven.wegener@stealer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.