linux-kernel - Re: [malware-list] [RFC 0/5] [TALPA] Intro toalinuxinterfaceforonaccess 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-next>] [day] [month] [year] [list]

Date:	Tue, 5 Aug 2008 15:26:38 -0700
From:	Greg KH <greg@...ah.com>
To:	"Press, Jonathan" <Jonathan.Press@...com>
Cc:	Theodore Tso <tytso@....edu>,
	Arjan van de Ven <arjan@...radead.org>,
	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	malware-list@...ts.printk.net,
	linux-security-module@...r.kernel.org
Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro
	toalinuxinterfaceforonaccess scanning

On Tue, Aug 05, 2008 at 06:12:34PM -0400, Press, Jonathan wrote:
> Sorry for the top-post... but I give up.
>  
> I don't think I'm stupid, but frankly I don't understand the point of
> the questions being asked in the last three responses to my statement.
> I don't know why they are relevant, and I don't know how to answer
> them in a framework that we can all understand at the same time.  What
> is my threat model?  Naively stated, it is that there is a file on a
> machine that might do damage, either there or elsewhere, and I want to
> find it and get rid of it in the most efficient way.  I am not
> defining the nature of the damage or the mechanism.

If you can not define this, in a precise manner, then how can we expect
to review the proposed solution to ensure that it matches your needs?

Without that, this patchset is going to go nowhere but into the circular
bin :(

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/