Messages in this thread | | | Date | Mon, 4 Aug 2008 20:26:19 -0400 | From | Christoph Hellwig <> | Subject | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| |
On Mon, Aug 04, 2008 at 03:32:49PM -0700, Greg KH wrote: > > 1. Intercept file opens (exec also) for vetting (block until > > decision is made) and allow some userspace black magic to make > > decisions.
NACK, this kind of policy should be done in kernelspace.
> > 2. Intercept file closes for scanning post access
Not even possible for mmap, and dumb otherwise, NACK.
> > 6. Scan files directly not relying on path. Avoid races and problems with namespaces, chroot, containers, etc.
Explain?
> > 9. Mark a processes as exempt from on access scanning
Nack, this completely defeats the purpose.
> > 11. Exclude sub-trees from scanning based on filesystem path > > 12. Include only certain sub-trees from scanning based on filesystem path
Nack, please no pathname based idiocies.
| |