| 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
| ||
|
Date: Fri, 16 Feb 2007 00:07:10 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: v j <vj.linux@...il.com> CC: Scott Preece <sepreece@...il.com>, linux-kernel@...r.kernel.org Subject: Re: GPL vs non-GPL device drivers v j wrote: > Greg > KH has gone and made the basic sysfs interface, which any generic > driver could use as EXPORT_SYMBOL_GPL. > ...The point is that old functionality is being ripped > off and new ones introduced, and their interfaces are not open > anymore. Hmm...you keep using the word "open". What definition are you using? Because the new implementation is licensed under the GPL, which is an "Open Source" license. By definition, this means that it is "open". What I see you saying is that the interfaces are more restrictive than before. This is true. However, if you are confident that you are abiding by the terms of the GPL then there is nothing stopping you from patching the kernel to convert the EXPORT_SYMBOL_GPL to just EXPORT_SYMBOL. The _GPL version is just a hint as to the intent/opinion of the designer. The flip side of that is that using only items exported via EXPORT_SYMBOL doesn't make you automatically compliant to the GPL. You could still be infringing if the module is legally considered a derivative work of the kernel. Chris - 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/
Powered by blists - more mailing lists