On Sunday 15 January 2006 1:00 pm, Jim Powers wrote:
> Unfortunately this is true.  I am game for cracking this thing, but time
> (I'd have to learn a TON about decryption) and priorities (I've got my
> own projects to work on) will prohibit this.  I hate the idea of letting
> these bastards get away with stomping all over my rights, especially via
> wrong-headed legislation.

Well, I was thinking about this the other day (after reading some of the 
links that the wiki pointed me to).

What if the portion of the Windows code that loads the firmware (ie. does 
the decryption and such) could be loaded and executed?  Then there's no 
DMCA problem in the U.S.  Once the firmware is loaded, that portion of code 
is kicked out of the kernel.

Of course, using an open wireless link (even in the U.S.) it's feasible that 
one could upload the decrypted firmware to a site outside the U.S.  A 
particular location in Sweden comes to mind. :-)

Using an unauthenticated wireless connection would be the way to go.

Of course, I agree that TI should just release the stupid firmware.  I 
browsed around their pages to see if I could download it from them.  I got 
to the point of ordering a sample of the chipset (which would have to 
include the firmware) and the driver development kit, but then the TI.com 
web site wanted a (free?) login.

It seems to me that the correct way to go about this might be to pressure 
Compaq/HP into getting the unencrypted firmware from TI and releasing it.  
After all, HP has a customer base that they (should) want to keep happy, 
while TI is just a backend supplier (with emphasis on "backend"!).

Just thinking out loud...
-- 
Frank J. Edwards
Edwards & Edwards Consulting, LLC
Voice: (813) 996-7954
Email: [EMAIL PROTECTED]
Large Attachments To: [EMAIL PROTECTED]

Attachment: pgp4v4ESBpepw.pgp
Description: PGP signature

_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Reply via email to