linux-kernel - Re: Free Linux Driver Development!

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: <20070201164201.GI7584@csclub.uwaterloo.ca>
Date:	Thu, 1 Feb 2007 11:42:01 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Michael Buesch <mb@...sch.de>
Cc:	Jeff Garzik <jeff@...zik.org>, Roland Dreier <rdreier@...co.com>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

On Thu, Feb 01, 2007 at 04:46:38PM +0100, Michael Buesch wrote:
> Nah, why do you think it will screw up the eeprom?
> Did you try to completely power off the machine before rebooting
> into windows?

No at the time I don't think I powered it off, and I suspect that is
probably what went wrong.  The windows driver probably didn't like the
state of the chip after linux had poked it.

> I _really_ _really_ _really_ think that there is no chance of writing
> the eeprom by accident. It is protected by some write-enable bit in
> PCI config space. There is only one place where we enable that bit
> and where we actually _write_ to the eeprom shadow mmio space. That's
> the eeprom writing code. It will output _lots_ of kernelmessages that
> you really can't miss when that happens. And it's only called on behalf
> of a private ioctl user request. _And_ it verifies the data with a CRC
> check. So you really can't call it by accident.

Well it must have just been the state of some registers then.

> But prove me wrong and show the code that writes to eeprom. :)

I suspect I can't.  I still can't make it connect successfully to
anything yet, but that could just be a configuration problem, or it not
liking WPA encryption yet.

> Are you suggesting that bcm43xx people don't, or what?

I have just mainly seen messages about devicescape from the ralink
driver.

> Are you living on another planet than me? Mine is called "Earth".

Sometimes I might be.  At least on the days I have to deal with problems
in Windows (it's not even my machine, so I don't get to pick what it
runs all the time. :)  I haven't had particularly much luck getting a
stable wireless going on linux yet, although I haven't put much effort
into it yet either.  I figure in a couple of years there will be so many
wifi devices around that wireless won't work anymore anyhow so it isn't
a high priority.  I like simple trustworthy wires.

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