linux-kernel - the easy way to sandbox?

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-next>] [day] [month] [year] [list]

Date:	Mon, 21 May 2012 09:28:13 -0700
From:	ivo welch <ivo.welch@...erson.ucla.edu>
To:	linux-kernel@...r.kernel.org
Subject: the easy way to sandbox?

Suggestion:  introduce a system call that eliminates access to all
real file systems for the current process.  the only permissible
interaction would be stdin, stdout, and stderr.

this would make it very simple to write a sandboxed safe fcgi script.
the script could load all the dynamic libraries and data it wants, and
then call this no-more-filesystem-access feature (preferably allowable
without root privileges).  thereafter, even if a hacker takes control
of the script, not much permanent damage can happen.

right now, it is much more complex to accomplish this---which is why
sandboxing cgi scripts is not used too often.

sincerely,

/iaw

----
Ivo Welch (ivo.welch@...il.com)
--
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/