linux-kernel - Re: Inserting code from userspace to kernel space

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: <Pine.LNX.4.64.0805261143450.18218@twin.jikos.cz>
Date:	Mon, 26 May 2008 11:44:54 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	David Newall <davidn@...idnewall.com>
cc:	Shuduo Sang <sangshuduo@...il.com>, devzero@....de,
	bosko.radivojevic@...il.com, linux-kernel@...r.kernel.org
Subject: Re: Inserting code from userspace to kernel space

On Sun, 25 May 2008, David Newall wrote:

> > someone does not want to leak propertied algorithm out with GPL. This
> > can be a way to protect.
> Perhaps you want something similar to the firmware files that some 
> devices need loaded?  (By the way, I think the word is "proprietary".) 

This is different, because the firmware that is loaded by 
request_firmware() is not meant to be interpreted/executed by the kernel, 
drivers usually just pass it over to the device.

-- 
Jiri Kosina
SUSE Labs

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