From: dj@deadhat.com
To: linux-kernel@vger.kernel.org
Subject: Why is my copyright code in the linux kernel?
Date: Tue, 1 Mar 2011 14:49:28 -0800 [thread overview]
Message-ID: <ded07e5c09d72da478c6218658095f5a.squirrel@deadhat.com> (raw)
I was surprised to find code that is mine in Linux.
Following the advice in the REPORTING_BUGS file, I'm sending this email
here, for want of knowledge of a better contact.
In 2002, I published code at www.deadhat.com to generate cryptographic
vectors to aid in the development of IEEE 802.11i, a spec for which I was
a contributor.
One example can be found here:
http://www.deadhat.com/wlancrypto/ccm1.2.c
You will see a remarkable resemblance to parts of
linux-2.6.36.2/drivers/staging/rt2860/common/cmm_aes.c. E.G. the AES code,
the MIC header code and some ancillary functions.
However my header with my name and copyright has been removed. A different
copyright has been added and it has been licensed under the GPL without my
knowledge.
I am a happy user of Linux, I don't want to cause trouble and I'd be quite
honored to have some of my code in the kernel, so I'm not demanding the
immediate removal of this code. I'm willing to GPL my code if necessary,
but I do require proper attribution and acknowledgment of my copyright on
my code
I'd like to know who is an appropriate person to discuss this with.
Thank you,
David Johnston
dj@deadhat.com
next reply other threads:[~2011-03-01 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 22:49 dj [this message]
2011-03-01 23:30 ` Why is my copyright code in the linux kernel? richard -rw- weinberger
2011-03-01 23:54 ` Ted Ts'o
2011-03-02 21:52 ` H. Peter Anvin
2011-03-03 6:04 ` Greg KH
2011-03-04 5:29 ` David Johnston
2011-03-04 6:34 ` H. Peter Anvin
2011-03-04 22:16 ` Yinghai Lu
2011-03-04 22:19 ` H. Peter Anvin
[not found] ` <56a24cfecea63a4752f441056da9c813.squirrel@deadhat.com>
2011-03-03 4:03 ` Greg KH
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=ded07e5c09d72da478c6218658095f5a.squirrel@deadhat.com \
--to=dj@deadhat.com \
--cc=linux-kernel@vger.kernel.org \
/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