linux-kernel - Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interfaceforon access scanning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080806152402.GC13996@kroah.com>
Date:	Wed, 6 Aug 2008 08:24:02 -0700
From:	Greg KH <greg@...ah.com>
To:	tvrtko.ursulin@...hos.com
Cc:	Arjan van de Ven <arjan@...radead.org>,
	"Press, Jonathan" <Jonathan.Press@...com>,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	malware-list@...ts.printk.net
Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux
	interfaceforon access scanning

On Wed, Aug 06, 2008 at 10:24:21AM +0100, tvrtko.ursulin@...hos.com wrote:
> Greg KH wrote on 05/08/2008 19:11:41:
> 
> > On Tue, Aug 05, 2008 at 02:04:26PM -0400, Press, Jonathan wrote:
> > > I'm not sure if this is off the direct idea of this thread, or if I am
> > > possibly missing the whole point.
> > 
> > I think you might be missing the point a bit here, as the traditional
> > Unix model that Linux has prevents much of what the "traditional AV"
> > products need to do, right?
> 
> Could you please explain some more what and how do you think Unix model 
> prevents?

It prevents any user from overwriting an existing executable, and it
prevents any user from adding an executable file to a common directory
(/usr/bin).

It also prevents any user from overwriting a different user's data file.

What specific threat model are you feeling is still present on Linux
today that this proposal is supposed to address?

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/