From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable for NS2.28 and NS2.27
Date: Fri, 08 Jul 2005 03:57:00 -0000 [thread overview]
Message-ID: <20050708035619.GC2123@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050708032931.GA2392@efn.org>
On Thu, Jul 07, 2005 at 08:29:31PM -0700, Yitzchak Scott-Thoennes wrote:
>On Wed, Jul 06, 2005 at 11:27:15AM -0400, Larry Hall wrote:
>> I said "virus program". That would be something like
>> Norton AV, McAfee VirusScan, etc.
>
>Hmm, is there any way cygcheck could report on intrusive software like
>virus scanners and firewalls? Though my knowlege on the subject is
>close to nil I think the latter may be doable with WSCEnumProtocols.
You may be onto something here.
We could even run cygcheck as a background process looking for the
installation of virus scanners and popping up warnings when a virus
scanner was introduced. If someone was interested, we could maintain
an active database of virus scanners which would be updated over the
internet.
A future project might entail linking cygcheck to email clients, scanning
them for virus scanner attachments and "quarantining" them. We could
also add a "virus scanner" hook for IE which would detect attempts by
users to download rogue virus scanners to their systems.
If it helps, I could add a cygwin-virus-scanner mailing list devoted to
"first alert" sightings of virus scanners "in the wild".
This could be big.
cgf
next parent reply other threads:[~2005-07-08 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6.2.1.2.0.20050705223027.08ca8288@pop.prospeed.net>
[not found] ` <20050706062832.63358.qmail@web30112.mail.mud.yahoo.com>
[not found] ` <6.2.1.2.0.20050706111849.08d26298@pop.prospeed.net>
[not found] ` <20050708032931.GA2392@efn.org>
2005-07-08 3:57 ` Christopher Faylor [this message]
2005-07-08 4:57 ` Brian Dessent
2005-07-08 5:17 ` One Angry User
2005-07-08 11:51 ` Dave Korn
2005-07-08 14:21 ` Igor Pechtchanski
2005-07-08 6:00 ` Yitzchak Scott-Thoennes
2005-07-08 12:29 ` Christopher Faylor
2005-07-08 13:05 ` Corinna Vinschen
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=20050708035619.GC2123@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).