From: Will Smith <wilsmith@iglou.com>
To: speakup@braille.uwo.ca
Subject: Open Virus
Date: Thu, 11 Sep 2003 10:47:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.56.0309111044561.21582@shell1> (raw)
In-Reply-To: <20030909042543.GB5723@lnx3.holmesgrown.com>
I thought others might enjoy this bit of humor:
Will
wilsmith@iglou.com
Thursday, August 28 12:01 AM EDT
Open Source Community
Developing Their Own Viruses
By [15]Brian Briggs
Helsinki, Finland - Open source developers plan to challenge
Microsoft's dominance in the world of viruses by developing their own
through the Open Virus Project (OVP), and unlike proprietary Microsoft
viruses, the open source versions will infect across all platforms.
[biohazard.jpg] Heading the development of the OVP is Jukka Koskelin.
He explained, "We took a look at the virus marketspace and realized
that Microsoft has over a 95% share of all viruses developed. I don't
think the Linux community can be taken seriously if we don't increase
our share in that area."
"The viruses we're developing will work cross-platform unlike
Microsoft viruses which only work on Windows systems. There are ports
to Linux, *BSD, Solaris, and yes, even Windows. We should have a Mac
port in a couple of months," Koskelin continued.
The OVP currently has two viruses in beta: "eyespy" and "GPLdaemon."
Eyespy installs a spyware checking program, and notifies OVP, so they
can inform the user that they're being spied on. GPLdaemon uses spare
CPU cycles to check every file on an infected users hard drive
bit-by-bit to see if it contains any software that violates the GPL.
The viruses will arrive as .tar.gz attachments and will use automake.
Both eyespy and GPLdaemon will need to be compiled and executed by the
user for them to be infected. The viruses can use any e-mail program
to propagate, and do not require Outlook or Outlook Express.
"We had a lot of arguments on the OVP mailing list about whether to
send it out as source code or as an executable, but eventually we
decided that source would spread much more rapidly as it would be
optimized for each system," said Koskelin. "I know a few programmers
outside the project have already created .rpm and .deb packages,
however."
References
Visible links
1. http://www.bbspot.com/index.html
2. http://www.bbspot.com/politics/
3. http://www.bbspot.com/Legal/support_faq.html
4. http://www.bbspot.com/Log/index.html
5. http://www.guptamedia.com/f-ad.php?BBspot.com
prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
automated nfbtrans; was Re: Continuous speaker beep (fwd) Cheryl Homiak
` William F. Acker WB2FLW +1-303-722-7209
` Cheryl Homiak
` JOHN LEE
` automated nfbtrans Christopher Moore
` Cheryl Homiak
` Steve Holmes
` Will Smith [this message]
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=Pine.GSO.4.56.0309111044561.21582@shell1 \
--to=wilsmith@iglou.com \
--cc=speakup@braille.uwo.ca \
/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).