|| ||Theodore Tso <tytso-AT-mit.edu>|
|| ||Rik van Riel <riel-AT-redhat.com>|
|| ||Re: [malware-list] [RFC 0/5] [TALPA] Intro
|| ||Tue, 5 Aug 2008 21:44:36 -0400|
|| ||Eric Paris <eparis-AT-redhat.com>, Greg KH <greg-AT-kroah.com>,
Al Viro <viro-AT-ZenIV.linux.org.uk>,
"Press, Jonathan" <Jonathan.Press-AT-ca.com>,
Arjan van de Ven <arjan-AT-infradead.org>,
On Tue, Aug 05, 2008 at 08:46:00PM -0400, Rik van Riel wrote:
> My real worry is that the anti-virus companies have been working
> with an enforcement policy that has been evolving slowly from the
> DOS days, while today's threat model has changed considerably.
... and which also doesn't into account some of the facilities which
Linux has, that DOS/Windows does not have.
Part of the problem I suspect is that the AV folks have managed to get
CIO's believe that all computer systems need to have anti-virus
software, of the same design that is needed for DOS/Windows systems.
This state of delusion is so bad that apparently some AV engineers
aren't even willing to reason from first principles what is necessary
or not to maintain a secure system.
And arguably, if the goal is security theater, much like the security
lines in airports, perhaps it doesn't matter. If there are silly
CIO's that are willing to pay for such a thing, regardless of whether
or not it is actually *necessary* to maintain security, one school of
capitalism would say it doesn't matter if it actually provides any
functional value or not.
On the other hand, it seems pretty clear there are plenty of LKML
developers who aren't buying it. :-)
It may be helpful to separate the threat model into at least three
The Linux Desktop (where clueless users may be tricked into
The Linux File Server (where it is *highly* unlikely to have
active running malware, since there are no clueless
users running on said file server), but where malware
may be stored and read over CIFS, NFS, etc.
The Linux Mail server is really a restricted case of the Linux
Fileserver; where the only way in is SMTP, and the
only protocol out is IMAP/POP.
Clamav arguably does a very nice job for the third case. And the
number of ways in and out for a Linux fileserver is sufficiently small
(and there are no clueless users to start the malware program
running), that it's relatively easy to reason about.
In the Linux Desktop case, you do have to worry about clueless users,
but in general you don't have to worry about serving CIFS or NFS on
It seems that the AV folks are trying to argue for a worst case
scenario --- one where you have a clueless user, *and* you have a root
comproise, *and* it is also simultaneously serving as a high output
fileserver. #1, I think it is questionable whether this is a
reasonable model, and #2, if root is compromised, no amount of
scanning software will helpyou, since the malware can simply directly
attach and disable the scanning software.
But it is specifically this sort of threat analysis and explicit
detailing of the assumptions of what capabilities the attacker has
which is critical for proceeding. The fact at least one AV engineer
thinks it's pointless to do this sort of low-level design is
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)