linux-kernel - Re: ipw3945 status

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: <20060730231251.GB1800@elf.ucw.cz>
Date:	Mon, 31 Jul 2006 01:12:51 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Theodore Tso <tytso@....edu>, Kasper Sandberg <lkml@...anurb.dk>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Jan Dittmer <jdi@....org>, Jirka Lenost Benc <jbenc@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ipw2100-admin@...ux.intel.com
Subject: Re: ipw3945 status

Hi!

> > > Because it would involve a moderate rewriting of the driver, and we'd 
> > > have to carry a delta against Intel's code forever.
> >
> > without knowing this for sure, dont you think that if a largely changed
> > version of the driver appeared in the tree, intel may start developing
> > on that? cause then they wouldnt be the ones that "broke" compliance
> > with FCC(hah) by not doing binaryonly.
> 
> It's just as likely that their lawyers would tell them that they would
> have to pretend that the modifications don't exist at all, and not
> release any changes for any driver (like OpenBSD's) that bypassed the
> regulatory daemon.  The bigger worry would be if they decided that
> they couldn't risk supporting their current out-of-tree driver, and
> couldn't release Linux drivers for their softmac wireless devices in
> the future.
> 
> Personally, I don't see why the requirement of an external daemon is
> really considered that evil.  We allow drivers that depend on firmware
> loaders, don't we?  I could imagine a device that required a
> digitally

Well, drivers that depend on external, non-redistributable firmware
(aka ipw2200/ipw2100) already are evil, but at least I do not run
untrusted code on my CPU. (And yes, firmware in ipw2200 crashes a
_lot_).

Plus, that regulatory daemon probably contains security hole (or two)
inside, and I can't properly audit it. (Yes, firmware in ipw2200
probably contains security holes, too, but at least those are more
"interesting" to exploit).

And... Intel will not even tell you WTF that daemon does. They claim
it is for FCC, but it seems to be doing more than that. So maybe I'm
not _that_ paranoid.

(Of course, binary-only kernel module would be even uglier).

Ouch and binary-only daemon will conviently prevent me from using that
wireless card in ppc machine.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/