All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Pattie" <pattieja@pcxperience.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] viruses
Date: Fri, 05 Mar 2004 22:33:24 +0000	[thread overview]
Message-ID: <40490034.5090805@pcxperience.com> (raw)
In-Reply-To: <20040305221016.11186.qmail@web60507.mail.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Chemko wrote:
| If you are talking about application layer viruses like through email:
|
| Kazaa, etc worms cannot be blocked since nobody's written filters for
| them.

I have seen "solutions" that help the Kazaa problem.  One was something
like P2PWall, I think.  There are even extensions that have been
integrated with the IPCop firewall distro to block Kazaa (couldn't get
them to work, but that's a different story).

- --
Jason A. Pattie
pattieja@xperienceinc.com
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFASQA0uYsUrHkpYtARAq6UAJ43dgLXoBcmQfbx7LcjXC8JOdgU8ACggnwn
NoyntAbwbF+xur8tUQh5caw=Q4Wi
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-03-05 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 22:10 [LARTC] viruses Yemi Fowe
2004-03-05 22:27 ` Daniel Chemko
2004-03-05 22:31 ` Jason A. Pattie
2004-03-05 22:33 ` Jason A. Pattie [this message]
2004-03-05 22:42 ` Nathan Littlepage
2004-03-05 22:53 ` Nathan Littlepage

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=40490034.5090805@pcxperience.com \
    --to=pattieja@pcxperience.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.