linux-kernel - Kernel Event Notification Subsystem (was: fanotify - overall design before I start sending patches)

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200908061650.23973.a1426z@gawab.com>
Date:	Thu, 6 Aug 2009 16:50:23 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Tvrtko Ursulin <tvrtko.ursulin@...hos.com>
Cc:	Douglas Leeder <douglas.leeder@...hos.com>,
	Pavel Machek <pavel@....cz>, Eric Paris <eparis@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"malware-list@...sg.printk.net" <malware-list@...sg.printk.net>,
	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	"greg@...ah.com" <greg@...ah.com>,
	"jcm@...hat.com" <jcm@...hat.com>, "tytso@....edu" <tytso@....edu>,
	"arjan@...radead.org" <arjan@...radead.org>,
	"david@...g.hm" <david@...g.hm>,
	"jengelh@...ozas.de" <jengelh@...ozas.de>,
	"aviro@...hat.com" <aviro@...hat.com>,
	"mrkafk@...il.com" <mrkafk@...il.com>,
	"alexl@...hat.com" <alexl@...hat.com>,
	"hch@...radead.org" <hch@...radead.org>,
	"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
	"mmorley@....in" <mmorley@....in>
Subject: Kernel Event Notification Subsystem (was: fanotify - overall design before I start sending patches)

Peter Zijlstra wrote:
> Like said, having the filesystem block actions based on external
> processes seems just asking for trouble.

I can't see anything wrong with that.  In fact, moving policy into userland 
seems like the correct approach anyway.  IOW, the fact that the kernel is 
dealing with policy all over the place is completely flawed.

What we really need, is to take the hard-coded policy burden out of the 
kernel, and pipe all requests into dynamically configurable userland.

Which implies a "Kernel Event Notification Subsystem" that would by default 
allow requests for root, and deny them for others, unless there is a userland 
daemon that would respond differently within a timeout period.

Thanks!

--
Al

--
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/