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: Thu, 7 Mar 2019 01:42:45 +0100 From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net> To: Pavel Machek <pavel@....cz>, Joel Fernandes <joel@...lfernandes.org> Cc: hpa@...or.com, Daniel Colascione <dancol@...gle.com>, Greg KH <gregkh@...uxfoundation.org>, linux-kernel <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, ast@...nel.org, atishp04@...il.com, Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>, Jan Kara <jack@...e.cz>, Jonathan Corbet <corbet@....net>, karim.yaghmour@...rsys.com, Kees Cook <keescook@...omium.org>, kernel-team@...roid.com, "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>, Manoj Rao <linux@...ojrajarao.com>, Masahiro Yamada <yamada.masahiro@...ionext.com>, Paul McKenney <paulmck@...ux.vnet.ibm.com>, "Peter Zijlstra (Intel)" <peterz@...radead.org>, Randy Dunlap <rdunlap@...radead.org>, rostedt@...dmis.org, Thomas Gleixner <tglx@...utronix.de>, "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>, yhs@...com Subject: Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel On 07.03.19 00:09, Pavel Machek wrote: > So your licensing requirements prevent you from having headers in the > filesystem, but allow module with the headers hidden inside on the > filesystem? Maybe it's just because I've missed most of the thread, but which license requirements exactly could that be ? The kernel still is GPL, isn't it ? So, any device vendor needs to hand out the exact kernel source he hat built the image from, anyways. (by the way: we should start a flash mob action of demanding sources from the pocket-computers-with-3g vendors, but that's another story ;-)) So, what kind of license issue could it be, which prevents putting the files (that you'd have to hand out anyways) directly into filesystem, while allowing them in a .ko in the same filesystem ? I'm confused. > Looks like you should just tar xvzf > this-is-a-kernel-module-I-promise.ko /usr/src/linux/include :-). We should ask coreutils folks to add an ELF encapsulation to tar ;-) --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists