From: Andi Kleen <andi@firstfloor.org>
To: 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libmalware.so: Dazuko Linux/BSD On-Access scanning and control
Date: Wed, 13 Aug 2008 21:37:15 +0200 [thread overview]
Message-ID: <87bpzw1zbo.fsf@basil.nowhere.org> (raw)
In-Reply-To: <48A32CAC.1030605@gmail.com> (7v5w7go9ub0o@gmail.com's message of "Wed, 13 Aug 2008 14:49:16 -0400")
7v5w7go9ub0o <7v5w7go9ub0o@gmail.com> writes:
> (FYI. Dazuko may have trailblazed some of the issues now under
> discussion re: libmalware.so. It has worked well for me.
Against what exactly did it protect you? Please give a concrete example.
-Andi
next prev parent reply other threads:[~2008-08-13 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 18:49 libmalware.so: Dazuko Linux/BSD On-Access scanning and control 7v5w7go9ub0o
2008-08-13 19:37 ` Andi Kleen [this message]
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=87bpzw1zbo.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=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