[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080805183845.GA11375@kroah.com>
Date: Tue, 5 Aug 2008 11:38:45 -0700
From: Greg KH <greg@...ah.com>
To: "Press, Jonathan" <Jonathan.Press@...com>
Cc: Arjan van de Ven <arjan@...radead.org>,
Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
malware-list@...ts.printk.net,
linux-security-module@...r.kernel.org
Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux
interfaceforon access scanning
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
On Tue, Aug 05, 2008 at 02:34:26PM -0400, Press, Jonathan wrote:
> You're right...I am not talking about blocking at all -- which may be a
> further indication that I am missing the specific point of this thread.
>
> But be that as it may... I don't want to have to use more than one
> interface to get all the events I am interested in. I want to register
> as a client and listen, and get everything I need from the same place.
That's an implementation issue, not a requirement. If it's a
requirement, it sure is a lazy one :)
> Also, it seems to me that for my purposes, close is discrete enough. It
> tells me that there is now something out there that should be looked at.
So, if you hook glibc to catch all calls to close, is that sufficient?
thanks,
greg k-h
--
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/
Powered by blists - more mailing lists