linux-kernel - Re: Building two (external) modules from the same sources

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]

Date:	Wed, 01 Oct 2008 23:27:16 +0100
From:	TJ <linux@...orld.net>
To:	Greg KH <greg@...ah.com>
Cc:	Andrey Borzenkov <arvidjaar@...l.ru>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Casual J. Programmer" <casualprogrammer@...glemail.com>
Subject: Re: Building two (external) modules from the same sources

On Wed, 2008-10-01 at 13:05 -0700, Greg KH wrote:
> Hm, I'll look at the code and see if I see anything obvious.
> 
> > If someone could offer (link to) hermes-1/2 programming manual ...
> 
> That would probably help out a lot :)

Unfortunately the changes in the corporate history have always confused
the issue of locating the old documentation.

As I understand it, the chipset(s) were originally developed at Lucent
around 1999-ish. In 2000 the division responsible became a subsidiary
called Agere Systems. In 2002 it was spun-off as a separate business. In
April 2007 it was bought by LSI Corporation, and by the end of 2007 had
lost its separate existence, along with its web-site and the developer
resources it provided.

The Wayback Machine has working links to the product data-sheets and the
original driver packages:

http://web.archive.org/web/20031202185415/www.agere.com/client/wlan.html
http://web.archive.org/web/20060330013615/http://www.agere.com/mobility/wireless_lan_drivers.html

There is another source of confusion - the actual chip-sets used.

Under the name WaveLAN/IEEE there was a pre-802.11b chip-set, as well as
the later WaveLAN Hermes I (1/one) and II (2/two) which are 802.11b
compatible.

The orinoco_cs drivers support the Hermes I chip-set, at least for WEP,
but as I recall, not for WPA/WPA2.

With Andrey's modifications the wlags49 driver supports WPA but not WPA2
- at least not in my tests.

The only technical documentation I can find, and I'm not sure it will be
completely applicable to the 802.11b Hermes chip-sets, is the 1999
Lucent Technologies/Bell Labs Innovations document:

"DRAFT Software Interface Specification for Wireless Connection
Interface for WaveLAN/IEEE (HCF-light)"

which is available (for now) from a Berkeley graduate student's site:

http://bwrc.eecs.berkeley.edu/People/Grad_Students/jbeutel/wavelan_s0005-11-light.htm

The HCF information might be pretty close to what is used in the HCF by
the Hermes wlags49 MSF.

TJ.

P.S. Andrey: Your mail-provider (mail.ru) is blocking my emails to you.

--
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/