linux-kernel - Why is everyone comfortable with GRSecurity violating the terms underwhich the Linux Kernel is licensed out?

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>] [day] [month] [year] [list]

Message-ID: <5d7fee582288a239d6c70394e3ca3956@airmail.cc>
Date:   Thu, 15 Jun 2017 15:10:44 +0000
From:   aconcernedfossdev@...mail.cc
To:     linux-kernel@...r.kernel.org
Subject: Why is everyone comfortable with GRSecurity violating the terms
 underwhich the Linux Kernel is licensed out?

Why is everyone comfortable with GRSecurity violating the terms 
underwhich the Linux Kernel is licensed out?

They are preventing redistribution of their derivative work.

The Law is not a Genie, it is not a computer, and Judges are not fools.

The license grant the Linux Kernel is distributed under disallows the 
imposition of additional terms.
The making of an understanding that the derivative work must not be 
redistributed (lest there be retaliation) is the imposition of an 
additional term.
The communication of this threat is the moment that GRSecurity violates 
the license grant.
Thence-forth modification, making of derivative works, and distribution 
of such is a violation of the Copyright statute.
The concoction of the transparent scheme shows that it is a willful 
violation, one taken in full knowledge by GRSecurity of the intention of 
the original grantor.