linux-kernel - Re: Why is my copyright code in the linux kernel?

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: <AANLkTim6utrJZ-jVJdNJA6Ea_f8xQ-eAaGX8yfBaT9oc@mail.gmail.com>
Date:	Fri, 4 Mar 2011 14:16:43 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	David Johnston <dj@...dhat.com>, tytso@....edu,
	richard.weinberger@...il.com, linux-kernel@...r.kernel.org,
	gregkh@...e.de
Subject: Re: Why is my copyright code in the linux kernel?

On Thu, Mar 3, 2011 at 10:34 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 03/03/2011 09:29 PM, David Johnston wrote:
>> Yes I am willing to allow you to retain it.
>> I guess, to be all legalese..
>>     I herein permit you to use any 802.11 related C code taken from the
>> www.deadhat.com website, in the linux kernel, and to publish it under
>> the terms of version 2 of the GNU General Public License.
>>
>> Yes I've emailed ralink and VIA. I hope they're nice people.
>
> First of all, thank you (both for the code and for being reasonable.)
>
> It sounds like this might simply have been an honest misreading.
>

interesting.

in the git history, some functions take IN/OUT macro.

-VOID AES_GTK_KEY_UNWRAP(IN UCHAR * key,
-                       OUT UCHAR * plaintext,
-                       IN UINT32 c_len, IN UCHAR * ciphertext)

so they had driver for other os at first, and ported that one to Linux later ?

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/