linux-kernel - Re: [PATCH] USB: mark USB drivers as being GPL only

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]

Date:	Thu, 07 Feb 2008 14:34:03 -0500
From:	Lee Mathers <Lee.Mathers@...fs.org>
To:	David Newall <davidn@...idnewall.com>
CC:	Diego Zuccato <diego@...llo.alma.unibo.it>,
	Greg KH <greg@...ah.com>,
	Christer Weinigel <christer@...nigel.se>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only

>> And it's a logical problem, too: why should the *driver* enforce a
>> *technical* limit?
>>     
> That's part of it's purpose.  It permits a manufacturer to make a global
> device that operates within local restrictions.
> --
>   

Then the hardware vendor needs to review there practices.  If you want 
to limit the ability of your technology do not include it.    I realize 
that this has become large revenue stream for many company's.   What 
they do not realize is that they have created a Wack-a-Mole situation.  
Just look at the Digital Satellite TV industry.

Companies used to Produce one logic board and selectively remove certain 
resistors or ic's to limit the end users ability.   The end user could 
still solder the missing chips etc to by  pass but much more 
difficult.   Way I see it is let the companies does as they please as 
they will bury themselves in the long run.

Now we have hardware ASIC that depend on the most part a (dll in 
windows) or .ko .o file under linux to provide the entire instruction 
set.  Think Winmodems,  Winprinters etc....
--
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/