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: <625fc13d0702151041w3621b18aw299133164db1bde4@mail.gmail.com>
Date:	Thu, 15 Feb 2007 12:41:45 -0600
From:	"Josh Boyer" <jwboyer@...il.com>
To:	"v j" <vj.linux@...il.com>
Cc:	"Theodore Tso" <tytso@....edu>, "Dave Jones" <davej@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: GPL vs non-GPL device drivers

On 2/15/07, v j <vj.linux@...il.com> wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
> All this is fine. Just say so. Make it black and white. Make it
> perfectly clear what is and isn't legal. If we can't load proprietary
> modules, then so be it. It will help everybody if this is out in the
> clear, instead of resorting to stupid half measures like
> EXPORT_SYMBOL_GPL.

That does not prevent you from loading proprietary modules.  If your
legal team finds it acceptable to use non-GPL modules, then at your
risk it is possible to modify the kernel source to remove the
restriction anyway.

You are not blocked by this.  Your largest gripe seems to be the fact
that the community does not want to endorse proprietary modules.  For
_your_ use, with advice from _your_ legal team, with _your_ company
assuming any risk, you can certainly continue to use Linux because the
very people you're whining at _did_ contribute the code and provide it
under an Open Source license.  However, I would not want to be in your
position should your company choose to go that avenue and a lawsuit
occurred.

The fact that you're asking for the community to care about
proprietary modules seems odd to me.  It's as if you almost know that
it's legally questionable and you want the community somehow make it
ok to use proprietary modules so you feel better.

Anyway, Linux is not BSD.  If you want something you can take and not
have to care about giving back to, perhaps you should look into that.

josh
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ