[lkml]   [2008]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [malware-list] [RFC 0/5] [TALPA] Intro to alinuxinterfaceforonaccess scanning
On Tue, Aug 05, 2008 at 05:23:39PM -0400, Press, Jonathan wrote:
> -----Original Message-----
> From: Greg KH []
> Sent: Tuesday, August 05, 2008 5:15 PM
> To: Press, Jonathan
> Cc: Theodore Tso; Arjan van de Ven; Eric Paris;
> Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to
> alinuxinterfaceforonaccess scanning
> On Tue, Aug 05, 2008 at 04:37:42PM -0400, Press, Jonathan wrote:
> >
> > [JON PRESS] I don't get the connection between what I said and your
> > point about not needing blocking open() interface. If I ftp into a
> > Linux machine and GET an infected file, you want FTP to go right ahead
> > and read it and send it to me over the wire?
> Shouldn't that be the issue of the FTP server itself not serving up
> "invalid" files, and not the kernel? Why not just hook in it, I'm
> pretty sure they already provide this kind of interface, right?
> [JON PRESS] So how would that work? The FTP server would have code
> that called into someone's AV SDK (maybe CA's, maybe not) and scanned
> the file before sending. OK. What about all the thousands of other
> applications that might access a file and send it somewhere, or copy it
> somewhere.

Ok, let's stop right here.

Please answer Al's question:
What is the threat model this proposal is attempting to address?

Unless this is well defined, we will go down the "hook this here", "but
what about..." argument back and forth for a very long time getting no

So please let's end this thread right now and can someone please post
the answer to this question.


greg k-h

 \ /
  Last update: 2008-08-05 23:49    [W:0.174 / U:1.152 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site