linux-kernel - Re: [Question] inotify : process based filtering of events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081220171340.GA4655@ioremap.net>
Date:	Sat, 20 Dec 2008 20:13:40 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Niraj kumar <niraj17@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [Question] inotify : process based filtering of events

On Sat, Dec 20, 2008 at 06:43:01PM +0530, Niraj kumar (niraj17@...il.com) wrote:
> I was hoping to add a flag (similar to IN_ATTRS that you have added)
> which, when used, will only collect events for the calling
> process and it's children...

With nested attributes patch you can add your own callback which will
check private list of interested pids and only add event into the queue
when current credentials match stored data. IMHO that will br much
smaller amount of work than extending inotify with new flag and redoing
new event structure processing. But it is up to you to decide of course
:)

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/