From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] DMCA loop hole
Date: Tue, 14 Aug 2001 15:17:29 +0200 [thread overview]
Message-ID: <20010814151729.E20719@lug-owl.de> (raw)
In-Reply-To: <Pine.BSO.4.33.0108140204380.22991-100000@aaieee.daisy-chan.org> <3B791B59.5F5F4113@idb.hist.no>
In-Reply-To: <3B791B59.5F5F4113@idb.hist.no>; from helgehaf@idb.hist.no on Tue, Aug 14, 2001 at 02:36:41PM +0200
On Tue, 2001-08-14 14:36:41 +0200, Helge Hafting <helgehaf@idb.hist.no>
wrote in message <3B791B59.5F5F4113@idb.hist.no>:
> "Joshua b. Jore" wrote:
> How is making a virus any different from making any other weapon, like
> a gun? Using it against someone might of course be illegal.
Well... It's quite different in some points:
- building some kind of weapon means hand-working on
"real" iron.
- programming a virus is just altering bits.
- Nobody will claim building an arbitrary warpon is some
kind of art ("I've always seen a weapon within this
block of iron. I've only cut off some peaces to
let it appear")
- Many programmers will in fact have others to see their
work as art. Esp., if it's kind of difficult work.
Another effect is that firing a weapon means real movement of
material whereas "firing" a virus is "just" altering bits. For
humans, this is a big difference. I (speaking for me) would feel
quite more guilty firing a weapon than firing a virus...
> There are certainly valid reasons for making viruses. For example
> in order to test (and develop) antivirus software that
> automatically detect new viruses without being told about them first.
There are even more uses of viruses: a major one is to show
up security flaws. As of today, we've reached (in some countries)
a state of stagnation (sp?):
- You think you found some kind of security weakness
- You're not allowed to do further investigation because
you mustn't do reverse engineering
- You're asked to report that bug. Then, you may wait
for the next update soming some months later (which
may cost you some $$). However, what so you do if
your software you've just found a security relevant bug
in isn't licensed? You can't report the bug. (Which
is why I use Linux at al.)
Then, you've got 2 possibilities: Either the leak is fixed before
some maliculous people write a virus for, or you hope (or write it
yourself) that a virus will occur on this topic. Reason: if it's
a really bad virus, people will fasten their work on your bug and
you'll get your patch learlier.
> Oh, and surely someone can invent an excuse for using a virus
> offensively
> too. "I need this to defend my site from cyber-terrorists..."
Come on, don't fiddle with the bullshit. Software (both, commercial
as well as GPLed) lives and goes through evolution. Weak species
(those with bugs and security flaws) will die out, stronger ones
(stronger against virus attacks) will survive. By sending out
viruses, you put more preassure on the weak species.
Looking at today's software world, you'll find thousands fo programs
doing more-or-less the same. However, all of them need to be cared
about. Putting preassure on this system will help minorities
to better grow because it's easier to care about short programs
than about monoliths (like famous word progrssing programs and so
on).
OTOH, this suggests to keep really near to up-to-date software. I
like that, too. Looking for bugs in *old* versions is boring.
The concept of only working on HEAD sounds better to me...
So my result: I'm not that much against viruses. People using
computers shoul know what they do. Then, they'll never (or not
that often) get hit by a virus. I've never really had trouble
with them:-)
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
next prev parent reply other threads:[~2001-08-14 13:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 4:14 [OT] DMCA loop hole James Simmons
2001-08-01 5:45 ` Alexander Viro
2001-08-01 5:49 ` James Simmons
2001-08-01 9:40 ` Paul G. Allen
2001-08-01 10:47 ` Helge Hafting
2001-08-01 11:16 ` Anton Altaparmakov
2001-08-01 6:44 ` Joshua Jore
2001-08-01 13:54 ` Helge Hafting
2001-08-01 17:18 ` [very OT] " Garett Spencley
2001-08-01 20:40 ` Justin Guyett
2001-08-02 0:14 ` [OT] " Paul G. Allen
2001-08-03 21:52 ` Joseph Pingenot
2001-08-03 22:09 ` Alan Cox
2001-08-03 22:16 ` Joseph Pingenot
2001-08-03 22:45 ` Jakob Østergaard
2001-08-03 22:31 ` nick
2001-08-03 22:46 ` Alan Shutko
2001-08-03 23:45 ` Paul G. Allen
2001-08-03 22:51 ` Mike Harrold
2001-08-03 23:14 ` Dan Hollis
2001-08-04 0:51 ` Paul G. Allen
2001-08-04 1:34 ` Rik van Riel
2001-08-11 12:10 ` Pavel Machek
2001-08-14 7:07 ` Joshua b. Jore
2001-08-14 12:36 ` Helge Hafting
2001-08-14 13:17 ` Jan-Benedict Glaw [this message]
2001-08-14 14:32 ` Richard B. Johnson
2001-08-14 22:13 ` Paul G. Allen
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=20010814151729.E20719@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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