From: Helge Hafting <helge.hafting@aitel.hist.no>
To: jonathan@jonmasters.org
Cc: Chris Ball <cjb@mrao.cam.ac.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OT] inotify hack for locate
Date: Mon, 06 Mar 2006 10:31:33 +0100 [thread overview]
Message-ID: <440C0175.7040909@aitel.hist.no> (raw)
In-Reply-To: <35fb2e590603051704k120e0257wb39c3e3eb1cf0b49@mail.gmail.com>
Jon Masters wrote:
>You're right. What I want really is to be able to bind to a netlink
>socket and get told about particular file IO operations I'm interested
>in for the /whole/ of a filesystem. The same kind of thing that real
>time anti-virus/anti-spam people want to do anyway.
>
>
>
Do they?
I thought all this mail processing could be done in the mailserver
and/or mail reader. Why detect spam by looking for generic file
creation when you can trivially tap into mail as it arrives?
As for the non-existent virus problem - it is mostly prevented
by users not being administrators. And you can go further
with a readonly /usr and a noexec /home.
Helge Hafting
next prev parent reply other threads:[~2006-03-06 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 21:36 [OT] inotify hack for locate Jon Masters
2006-03-05 21:42 ` Jesper Juhl
2006-03-05 21:50 ` Jon Masters
2006-03-06 9:23 ` Helge Hafting
2006-03-06 21:59 ` Pavel Machek
2006-03-05 21:53 ` Robin Holt
2006-03-05 22:02 ` Jon Masters
2006-03-05 21:43 ` Lee Revell
2006-03-05 23:08 ` Benjamin LaHaise
2006-03-05 23:30 ` Måns Rullgård
2006-03-06 21:53 ` Pavel Machek
2006-03-06 22:08 ` Måns Rullgård
2006-03-06 22:22 ` Pavel Machek
2006-03-08 13:56 ` Jan Engelhardt
2006-03-05 23:41 ` Chris Ball
2006-03-06 1:04 ` Jon Masters
2006-03-06 9:31 ` Helge Hafting [this message]
2006-03-06 13:10 ` Jon Masters
2006-03-07 0:11 ` Lee Revell
2006-03-07 0:33 ` Jon Masters
2006-03-07 10:26 ` Steven Rostedt
2006-03-09 2:44 ` Jon Masters
2006-03-06 7:49 ` Arjan van de Ven
2006-03-06 13:12 ` Jon Masters
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=440C0175.7040909@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=cjb@mrao.cam.ac.uk \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.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