public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chad Christopher Giffin <typo@shaw.ca>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paulo Marques <pmarques@grupopie.com>
Subject: Re: Linuxant/Conexant HSF/HCF Modem Drivers Unlocked
Date: Fri, 29 Oct 2004 06:43:08 -0600	[thread overview]
Message-ID: <1099053788.4511.13.camel@localhost> (raw)
In-Reply-To: <418226FA.1030803@grupopie.com>

[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]

On Fri, 2004-10-29 at 12:18 +0100, Paulo Marques wrote:
> Chad Christopher Giffin wrote:
> > I couldn't help but notice that the Linuxant Modem drivers appear to be
> > GPL'd, as a strings of the modules shows that License=GPL.
> 
> There was a huge discussion about this in April. You should check this 
> thread:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=108303207819170&w=2

Thank you for bringing this to my attention. :-) 

> Always search the archives before posting to LKML ;)

Yes, I see why.


Well then, it appears as though I have made a mistake which therefore
warrants a public request that: 

Any recipients of my email to the Linux Kernel Mailing List, which had
attachment "keygen.pl" for generating keys for Linuxant HCF/HSF modem
drivers, are all hereby requested to ignore said email, save for the
purpose of its immediate removal, and take notice that the Linuxant
drivers are in fact covered by a non-GPL, commercial license.  Use of
that script would be illegal.


I still find myself deeply troubled and questioning the legalities of
using "GPL\0[...]" in the license string of a non-GPL module.  As it is
a blatant lie.  

A string is used to represent ASCII characters, normally.  And this is
often data that is for human eligibility.  Said format of string storage
uses NULL, or \0, as a mark of termination of string.  

Therefore such a string implies that the license *is* GPL.  Since
the /ONLY/ use of this variable is to mark the license type of the
module, it has been violated by this clear form of abuse.

My apologies to Linuxant for any troubles this misinterpretation of
their lie^H^H^Hhack may have caused.

-- 
Chad Christopher Giffin
mailto:typo@shaw.ca

There are 10 kinds of people in this world... those who understand
binary and those who do not.   -- Anonymous


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-29 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  6:52 Linuxant/Conexant HSF/HCF Modem Drivers Unlocked Chad Christopher Giffin
2004-10-29 11:18 ` Paulo Marques
2004-10-29 12:43   ` Chad Christopher Giffin [this message]
2004-10-29 12:49     ` Arjan van de Ven
2004-10-29 13:50     ` Alan Cox
2004-10-29 20:00       ` Dave Jones
2004-10-29 20:21         ` Willy Tarreau
2004-10-29 20:37         ` Andreas Steinmetz
2004-10-29 22:46           ` Kenneth Aafløy
2004-10-29 22:54             ` Andreas Steinmetz

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=1099053788.4511.13.camel@localhost \
    --to=typo@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    /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