[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080815143703.GB8860@ucw.cz>
Date: Fri, 15 Aug 2008 16:37:04 +0200
From: Pavel Machek <pavel@...e.cz>
To: Theodore Tso <tytso@....edu>, Eric Paris <eparis@...hat.com>,
tvrtko.ursulin@...hos.com, alan@...rguk.ukuu.org.uk,
andi@...stfloor.org, Arjan van de Ven <arjan@...radead.org>,
hch@...radead.org, linux-kernel@...r.kernel.org,
malware-list@...ts.printk.net,
malware-list-bounces@...sg.printk.net, peterz@...radead.org,
viro@...IV.linux.org.uk
Subject: Re: [malware-list] TALPA - a threat model? well sorta.
On Thu 2008-08-14 11:50:28, Theodore Tso wrote:
> On Thu, Aug 14, 2008 at 09:48:33AM -0400, Eric Paris wrote:
> >
> > There needs to be a way to say that an inode in cache needs to be
> > rescanned. 3 states this flag can be. Clean, Dirty, Infected. The
> > current talpa solution involves a global monotomically increasing
> > counter every time you change virus defs or make some "interesting"
> > change. If global == inode flag we are clean. If global == negative
> > inode flag we are infected. if global > inode flag we are dirty and
> > need a scan.
>
> "Infected" just means to instantly return an error when the file is
> opened or if an already opened file descriptor is read or mmap'ed,
> right? If file is already mmaped(), what's the plan? Send a kill -9
Me thinks about naming my machine
host-inline-real-virus-or-at-least-identifiable-part-here.cz, then
having fun with people not able to access their apache logs.
Returning an error when you think you see a virus is a great
invitation to DoS attack, really.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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