linux-kernel - [ANNOUNCE] ndiswrapper 1.54 for Linux 2.6.28 Released

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-next>] [day] [month] [year] [list]

Message-ID: <38153.166.70.238.44.1230404757.squirrel@webmail.wolfmountaingroup.com>
Date:	Sat, 27 Dec 2008 12:05:57 -0700 (MST)
From:	jmerkey@...fmountaingroup.com
To:	linux-kernel@...r.kernel.org
Subject: [ANNOUNCE] ndiswrapper 1.54 for Linux 2.6.28 Released

ftp://ftp.wolfmountaingroup.org/pub/ndiswrapper/ndiswrapper-1.54-2.6.28.tar.gz

The breakage during unload and subsequent kernel corruption has been
tracked down to link_watch.c and the packet scheduler code and is due to
list corruption in dev_deactivate() being called with an invalid netdev
context.

The linkwatch code is not called by ndiswrapper and the problems are due
to poor error checking and cleanup in Linux proper with network drivers. 
As such, ndiswrapper for 2.6.28 is posted as released based upon input
from other folks.  Thanks to those folks who downloaded and tested the
code and provided feedback for this release.

The Native Linux wireless drivers and the hacked up pseudo-pirated
microcode they rely on still do not work properly on most of my laptop
wireless drivers or are very flaky for the BCM based drivers and Intel
3945 series drivers in 2.6.28.  ndiswrapper almost a required component in
order to use wireless with Linux on a large number of laptops.    I see no
way around the current vendors offerings which are heavily dependent on
internal and proprietary microcode without ndiswrapper since the Linux
drivers are essentially impossible to keep working.

Since most people (me included) are not interested in engaging in piracy
by using tools which lift microcode and firmware images from ndis drivers,
ndiswrapper seems a reasonable compromise since any customer who purchases
a card with ndis based drivers has a legal right to use them as ndis
drivers.

Cutting and pasting firmware seems too much like piracy, not to mention
being a great big hassle.

Jeff

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