linux-kernel - Re: Agere Hermes source-code: copyright situation

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]

Date:	Thu, 2 Oct 2008 06:37:18 +0400
From:	Andrey Borzenkov <arvidjaar@...l.ru>
To:	Dave <kilroyd@...glemail.com>
Cc:	Greg KH <greg@...ah.com>, TJ <linux@...orld.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Casual J. Programmer" <casualprogrammer@...glemail.com>,
	linux-wireless@...r.kernel.org,
	Alexander Shirshikov <alexander.shirshikov@...il.com>
Subject: Re: Agere Hermes source-code: copyright situation

TJ you can answer me using arvidjaar (at) newmail dot ru. Hopefully
one of them works. Re WPA2 - there is no information how to setup
CCMP/AES (even if firmware supports it); so no WPA2.

On Thursday 02 October 2008, Dave wrote:
> Greg KH wrote:
> > On Wed, Oct 01, 2008 at 05:40:29PM +0100, TJ wrote:
> >> On Wed, 2008-10-01 at 14:13 +0400, Andrey Borzenkov wrote:
> >>>On Wednesday 01 October 2008, Greg KH wrote:
> >>>> On Mon, Sep 29, 2008 at 09:49:34AM +0400, Andrey Borzenkov wrote:
> >>>>> I have here driver that can be built for two different types of
> >>>>> hardware from basically the same sources (this is port of old Agere
> >>>>> drivers for Hermes-I/Hermes-II chipsets).
> >>>> 
> >>>> Cool, do you have a link to the code, I'd be glad to add it to
> >>>> drivers/staging/ if it's not in a fully-mergable state yet to get wider
> >>>> users for it.
> >>>
> >>> You can look at it here: http://arvidjaar.newmail.ru/wlags49.tar.bz
> >>>
> >>> I doubt that it is suitable for inclusion at current state if ever.
> >>> This is taken directly from Agere 2.4 sources; the only parts that were
> >>> touched are kernel glue and wireless extensions interface.
> >>>
> >>> And it is not GPL'ed, of course. I attach E-Mail I received a while
> >>> back with answere from Agere legal department.
> >>
> >> I'm attaching the original email I sent to Agere and their response for
> >> the record, hoping it helps clarify the legal position.
> > 
> > Very nice, thanks for forwarding this on.
> > 
> > As the license is BSD, that means we can place it in the kernel tree.
> > Do you all mind if I add it to the drivers/staging/ directory so you can
> > work on cleaning it up within the main kernel tree infrastructure?
>

I do not mind but it is likely makes no sense for H-I now; and
I do not own H-II myself so cannot work on it. If we are focusing on
H-2/2.5, it would make more sense to make similar modifications to
7.22 driver set from Agere to avoid overlap with Orinoco.
 
> (cc'ing linux-wireless)
>
> FYI, Hermes I hardware is already covered by the orinoco driver. WPA and firmware download functionality (which is supported by the Agere driver, but not orinoco in 2.6.27) is already in the wireless queue for 2.6.28.
> 

Yes, I discovered this yesterday as well. Thank you!

How are you going to distribute firmware? You will need 9.x firmware from
original Agere driver; do I understand it correctly that it will come
with orinoco in binary form?

> This leaves Hermes-II (and USB?) hardware which orinoco does not support, but could if someone had access to a card for development.
> 

As I initially wrote driver for internal consumption my mods supports
PCMCIA only.

Unfortunately I do not own Hermes-II device myself. I was asked recently
by Alexander who is owing such device and modification of Agere sources was
pretty trivial. I Cc to him; Aexander are you interested in aiding of
H-II driver development for mainstream?

Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)