linux-kernel - Re: Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3)

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

Message-ID: <d0af58324910b1c75d7d4e5185ab03ee@redchan.it>
Date:   Tue, 29 Jan 2019 09:38:24 +0000
From:   linuxgpletc@...chan.it
To:     editor@...z.com, editor@....net, news@...register.co.uk
Cc:     misc@...nbsd.org, freebsd-chat@...ebsd.org,
        linux-kernel@...r.kernel.org, gentoo-user@...ts.gentoo.org
Subject: Re: Author of GPC-Slots2 promises to sue "John Doe" who violated GPL
 recission. (update 3)

Some updates (3):

http://8ch.net/tech/res/1018729.html

Anonymous  01/29/19 (Tue) 09:23:25 No.1024608

>> 1024606

https://copyleft.org/guide/comprehensive-gpl-guidech8.html#x11-540007.4

Sorry lad.

Anonymous  01/29/19 (Tue) 09:25:16 No.1024609

>> 1024604

> Cites previously anonomyous paralegal woman from online rag

> Ignores published lawyers who are men

(Paralegal woman stopped talking after she would outed)

Anonymous  01/29/19 (Tue) 09:27:15 No.1024610

>> 1024608

Sorry, they published that "clarification" after I raised the issue, and 
their "clarification" is bullshit.

Guess what: The FSF doesn't make the law.

Quick rundown:

Section 4 of the GPLv2 states "parties who have received..."

The "you" here is the licensee, it is not the grantor (See Section 0 of 
the GPLv2 "Each licensee is addressed as "you". "). It is not applicable 
against the grantor of the license: it is a rule the licensee has to 
abide by, set by the grantor, in-order to have permission to modify or 
create derivative works at all.

About the printer driver case: The contract in that case is the 
preliminary writing, the offer to do business ("pay us, or alternatively 
follow the GPL"). The acceptance of that contract by following the terms 
of that preliminary writing (choosing the GPL instead of paying). That 
is why both contract and damages under copyright are available. Damages 
for the contract portion ("pay us"), or damages for violating the GPL 
license.

The parties later settled out of court. The key is that the businesses 
offer created two alternative means of acceptance of it's offer to do 
business: pay for the commercial license, or follow the GPL. So the 
court allowed the biz to recover the lost profit.

Anonymous  01/29/19 (Tue) 09:29:15 No.1024612

>> 1024608

Sorry, read a book *, not a publication by interested parties that was 
debunked 5 hours after it was published. 
https://lkml.org/lkml/2018/10/26/420

* 
https://www.amazon.com/Open-Source-Licensing-Software-Intellectual/dp/0131487876

Anonymous  01/29/19 (Tue) 09:34:06 No.1024614

>> 1024604

>> 1024608

Cites idiot self-sure* paralegal woman who doesn't know her ass from her 
elbow, and who went silent after she was outed, plus a publication from 
an interested party that was immediately debunked.

  (*is there any other type?)

Vs: Cites published lawyers well versed in their field.

Explains why interested party's publication is bullshit immediately once 
aware of the fraudulent advice.

Anonymous  01/29/19 (Tue) 09:36:24 No.1024615

Notice no response to >>1024602

Just a change of tactics.