From: "David Schwartz" <davids@webmaster.com>
To: <Valdis.Kletnieks@vt.edu>, "Bansh " <bansh21@mail.ru>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: GPL license and linux kernel modifications
Date: Thu, 29 Jan 2004 03:14:32 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEAFKAAA.davids@webmaster.com> (raw)
In-Reply-To: <200401290255.i0T2txQq013612@turing-police.cc.vt.edu>
> On Tue, 27 Jan 2004 19:25:55 +0300,
> =?koi8-r?Q?=22?=Bansh=?koi8-r?Q?=22=20?= <bansh21@mail.ru> said:
> Yes, but it has to be the *preferred* source form. So you have
> to distribute
> what you're actually using to maintain the system. You want to claim that
> the very tricky code is your preferred form, go right ahead. Let
> me know how
> the first time you try to fix a bug goes. ;)
> It is most certainly *NOT* allowed to pass your code through a obfuscator
> before shipping it out.
In my insanest musings, I've thought about a case where one has a
decrypting/encrypting editor and a decrypting compiler. This could honestly
make the encrypted source the preferred form for the purposes of making
modifications.
Anyone who attempts this would likely run afoul of a legal principle known
as the "straight face doctrine". This says that one may not make any
argument in court unless one can do so with a straight face. Because of
this, lawyers that can say rather insane things with perfectly straight
faces are quite highly prized.
DS
next prev parent reply other threads:[~2004-01-29 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 16:25 "Bansh"
2004-01-27 16:33 ` Kevin P. Fleming
2004-01-27 17:56 ` Måns Rullgård
2004-01-29 2:55 ` Valdis.Kletnieks
2004-01-29 11:14 ` David Schwartz [this message]
2004-02-01 20:49 ` Bill Davidsen
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=MDEHLPKNGKAHNMBLJOLKMEAFKAAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bansh21@mail.ru \
--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
Powered by JetHome