From: Joseph Pingenot <jap3003@ksu.edu>
To: "Paul G. Allen" <pgallen@randomlogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] DMCA loop hole
Date: Fri, 3 Aug 2001 16:52:22 -0500 [thread overview]
Message-ID: <20010803165221.C11011@ksu.edu> (raw)
In-Reply-To: <Pine.BSO.4.33.0108010137240.7994-100000@aaieee.daisy-chan.org> <3B689B50.33E84D33@randomlogic.com>
In-Reply-To: RE: [Re: [OT] DMCA loop hole]
>From Paul G. Allen on Wednesday, 01 August, 2001:
>To take another angle, those of us who actively look for exploits in software (because companies like M$ fail to do so themselves) risk being sued for doing so.
Hrm. Very good point. However, under most EULA's I've seen, reverse
engineering is already a no-no.
>This makes jobs like mine EXTREMELY difficult because on the one hand I don't want my company using software that will allow Joe Cracker to take over our
>machines, and on the other I don't want the company sued just because I did some necessary reverse engineering in order to prevent it (again, because the
>software mfg. can't be trusted to do it themselves).
I don't see why it makes your job any harder. Sounds like a very
good argument for Open Source and/or Free Software. :)
-Joseph
--
Joseph==============================================jap3003@ksu.edu
"IBM were providing source code in the 1960's under similar terms.
VMS source code was available under limited licenses to customers
from the beginning. Microsoft are catching up with 1960."
--Alan Cox, http://www2.usermagnet.com/cox/index.html
next prev parent reply other threads:[~2001-08-03 21:52 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 [this message]
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
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=20010803165221.C11011@ksu.edu \
--to=jap3003@ksu.edu \
--cc=jap3003+response@ksu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@randomlogic.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