full-disclosure - Re: Nipper licensing

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]

Message-ID: <74081.1251902020@turing-police.cc.vt.edu>
Date: Wed, 02 Sep 2009 10:33:40 -0400
From: Valdis.Kletnieks@...edu
To: Eric Sesterhenn <snakebyte@....de>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Nipper licensing

On Wed, 02 Sep 2009 11:48:42 +0200, Eric Sesterhenn said:

> LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:
> 
> THIS IS IMPORTANT:
> 
> libNipper and all other Nipper products are licensed under the GPL version 3
> with the following exceptions.

> 1. The code cannot be used as part of a commercial product.

I wonder how Rich Stallman feels about the concept of 'GPLV3 plus exceptions'.

Oh, we already know.  Section 10 of the GPLV3 says:
"You may not impose any further restrictions on the exercise of the rights
granted or affirmed under this License. "

And that would certainly qualify as a "further restriction". (In particular,
"as part of a commercial product" has some serious GPL issues if the person is
trying to use it as part of a commercial product that is itself under GPLV3).

Your second exception (regarding copyright info) can probably be rephrased
so it's aggreeable with clause 7(c).

You might want to run this past the good guys at the FSF and get their
reaction.

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/