linux-kernel - Re: [PATCH] kconfig: consolidate arch-specific seccomp options

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: <52EA8267.4020107@sr71.net>
Date:	Thu, 30 Jan 2014 08:48:39 -0800
From:	Dave Hansen <dave@...1.net>
To:	Ingo Molnar <mingo@...nel.org>
CC:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	linux-security-module@...r.kernel.org, linux-arch@...r.kernel.org,
	sfr@...b.auug.org.au, zohar@...ux.vnet.ibm.com,
	linux@....linux.org.uk, monstr@...str.eu, ralf@...ux-mips.org,
	benh@...nel.crashing.org, paulus@...ba.org, schwidefsky@...ibm.com,
	heiko.carstens@...ibm.com, lethal@...ux-sh.org, x86@...nel.org,
	james.l.morris@...cle.com
Subject: Re: [PATCH] kconfig: consolidate arch-specific seccomp options

On 01/30/2014 12:55 AM, Ingo Molnar wrote:
>> > +	  This kernel feature is useful for number crunching applications
>> > +	  that may need to compute untrusted bytecode during their
>> > +	  execution. By using pipes or other transports made available to
> I'd change and simplify the first sentence to:
> 
>> > +	  This kernel feature is useful to sandbox runtimes that need
>> > +	  to execute untrusted machine code.
> Seccomp isn't primarily about number crunching anymore, and it's 
> definitely not about 'bytecode' in the classical sense either.

I'll change that if I need to send it again.  Otherwise, I'll leave it
to the folks who actually know something about the feature, which isn't me.

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