public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Robert Love <rlove@rlove.org>
Cc: John McCutchan <ttb@tentacle.dhs.org>,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	mtk.manpages@gmail.com
Subject: Re: [1/1] Use pid in inotify events.
Date: Sat, 8 Nov 2008 21:40:13 +0300	[thread overview]
Message-ID: <20081108184013.GA11888@ioremap.net> (raw)
In-Reply-To: <acdcfe7e0811081035l56eedf05x8b3b7ee2fc01eee6@mail.gmail.com>

On Sat, Nov 08, 2008 at 01:35:07PM -0500, Robert Love (rlove@rlove.org) wrote:
> Pointing out some other information leak doesn't lessen the pid problem.

I just wanted to show that this is not a security problem.
Since there are others probably even more important.

But I really do not want to start to discuss this, since I already see
that result will be effectively zero, so returning to the original
problem with putting pid into events: if inotify_init() caller has 0
(e)uid or if IO origin has the same (e)uid, are you ok to put pid into
the event?

-- 
	Evgeniy Polyakov

       reply	other threads:[~2008-11-08 18:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <acdcfe7e0811081035l56eedf05x8b3b7ee2fc01eee6@mail.gmail.com>
2008-11-08 18:40 ` Evgeniy Polyakov [this message]
2008-11-08 22:03   ` [1/1] Use pid in inotify events Evgeniy Polyakov
2008-11-10 15:13 ` [take 2] " Evgeniy Polyakov
2008-11-16 23:24 ` [take 3] " Evgeniy Polyakov
2008-11-17 16:59   ` Michael Kerrisk
2008-11-17 17:15     ` Evgeniy Polyakov
2008-11-17 17:23       ` Michael Kerrisk
2008-11-17 17:52         ` Evgeniy Polyakov
2008-11-20 13:09           ` Pavel Machek
2008-11-21 14:03             ` Evgeniy Polyakov
2008-11-21 14:20               ` Michael Kerrisk
2008-11-21 14:37                 ` Evgeniy Polyakov
2008-11-21 14:30               ` Robert Love
2008-11-21 14:53                 ` Evgeniy Polyakov
2008-11-21 14:57                 ` Pavel Machek
2008-11-21 15:08                   ` Evgeniy Polyakov
2008-11-18 13:19     ` Christoph Hellwig
2008-11-19 14:05       ` Evgeniy Polyakov
     [not found]         ` <cfd18e0f0811190634g276b4a2dm5b3d5de25a5c9222@mail.gmail.com>
2008-11-19 14:43           ` Michael Kerrisk
2008-11-20 19:17             ` Ville Syrjälä
2008-11-19 14:53           ` Evgeniy Polyakov
2008-11-20 22:34             ` John McCutchan
2008-11-20 23:06               ` Evgeniy Polyakov
2008-11-21 18:39                 ` Arnd Bergmann
2008-11-22  7:12                   ` David Newall
2008-11-22  9:41                     ` Evgeniy Polyakov
2008-11-22 11:41                       ` David Newall
2008-11-22  9:37                   ` Evgeniy Polyakov
2008-11-24  5:08                     ` John McCutchan
2008-11-24  7:30                       ` Evgeniy Polyakov
2008-11-08 11:42 [1/1] " Evgeniy Polyakov
2008-11-08 14:25 ` Michael Kerrisk
2008-11-08 15:35   ` Evgeniy Polyakov
2008-11-08 16:58     ` Michael Kerrisk
2008-11-08 17:04       ` Robert Love
2008-11-08 17:27         ` Evgeniy Polyakov
2008-11-10 15:20       ` Evgeniy Polyakov
2008-11-10 17:15         ` Michael Kerrisk
2008-11-10 17:20           ` Evgeniy Polyakov

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=20081108184013.GA11888@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rlove@rlove.org \
    --cc=ttb@tentacle.dhs.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