public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: re: libmalware.so: Dazuko Linux/BSD On-Access scanning and control
Date: Wed, 13 Aug 2008 14:49:16 -0400	[thread overview]
Message-ID: <48A32CAC.1030605@gmail.com> (raw)

(FYI. Dazuko may have trailblazed some of the issues now under 
discussion re: libmalware.so. It has worked well for me. It used to be 
an LKM, it is now a source patch. It is used in a number of commercial 
products)


<http://dazuko.dnsalias.org/wiki/index.php/Main_Page>

"A Virtual Device Driver to Allow Online File Access Control

A common interface is needed, which allows userland applications to
perform online file access control. Dazuko aims to provide that interface."

FWIW, I'm not associated with Dazuko or Antivir; I've been happily using
Dazuko with AntiVir for a year or so.

1. AntiVir includes numerous Linux signatures as well as Windows. So I
scan both 'ix downloads, as well as the process of compiling new software.

2. Other AntiMalwares are using Dazuko, though many are scanning for 
Windows malware only.

3. The AntiVir/Dazuko combination with full heuristics has blocked
access to clearly dangerous JS scripts in my browser cache.

4. IMHO, what is needed is a Dazuko or libmalware/Integrity database 
link. If an md5 of an executable or script is new or has changed, access 
is blocked 'til a response to a popup is given. Access can be blocked; 
one-time allowed; or permanently allowed, in which case the md5 is updated.

Hope This Helps.




             reply	other threads:[~2008-08-13 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 18:49 7v5w7go9ub0o [this message]
2008-08-13 19:37 ` libmalware.so: Dazuko Linux/BSD On-Access scanning and control Andi Kleen
2008-08-13 20:00   ` 7v5w7go9ub0o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A32CAC.1030605@gmail.com \
    --to=7v5w7go9ub0o@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox