linux-kernel - Re: GPLv3 Position Statement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Sep 2006 14:40:44 +1000
From:	Neil Brown <neilb@...e.de>
To:	James Bottomley <James.Bottomley@...elEye.com>
Cc:	tridge@...ba.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

On Thursday September 28, James.Bottomley@...elEye.com wrote:
> It's the "act of running the program is not restricted".
> 
> This is really the crux of the argument with the FSF over the DRM
> clauses.  If you take the position (as the people who signed the
> discussion paper do) that embedded Linux constitutes an end use, then
> this freedom from restriction of running the programme is compromised in
> GPLv3, and hence is against the spirit of GPLv2 (and thus violates
> clause 9 of GPLv2).

I hadn't seen this distinction before, and it is probably worth
repeating and exploring a bit.

You seem to be saying that including software in a product that you
then distribute is *both* a USE and a DISTRIBUTION of that software.
So if the software is obtained under the GPL, and the GPL asserts "no
restrictions on use" then it should also not restrict distribution.
It can place requirements that must be met before distribution is
allowed, but they shouldn't be so onerous as to inhibit distribution.
Does that sound right?

The requirements in GPLv2 are not sufficient to prevent distribution.
The requirements in GPLv3-draft are - they might require modification
to the device which might make it illegal to sell (?).

Presumably this doesn't just apply to embedded uses.
When Redhat or Novell/SuSE make a Enterprise Distribution, they are
"using" Linux just as much as a company produces devices with embedded
Linux are.

So if GPLv3 required not only that you give away the right to assert
your patents, and give away certain secrets (keys) but also that you
give up the right to protect your Trademarks, then Redhat would
probably be very unhappy about that, as might Mozilla.  Fortunately
GPLv3-draft doesn't make that requirement.
I wonder what v4 will do :-) 

I wonder how hard it is to modify the hardware of a Tivo-2 to allow
software updates (it was done for the Xbox after all), and if the
difference between that and the effort of removing trade marks from
RHEL (just producing whitebox) is a difference of degree or a
difference of kind....

NeilBrown

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/